: [EMAIL PROTECTED]
Subject: RE: Property Configurator
Hi Donald
Thank you very much for your suggestions. I tried approach # 2 but it did
not work. So I tried setting the other attribute ( false ) But no luck
I like the Solution #1 too. But I tried it using war file and using
jboss-web.xml.
jboss
s a benefit; some as, umm, not.
>
> Anyway, If you wish to force jBoss to behave a bit
> more like most J2EE
> containers (and therefore avoid the whole property
> configurator bit) you can
> try the following approaches...
>
> ASSUMPTIONS:
>- You are using jBoss v3.2.
as a benefit; some as, umm, not.
Anyway, If you wish to force jBoss to behave a bit more like most J2EE
containers (and therefore avoid the whole property configurator bit) you can
try the following approaches...
ASSUMPTIONS:
- You are using jBoss v3.2.x
- You are interested in using log4j
Hi
I have a J2EE application and we use log4j for
logging. We used log4j.properties files and packaged
it in a war under WEB-INF/classes. It all worked fine
under Weblogic, Tomcat etc.
But now when we migrated to JBoss it has its own
log4j.xml file. So our application grabbed it as the
first one
