It's at least as simple (I'd say simpler) to include the compiled classes on the filesystem in the same directory as your CF files, and use a URLClassLoader to load them. Still no need for access to the classpath, it's just as easy to install the app, and no messing with having to encode your classes and all that rot (which makes building a lot easier).

Barney, I don't disagree with you at all. But, consider my business: selling easy-to-use-but-still-somehow-powerful components to developers of all skill levels. I know, without a doubt, that you and Pete could easily handle moving some class files arround. I can't say that for everyone else. (I speak from experiance.) Besides, there's the "how'd they do that?!?" effect. Oh, and if you implement all your code in Java, but create a CF facade and imbed your java classes inside that CFC, you can prevent decompiling... sorta. :)

Anyhow, I'm not saying we should use it. I'm just saying it works.

Doug