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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:247583
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
