Re: Issues with java.util.logging

That seems a lot more like it by the looks of things. Any idea on when 
3.0.20 is going to be released?

Andy

Scott Ferguson wrote:
> 
> On Jun 7, 2006, at 1:53 AM, Andy Yates wrote:
> 
>> I've had similar problems with the resin logging levels in that it 
>> just ignores any kind of sub declaration of logging. For instance I 
>> had the following levels setup:
>>
>> <log path='stdout:' timestamp='[%H:%M:%S.%s] '>
>>     <logger name="" level="info"/>
>>     <logger name="org.springframework" level="severe"/>
>>     <logger name="org.apache" level="severe"/>
>>     <logger name="uk.ac.sanger" level="fine"/>
>> </log>
> 
> The Resin 3.0.20 changes will allow/suggest a different configuration:
> 
>   <log path="stdout:" level="all" timestamp="[%H:%M:%S.%s] "/>
> 
>   <logger name="" level="info"/>
>   <logger name="org.springframework" level="severe"/>
>   <logger name="org.apache" level="severe"/>
>   <logger name="uk.ac.sanger" level="fine"/>
> 
> The <log> tag configures a log Handler.  In this case, it's the 
> destination for any active Loggers.
> 
> The <logger> tag configures the Logger.  So the latest <logger> is 
> equivalent to:
> 
>   Logger.getLogger("uk.ac.sanger").setLevel(Level.FINE);
> 
> I think this is closer to what you want to configure.
> 
> -- Scott
> 
> 
>