I know this post is over 8 years old, but it is the only one that was "on 
point" to a problem I was having.  I now have a solution so am simply updating 
this in case others stumble upon the same situation. I'm on Coldfusion 9.

My set up is exactly like the original poster's:  webservices in a directory 
under the webroot, components in a directory outside the webroot of the current 
app.

I was getting the same as errors described above. 

What I discovered - after much hair pulling! - was that I had carefully (I 
thought) sculpted a extremely limited subset of the main application.cfc (being 
overly cautious perhaps) and placed it in the web services directory.  In 
CFAdmin, the order for reading application.cfcs was set to "default order".  
Accordingly it was reading the application.cfc in the web services directory.

I also put all my mappings in the application.cfc (vs. manage them in the 
CFAdminstrator).

Well, in my vast wisdom, I discovered that I had excised the mapping to the 
components directory in the web services version of application.cfc.  Once I 
added that back in, I was in heaven.  The components lived outside the app and 
functioned beautifully with the CFCs in the web services directory.

Hope this helps the next soul that stumbles upon this problem. 


>*       Have
>you tried downing your instance and blowing away the contents of both
>your cfclasses and cfc-skeletons directories.....
>
> 
>
>Yup - tried it many times, no luck... 


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:352048
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to