Copy link to clipboard
Copied
I'm getting a "Could not find the ColdFusion component or interface" error when I try to invoke the feed or http CF methods, for example:
localtest.httpService = new http();
Results in the error, "Cold not find the ColdFusion component or interface http"
I have two CF 9 instances running on the same box (Windows Server 2008), both running the latest hotfix (hot fix 2). Both instances throw the same error. I have another separate server running CF 9 (doesn't have hotfix 2 installed) and it can run the code just fine. I'm assuming that feed() and http() are defined in an Adobe ColdFusion cfc in the CFIDE directory somewhere, but I don't know which one as they are encrypted.
When you say "mapped" do you mean "with a CF mapping"? If so, what's the mapping, and to where?
On my CF9 install, I've got a custom tag path defined, which points to the cfusion/customTags dir, which in turn contains the com/adobe/coldfusion dir, which is where those CFCs are. This is the out-of-the-box config.
Because of the custom tag path being defined, any files within that subdir structure can be addressed without any further pathing, eg as:
new http()
A mapping to CFIDE won't help you, becaus
...Copy link to clipboard
Copied
ok - apparently the problem is bigger than this and it appears to be related to CF just not be able to find it's own components. For example, all of these produce the same component not found error:
createObject("component", "pop")
createObject("component", "query")
createObject("component", "http")
etc.
The CFIDE directory is mapped in the CFadmin (correctly), so I don't know why CF can't find these built-in components when using createObject or the new object syntax as noted in the original thread posting.
Copy link to clipboard
Copied
When you say "mapped" do you mean "with a CF mapping"? If so, what's the mapping, and to where?
On my CF9 install, I've got a custom tag path defined, which points to the cfusion/customTags dir, which in turn contains the com/adobe/coldfusion dir, which is where those CFCs are. This is the out-of-the-box config.
Because of the custom tag path being defined, any files within that subdir structure can be addressed without any further pathing, eg as:
new http()
A mapping to CFIDE won't help you, because the files aren't in the CFIDE dir. And even then, say you had a mapping to cfusion/customtags called "/foo", you'd need to path the CFCs in your code:
new foo.com.adobe.coldfusion.http()
(or have an import statement preceding the new statement)
--
Adam
Copy link to clipboard
Copied
That was it! The CF9 install was missing its custom tag path to C:\JRun4\servers\LiLa\cfusion.ear\cfusion.war\WEB-INF\cfusion\CustomTags
Once I added the custom tag path through the CFadmin, it was good to go. Thanks!