Hi Ceki,
See comments below...
At 11:52 PM 12/16/2004 +0100, you wrote:
<snip>
>Second, before strongly pushing for wide-spread use of >ContextJNDISelector, we should make sure it works perfectly. For >instance, we should check that loggers created by the application >server, e.g. Tomcat, and those created by the web-application are >always created using the correct repository. Since the order in which >classes are loaded into memory may influence (it should not but you >never know unless you check) the choice of ContextJNDISelector, we >must check that class static loggers as well as instance loggers are >attached to the correct repository. >
Is this is in partial reference to the email I sent out earlier today about "logger duality"? If not, could you read that message and respond? I'm not 100% sure of my theory, but there does seem to be a problem. Do you have any thoughts about how we might avoid the case I mentioned in said email? I'll copy it here for easy reference...
... ... log4j:INFO Creating new logger [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/myapp]] in repository [default]. ... ... log4j:INFO Creating new logger [org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/myapp]] in repository [myapp]. ... ...
Jake
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
