[ 
https://issues.apache.org/jira/browse/OWB-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837809#action_12837809
 ] 

Paul J. Reder commented on OWB-300:
-----------------------------------

I'm not an expert at Commons logging so I may have missed something, but 
Commons logging does not currently appear to provide embedded support for NLS 
(one of the main things I've been working to add to OWB logging), and also does 
not appear to natively support args (they would have to be processed externally 
before the log call). This would require all the logs to be wrapped in 
.isXXXEnabled (basically requiring a wrapper of the wrapper) which is basically 
what we currently have with the WebBeansLogger that I've been enhancing.

My patch allows OWB to be packaged with a minimal set of jars (it uses the 
exsisting JUL support by default), and shows how the wrapper can be altered to 
make use of log4j. Other loggers (including the Commons Logger, if you want) 
can be enabled in similar fashion. This path allows our current OWB logging 
(with args) to work seamlesslessly, as well as allowing OWB to make use of 
resource bundles for NLS.

In the future, when Commons Logger natively supports args and NLS the 
ebBeansLogger can be removed and replaced with the Commons Logger.

> Currently OWB requires log4j for logging. This patch provides a means of 
> choosing other loggers.
> ------------------------------------------------------------------------------------------------
>
>                 Key: OWB-300
>                 URL: https://issues.apache.org/jira/browse/OWB-300
>             Project: OpenWebBeans
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: M4
>         Environment: All
>            Reporter: Paul J. Reder
>            Assignee: Gurkan Erdogdu
>            Priority: Minor
>             Fix For: M4
>
>         Attachments: OWBLoggerOnly.patch
>
>
> Currently OWB requires log4j for logging. This patch provides a means of 
> choosing other loggers. Notably, the patch switches the logging code to using 
> the JDK java util logging. The patch includes comments to show how to 
> maintain log4j use or use it as a model to enable other logging libs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to