On Wed, 16 Jul 2003 15:58, Brian Wallis wrote: > This seems to result in ojdbc14 being loaded by two instances of > UnifiedClassLoader3. Once for the Class-Path entry in the EJB jar file > (3eec1a, addedOrder=22) and once because it is present in the deploy > directory (bc9673, addedOrder=0)
I've tried removing the Class-Path entry from the manifest and now I get only a single class loader for the class (as I suspected I would). Should having a Class-Path entry in the manifest cause the use of a new class loader instance? I wouldn't have thought so. brian... ------------------------------------------------------- This SF.net email is sponsored by: VM Ware With VMware you can run multiple operating systems on a single machine. WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the same time. Free trial click here: http://www.vmware.com/wl/offer/345/0 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
