At 12:21 PM 7/29/2005 -0500, you wrote:
>
>On Jul 29, 2005, at 11:43 AM, Curt Arnold wrote:
>
>Looking at the 1.2 code it appears that it already tries to just warn
>the user if it encounters a validation error. Is there a problem
>(other than a warning) that appears when there is non-ID value used
>for the name?
>
It would appear that you are correct. I just tested and got this in
Tomcat's stderr.log...
log4j:ERROR Parsing error on line 18 and column 101
log4j:ERROR Attribute value
"org.apache.catalina.core.ContainerBase.[Catalina].[localhost]" of type ID
must be a name.
However, I still get logging for the localhost logger, defined as....
<logger
name="org.apache.catalina.core.ContainerBase.[Catalina].[localhost]"
additivity="false">
<level value="INFO"/>
<appender-ref ref="LOCALHOST"/>
</logger>
I could have sworn that I had more problems than this before, but I guess
not. So, it looks as if this is not so serious as I had originally
thought. I think I saw the error a long while back and decided that i
shouldn't be using a config that gives me errors. Since then, this has
translated into "can't use XML for configuration in Tomcat using
Log4j-1.2.xx". I have been using builds of Log4j-1.3 for quite a while, so
I'm a bit out of practice with 1.2.xx.
Sorry for sounding the warning bells! In any case, maybe displaying a
"log4j:ERROR" is a bit much for something that doesn't actually cause any
problems? I would think WARN would be better, or even nothing at all if it
doesn't affect logging.
Jake
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
