I swapped out the JBoss supplied log4j.jar with log4j-1.5-rc1.jar and it all works well now. I'm thinking that maybe the dom4j that jboss ships with had a corrupt jaxen file maybe?
This is under jboss 3.2.5, system starts up fine, and my test ear file deploys properly (it's an mbean that parses then executes an xpath using jdom) So maybe the 'fix' for this is just to include a more current dom4j in jboss 3.2.6. Hopefully dom4j will be final before 3.2.6 is (just so people don't freak about a rc1 being in jboss) fyi, setting ear deployer to Isolated and CallByValue (both set to true) doesn't solve the problem. I suspect it really has to do with ServerLoader loading the class. I'm not super familure with what REALLY goes on in ServerLoader, but I would imagine that any of the jboss/lib files (toplevel lib) may be non-overridable due to them needing to be loaded as part of the bootstrap phase. I could be COMPLETELY wrong on that though. I'll go try all this with my real application now and report back if anything werid comes up. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842876#3842876 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842876 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
