[jbossts-issues] [JBoss JIRA] Closed: (JBTM-676) remove direct access to ResourceBundle in *Logger classes
Jonathan Halliday (JIRA)
jira-events at lists.jboss.org
Tue Feb 16 06:06:10 EST 2010
[ https://jira.jboss.org/jira/browse/JBTM-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Halliday closed JBTM-676.
----------------------------------
Resolution: Done
> remove direct access to ResourceBundle in *Logger classes
> ---------------------------------------------------------
>
> Key: JBTM-676
> URL: https://jira.jboss.org/jira/browse/JBTM-676
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Common
> Affects Versions: 4.9.0
> Reporter: Jonathan Halliday
> Assignee: Jonathan Halliday
> Fix For: 4.10.0
>
>
> The per-module loggers should not allow code to directly access the ResourceBundle. Instead of fooLogger.messages.getString("key") users should call fooLogger.loggeri18n.getString("key") which allows the Logi18n impl to e.g. provide a default key in key not found situations instead of falling over horribly. It also allows for more flexible ResourceBundle handling implementation because it's abstracted via the Logi18n.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues
mailing list