On 12/16/05, Ben Nadel <[EMAIL PROTECTED]> wrote: > If you use a class loader to load a java class, does that class now live in > the ColdFusion memory space the way a class would if it's path was set in > the ColdFusion admin....
That's not entirely a straightforward question to answer because it depends on what the class loader actually does... However, classes generally live in a specific part of memory so, yes, it's much the same as adding a class to the class path (in this case if you use the CFMX class loader to load a Java class explicitly, it will be the same as if CFMX had loaded it implicitly) - however classes don't live in "the ColdFusion memory space" (I assume you mean the regular heap). Java memory management is pretty complex but Sun have a lot of documentation on how the various memory spaces all work (perm, eden, survivor etc). > if you use class loader, does it incur large > overhead everytime you load that javaclass? Or just the first time, the rest > being like built in java classes? Again, it depends on which class loader you use and how it's written. In general, I'd say don't worry about it... -- Sean A Corfield -- http://corfield.org/ Got frameworks? "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 words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
