BTW, hello-log4j.xml is missing from the Hello webapp in CVS. Also, where is DOMConfigurator? I realize it is deprecated in favor of JoranConfigurator, but it should be there for backward compatibility. I didn't see it in either log4j.jar or log4j-xml.jar (why does the latter jar exist, BTW?).
Jake
At 12:22 AM 1/20/2005 -0600, you wrote:
>At 05:10 PM 1/19/2005 +0100, you wrote:
> >At 12:51 AM 1/19/2005, Jacob Kjome wrote:
> >
> >>I think there is an error in the tiny-webapp docs because there is no more
> >>automatic configuration of non-default logger repositories in Log4j-1.3,
> >
> >That is correct.
> >
> >>which the tiny-webapp assumes.
> >
> >tiny-webapp does not assume that. I thought this was corrected earlier but
> >let me double check. I just removed ambiguous statements with regards to
> >automatic configuration of non-default logger repositories. CVS commit will
> >follow shortly (as soon as the CVS server comes back up).
> >
>
>Maybe I'm missing something. You are saying that, although there is no
>autoconfiguration of non-default logger repositories, if one provides the
>"log4j/configuration-resource" <env-entry>, then the repository will be
>configured with the specified config file, which would have to be in the
>default package in the classpath (presumably WEB-INF/classes of the
>webapp)? So, if I had this...
>
><env-entry>
> <description>URL for configuring log4j context</description>
> <env-entry-name>log4j/configuration-resource</env-entry-name>
> <env-entry-value>log4j.xml</env-entry-value>
> <env-entry-type>java.lang.String</env-entry-type>
></env-entry>
>
>Log4j would search this out using the thread context classloader so it
>could load the config file from a child classloader (the one from which the
>thread started). However, if the "log4j.xml" file didn't exist there (we
>forgot to put a custom one in WEB-INF/classes), the logger repository would
>be configured with one higher up the classloader tree (probably the same
>one used by the server to configure the default logger repository). So,
>one would need to take care to try to name the file something unique that
>wouldn't exist anywhere else in the classloader hierarchy, right? For
>instance, "hello-log4j.xml" as you have done in the hello sample
>webapp. Am I on track here?
>
>
>Jake
>
> >>Please correct me if I'm wrong about this.
> >
> >Please let me know if any ambiguous statements remain.
> >
> >>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]
> >
> >
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
