karanmg, I used the approach you mention in some of my tests. It seemed to work for isolating log4j, but did nothing for keeping EARs separate from each other.
Redefining the problem one more time: I need total isolation of the contents of the EAR (like J2EE 1.4), including the logging. That way everything needed can be in the EAR, the EAR can be deployed to ANY version of the server, any server vendor, and logging is configured in the EAR and utterly independent. jBoss "claims" to allow this and there are some instructions - like the one referenced - that solve part of the problem. But I have yet to find a single set of instructions that solves the problem "completely". At our company we are getting very close to dumping jBoss and declaring it unsupported because of this issue. A sad situation, since our focus is on open source. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870254#3870254 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870254 ------------------------------------------------------- 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
