Thanks, but that's just basic log4j stuff. Like a good person, I have a (fairly large) number of shared packages between my 2 web-apps - and I need the logging to be in the correct file depending one who's calling them (app1 or app2).
When I had this problem with straight Tomcat, I had to create separate wars with the log4j stuff in each (xml and jar). This, at least, allowed me total control over the logging for each one. This approach doesn't seem to work within the JBoss environment - I presume because the classloading causes the LoggingContext singleton to remain just that - a singleton! I think I need a way to force the log4j instances to sit within the war-file's classloader (and thus have a singleton for each war which will get found first) ... which is what I hoped would happen with the ' Using your own log4j.xml file' description on the wiki page. However, it would appear that this doesn't work as I can't override the LoaderRepository except in the 'top-level' (ie at the ear level) ... and I need it for each war. I have separated my app into an EJB jar and 2 wars, and deployed them separately - which seems a little more controllable using the filter - but I think I should be able to take these 3 standalone deployments and place them in an ear and get the same behaviour! Thanks for your suggestions so far. tim View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3842875#3842875 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3842875 ------------------------------------------------------- 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
