You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Joe Bergmark (JIRA)" <ji...@apache.org> on 2010/04/27 21:48:34 UTC
[jira] Resolved: (OWB-364) Reduce the amount of info level logging
[ https://issues.apache.org/jira/browse/OWB-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bergmark resolved OWB-364.
------------------------------
Fix Version/s: 1.0.0
Resolution: Fixed
Closing this for now, will be happy to undo or discuss further if anyone has concerns about these two changes.
> Reduce the amount of info level logging
> ---------------------------------------
>
> Key: OWB-364
> URL: https://issues.apache.org/jira/browse/OWB-364
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Core
> Affects Versions: M4
> Reporter: Joe Bergmark
> Assignee: Joe Bergmark
> Priority: Minor
> Fix For: 1.0.0
>
>
> There is some info level logging that probably could be moved to debug level.
> Two ones that jump out during app startup and while driving requests are:
> 1) BeansDeployer defineManagedBean outputs for every class in the BDA. This could be a ton of output for complex applications. I think this could be moved to a level less than info without any major issues.
> 2) WebBeansPhaseListener before/after phase outputs two info level messages each time it is invoked. As this comes out per request, I feel it should definitely be moved to a level below info.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.