I was using JRat to profile a JEE application in weblogic. I struck issues with an XSL-FO component. It appears to define classes with no explicit class name. Whilst the java.lang.ClassLoader class has deprecated
the defineClass method without a name the other defineClass methods seem to allow a null to be passed: "name - The expected binary name of the class, or null if not known" It seems to the be case for JDK 1.5 and 6.
This was causing JRat some NPEs around the JVMTI stuff. I patched the JVMTI classes to check for the null and after this it worked fine. This issue was listed under the JRat forum:
failed to transform : null ernitingoel 0 2008-06-04 18:56
Also under Weblogic it appears you need to always exclude weblogic.management.* This will resolve another issue on the forum:
Stack Dump with BEA nobody 0 2007-11-29 00:03
Log in to post a comment.