#1 is fairly simple. As long as you have a way to set log4j.configuration as a system property, you should be able to use log4j from anywhere, portably. Of course, each server has it's idiosyncracies as to how it uses log4j (categories, trace-level extensions, etc). You may want to look at jakarta-commons-logging. It's basically a veneer on top of different logging implementations. You may never have total portability, since it's not part of j2ee spec.
#2 is a different story. Many have asked about application-level log4j configs, a few have claimed they have done it, but I have yet to see anyone offer a working example. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822258#3822258 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822258 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
