[jbossts-issues] [JBoss JIRA] Closed: (JBTM-674) decouple jta/jtax logging

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

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

Jonathan Halliday closed JBTM-674.

    Resolution: Done

> decouple jta/jtax logging
> -------------------------
>                 Key: JBTM-674
>                 URL: https://jira.jboss.org/jira/browse/JBTM-674
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JTA, JTS
>    Affects Versions: 4.9.0
>            Reporter: Jonathan Halliday
>            Assignee: Jonathan Halliday
>             Fix For: 4.10.0
> The jtax code uses the jta module logger rather than having its own, unlike all the other modules. This requires the logging system to jump through hoops to manage the associated resource bundles properly. It's the only use case for such functionality in the logging layer. Requiring the log framework to support this corner case limits our ability to plug in alternative logging impls. It's also unnecessary and potentially undesirable. So, add a jtaxLogger and change the module log statements to use it. Then we can clean up CLF and logging initialization a bit.

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