I do use this setting as part of the settings to obtain J2EE 1.4 compatibility and get pretty decent isolation between the stuff in your EAR and the jBoss logging.
I think the full configuration is described in either 4.01 or 4.02 release notes, even though the docs do have an error and I don't remember the exact one - just be sure to compare the config files mentioned with the config files from version 4.0.0. A nuisance, but it is the only way to get the real setup. But no. The change I was talking about was a change the jBoss guys did to their code and that finally fixed the logging issues. I think the log4j problem was originally inherited from Tomcat (which is part of jBoss). And I am not sure, but it is quite possible that you have to configure for J2EE 1.4 compatibility (as I mentioned above I am already doing that). It is also possible that you have to use an EAR file instead of just a WAR. I know I am not giving you many answers... but I hope this gets you investingating in the right direction. I can just say that "for the configuration I am using (EAR, full J2EE 1.4 compatibility)" the log4j/jBoss problem is fixed... and a new similar one regarding Hibernate showed up :P Good luck. Bruno Melloni Director of Software Architecture Akuratus Corporation 1333 N. Stemmons Fwy, Suite 110 Dallas, Texas 75207 Phone: 469.227.0920 Fax: 469.227.0967 [EMAIL PROTECTED] www.akuratus.com >>> [EMAIL PROTECTED] 6/6/2005 12:33:50 PM >>> Bruno, Is this the change you are talking about in JBoss 4.0.2? http://jira.jboss.com/jira/browse/JBAS-1691 Looks like they decided to default to child-first classloading with options to allow for parent-first delegation for specified packages. -Mark > -----Original Message----- > From: Bruno Melloni [mailto:[EMAIL PROTECTED] > Sent: Friday, June 03, 2005 5:19 AM > To: [email protected] > Subject: Re: log4J and JBoss > > Depends on the version of jBoss that you use. Try jBoss 4.02. If it > doesn't break any of your other technologies (it is incompatible with > some things), then you are in business... because they fixed their > logging problems in 4.02. > > Bruno Melloni > Director of Software Architecture > Akuratus Corporation > 1333 N. Stemmons Fwy, Suite 110 > Dallas, Texas 75207 > Phone: 469.227.0920 > Fax: 469.227.0967 > [EMAIL PROTECTED] > www.akuratus.com > > >>> [EMAIL PROTECTED] 6/3/2005 2:43:01 AM >>> > Hi, > > Is it possible to use log4j within my code independently of JBoss > logging? Apparently when I run JBoss I stop receiving my own logs. > > environment: JBoss 3.2, Eclipse 3.0, jdk 1.4, log4j 1.2.9, ant and > xdoclet 1.2.1 > > thanks! > > Fabien > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
