However, I will say that we found the problem. We were using a symlink in the path of the mapping, so in this example “path.to.Comp”, the mapping “path” used a symlink in it’s directory path. For whatever reason, Coldfusion would freak out at this and truncate the implements string to just the class name, not the entire package. While this is still irritating, at least I can tell what the difference is in the environments that it was working on and the ones where it wasn’t!

Apparently Adobe released a hotfix for CF that alters the way symlinks are processed. Here’s a blog post talking about how it affects include paths for cfms, not sure if it’s the same problem that affects cfc creation: http://devbox.computec.de/2009/07/coldfusion-8-and-symlinks-hell-awaits/

In your example, the Intf.cfc and Comp.cfc must live in the same directory, since you are able to use implements=”Intf”. Handy for an example, of course.

However, I have a component that implements an interface, and uses a coldfusion mapping to reference it like so: implements=”componentsroot.interfaces.Intf” where there is a mapping with the logical path /componentsroot that maps to a folder which contains a subfolder interfaces and that is where Intf.cfc lives.

All is well and good, except that if I execute the following lines of code:

on some CF instances (all of these identical in CF version) I would see this:
component path.to.Comp
implements componentsroot.interfaces.Intf
Whereas on others I see this:
component path.to.Comp
implements Intf
Note that the full path is not specified in the implements string. This is a huge problem when type checking, either as part of a cfargument or using isInstanceOf, since CF will not evaluate those two to be the same thing (must be a string match).

Any ideas?