I read the 4.0 docs (every single one of them) trying to resolve my classloader issue with 4.0.1SP1.
It has a very clear and well written section (a bit hard to find, but it is there) on how to configure 4.0.1 for J2EE 1.4 compatibility and "separate classloading". Unfortunately, when I followed the instructions and deployed a test EAR that works on 3.2.3 and contains a different version of log4j.jar and commons-logging.jar from the one in jBoss, it experienced a conflict - a clear failure to isolate the class loading. Note that the test app did not even use log4j, it just had the jars present in web-inf/lib. This is the kind "documentation out of date" issues that I was referring to. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869226#3869226 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869226 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
