Honestly, I couldn't understand what you were getting at in your examples, so I didn't read to far into them.
In fact, more often than not, I really am not sure what you are trying to communicate. As far your examples that show calling private and protected methods, quite frankly I think that that is a relatively irresponsible way to develop, when you are breaking severe rules of a programming language. You are right, JavaLoader, or any other ClassLoader based system will not work when calling those methods, because they should not work, nor is there any reason for them to. Anyway, this conversation has gone on long enough, I think. Mark On 7/25/06, Dan Plesse <[EMAIL PROTECTED]> wrote: > Mark, > > 95% of my post where scenarios in which the classes where not working > using the javaloader.cfc. And I do all my work using this classpath.cfc as a > foundation and nothing breaks. Did you at least try to run some of tests and > see for yourself that the cfc was not working with the scenarios I listed? I > provided you with three examples the forName() test, JDBC and JWS. How did > they function on your computer and inside the datasource manager? Those are > the scenarios which did not work. They are not small scenarios either. JDBC > plays is a big part with Coldfusion. I also found out that the classes > persist without scoping. The cfc didn't have any persistance by deault which > I think is good thing to have.. > > Dan -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:247585 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
