[jboss-dev] Logging (AS 5.1 Component Project Schedule)

[David M. Lloyd]

I've added a JDKLevel class to jboss-logging-log4j with mappings for JDK 
levels.  This way, people can specify JDK logging levels in their log4j.xml 
like this:

    <priority name="FINER" class="org.jboss.logging.log4j.JDKLevel"/>

I only put it in trunk though (new feature).  This module probably wants a 
2.1 release in general though - it looks like there's a lot of fixes which 
are missing from the 2.0 branch.

- DML

On 02/20/2009 10:14 AM, David M. Lloyd wrote:
> Yes, the code can go away.  The log levels are the same but different - 
> the bridge component automatically creates log4j level objects for the 
> JDK logging objects (so FINE is logged as FINE, etc).  The numeric value 
> selected for the mapped level is based on a mapping that is very similar 
> to what you list in the document though.  The only differences are that 
> SEVERE is always logged similarly to ERROR, CONFIG is logged at a level 
> halfway between DEBUG and INFO, and FINER is halfway between TRACE and 
> DEBUG.
> 
> - DML
> 
> On 02/20/2009 07:54 AM, Stan Silvert wrote:
>> Facelets uses JDK logging as well, but it doesn't ship with AS.  
>> However, because it is so common, I have bridge code in there to 
>> handle Facelets loggers in the same manner as JSF.
>> So all the code for the logging bridges can go away now?
>> Will the mapping of log levels between Log4J and JUL remain the same 
>> as specified here? http://www.jboss.org/community/docs/DOC-10379
>>
>> Stan
>>
>> David M. Lloyd wrote:
>>> On 02/19/2009 01:34 PM, David M. Lloyd wrote:
>>>> On 02/04/2009 01:50 PM, Jason T. Greene wrote:
>>>>> Project Leads,
>>>>>
>>>>> The next planned AS release is 5.1 Beta which we are targeting for 
>>>>> a March release, and a following GA in April (provided no major 
>>>>> problems).
>>>>
>>>> Here's the deal with logging.
>>>>
>>>> From a features perspective, there's two major pieces being 
>>>> developed. The first is getting JDK logging integrated nicely with 
>>>> the rest of the AS.  This feature will be done for 5.1 *no matter 
>>>> what* - this week if I can help it - and it will involve a "fixed" 
>>>> JDK logmanager as well as a JDK-log4j bridge component.
>>>
>>> This part is done.  If you have components using JDK logging (JSF is 
>>> the only one I know of for sure), please make sure everything looks 
>>> right, and bask in the awesomeness of having your logging work - 
>>> finally :)
>>>
>>> - DML
>>>
>>
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development