basic feature of how Java works. Normally, you don't have multiple class loaders of course so you never notice.I dont think the above is correct for J2EE Environment. Once the Class loads, its stays loaded...
That's exactly what I said: you don't normally have multiple class loaders.
I think this is why we have "HOT LOAD" features to "RE LOAD" classes in development environment.
Not all J2EE environments support 'hot load'.
I think there might be some mis-understanding above...loaders. Why does it use multiple class loaders? Because we want CF to dynamically recompile and reload classes.
Yes, you are misunderstanding me.
I am just using CFMX as an interface... The manipulation in done in the Java
Class.
I know that.
Again this works in Regular CF Page, am only having problems when i move
the code to a CFC.
Yes, and I've explained why: to allow CFC instances to be stored in shared scopes but still have new versions compiled and loaded - hence allowing two different versions of the class to be loaded into memory at the same time - CF uses multiple class loaders. Your Java class gets loaded into whichever class loader controls the CF code that creates the Java object.
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
