[jboss-jira] [JBoss JIRA] Resolved: (LOGMGR-20) Resource lookup cascades to parent loggers even though parent loggers will never have resources
David Lloyd (JIRA)
jira-events at lists.jboss.org
Fri Aug 13 12:38:49 EDT 2010
[ https://jira.jboss.org/browse/LOGMGR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Lloyd resolved LOGMGR-20.
-------------------------------
Resolution: Done
> Resource lookup cascades to parent loggers even though parent loggers will never have resources
> -----------------------------------------------------------------------------------------------
>
> Key: LOGMGR-20
> URL: https://jira.jboss.org/browse/LOGMGR-20
> Project: JBoss Log Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: core
> Affects Versions: 1.2.0.CR4
> Reporter: David Lloyd
> Assignee: David Lloyd
> Fix For: 1.2.0.CR5
>
>
> The fix for LOGMGR-17 implies that resource bundles can't be inherited from parent loggers (which makes sense considering that parent loggers can go away at any time). Stop wasting time (a lot of time) creating parent loggers only to have them immediately GC.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list