Max Rydahl Andersen wrote:
If it is for the spec then I would argue that the spec is very wrong since it will break all other kind of stuff. Like how will you convince all the external libraries hibernate uses to use your "magic" classloader ? (e.g. log4j, dom4j, cglib, yada, yada)
Thread.getContextCL() is the only way. If a library doesn't use Thread.getCCL() then it is a poorly written library. App server and J2EE in general require this because of classloader isolation (scoped ears or wars). If you are within Hibernate code and call Class.forName() it will use the classloader that loaded Hibernate to load the class. (read the javadocs) and you could get CCE, CNF exceptions. If you already know this, then apologies.
The same issues effect the loading of resources. Bill -- Bill Burke Chief Architect JBoss Inc. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
