That works perfectly. Now I can leave the
jboss/conf/tomcat/log4j.properties alone and encapsulate the app
specific log properties cleanly. I didn't use this code I used what
was mentioned in the log4 manual.
>I usually do something like this... put a log4j properties file in your
>application
Good point. H... Just a quick thought - what about writing your
own org.apache.log4.jspi.Filter that can somehow differentiate between
application deployements? That would give you a programatic hook that
is easily used from the log4j config file, however how the Filter could
differenti
I usually do something like this... put a log4j properties file in your
application e/j/war file, and somewhere in the initialization of the
application do this:
(sorry for the poor formatting)
private void init(){
ResourceBundle bundle = ResourceBundle.getBundle("com.kcp.sso.log4j");
>
>2) IMHO, what level gets logged and to where (file, rolling file,
>email, etc.) is very much a concern of the administrator of a site,
>moreso than the developer at that point.
>As an administrator with multiple apps to worry about, I would want
>centralized control over all logging of all d
1) Man, I can't wait till JBoss 3.2.3 comes out. It's going to kick
some serious butt.
2) IMHO, what level gets logged and to where (file, rolling file, email,
etc.) is very much a concern of the administrator of a site, moreso than
the developer at that point.
As an administrator with multip
Oops! I meant JBoss 2.4.2
>>I believe one of the changes from 2.2 to 2.4 was that 2.4 includes
>>log4j. What you're seeing is probably from a ClassCastException
>>where there are two copies of org.apache.log4j.Category - one in
>>your application and one in JBoss' lib/ext directory.
>
>Does th
>I believe one of the changes from 2.2 to 2.4 was that 2.4 includes
>log4j. What you're seeing is probably from a ClassCastException
>where there are two copies of org.apache.log4j.Category - one in
>your application and one in JBoss' lib/ext directory.
Does this mean that we are forced to use
I believe one of the changes from 2.2 to 2.4 was that 2.4 includes
log4j. What you're seeing is probably from a ClassCastException where
there are two copies of org.apache.log4j.Category - one in your
application and one in JBoss' lib/ext directory.
Try taking all log4j classes out of your app
I have a problem in JBoss2-4.4. I have several bean that use log4j to log
some aplication event. Thats beans work fine in JBoss-2.2, but when I try
to use JBoss-2.4.4 I get an error:
"java.rmi.ServerException: RemoteException occurred in server thread;
nested exception is:
java.rmi.ServerExcep
