Would the RepositorySelector solve the problem of not being able to control the log4j properties in your web application separately from the jboss server(I'm talking about in separate files. I know how to use one log4j.properties file for everything and just change the thresholds based on category, not as elegant). I am guessing not as JBoss has to use the same context so that your web application can use the container made by JBoss.
Chris ----- Original Message ----- From: "Ceki Gülcü" <[EMAIL PROTECTED]> To: "Log4J Users List" <[EMAIL PROTECTED]> Sent: Friday, January 11, 2002 6:25 AM Subject: Re: multiple components using log4j causes problems > > This is a very serious problem. The new log4j API allows the main > program to install a RepositorySelector which can control the > hierarchy to be used depending on the context, for example depending > on the enterprise application. However, this requires support from the > application server because only the application server (e.g. JBoss) > controls the context. > > In short log4j has the required pluggable interface, the application > server writers need to jump on the wagon. I suggest that you mention > the problem to the JBoss people also mentioning the new RepositorySelector > API in log4j. > > At 00:15 12.01.2002 -0800, Aron Kramlik wrote: > >Hi! > > > >We are coming across a bit of a problem where more and more third party > >libraries and applications are using log4j for their logging. The problem comes > >when JBoss or OpenJMS and third party libraries are all doing their initialisation > >of log4j and we need to as well when we deploy our components. > > > >Have other faced this problem? What are the suggested practices for this? > > > >Thanks. > > > >Aron. > > > >[EMAIL PROTECTED] > >iTouch Australia > > -- > Ceki Gülcü - http://qos.ch > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
