Once you download log4j 1.3.x, you can find step by step instructions in
$LOG4J_HOME/examples/tiny-webapp/INSTALL.txt
where $LOG4J_HOME is the directory where you placed the log4j files.
I hope this helps,
At 04:59 PM 11/22/2005, Jacob Kjome wrote:
Quoting "Harp, George" <[EMAIL PROTECTED]>:
> Modify Jboss' log4j.xml would seem to be the easiest solution.
>
Unfortunately, it's not that simple if one is trying to use the Log4j-1.3
specific configuration rolling policies and such which don't exist in 1.2.
However, now that Log4j-1.3 has been made, for the most part, compatible with
1.2, you can use the old 1.2 config with 1.3. So, if Darshan is willing to do
that and/or go back to using Log4j-1.2.x, then problem solved.
Keep in mind there is one other issue here; separation of logger
repositories.
Or, even, separation of Log4j instances. The latter is problematic in JBoss
with its unified classloader. The former can be done using a
JNDIContextSelector repository selector. This exists in Log4j-1.3. So, each
app can have the ability to have separate configurations from the server while
using a single Log4j.jar provided at the server level. I would tend to go
this
route. Switch out JBoss' log4j version with Log4j-1.3. Sepecifiy the
selector
on the command line (sorry, can't remember the name of the -D parameter for
this ATM) when starting Log4j. You'll probably have to manually configure
Log4j for each separate logger repository, especially if the unified
classloader won't allow for child-first classloading (although I believe there
is supposed to be an option for this... but I've heard its a bit problematic).
Jake
--
Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
