Mark,
The one of the areas in which classloaders don't work is JDBC and more
importantly JDBC drivers types I - lV. Another area in which classloaders
don't work is using JWS to create new classes at runtime. for example
creating a new java embedded databases class using HSQLDB which is the
default database for the other J2EE servers BEA and IBM WebSphere. The other
issue is class persistence i.e. Classloader classes only exist on the page
that loaded the class. The other issue was saving objects to disk. Did you
try to work out any of these issues during your initial testing?
Is this better? Which part confuses you? How can I help you understand?
Please write down your questions
below this line. Thank you.
I thought we could just code talk but I guess not :(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:247727
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
