[jbossts-issues] [JBoss JIRA] Closed: (JBTM-675) support i18n enabled loggers directly in CLF

Jonathan Halliday (JIRA) jira-events at lists.jboss.org
Mon Feb 15 12:24:17 EST 2010

     [ https://jira.jboss.org/jira/browse/JBTM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Halliday closed JBTM-675.

    Resolution: Done

> support i18n enabled loggers directly in CLF
> --------------------------------------------
>                 Key: JBTM-675
>                 URL: https://jira.jboss.org/jira/browse/JBTM-675
>             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
> CLF was designed at a time when no 3rd party logging framework supported i18n, so it is structured such that the CLF always does the i18n and passes the processed message to the underlying log impl. These days some 3rd party loggers do i18n, so it would be nice if we could delegate message processing to them. This will require a bit of cleanup (e.g. remove multiple message bundles per logger requirement, which they typically don't support, see JBTM-674) and then a new factory arrangement so it can be configured and used.

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