[ https://jira.jboss.org/jira/browse/JBTM-595?page=com.atlassian.jira.plugi... ] Jonathan Halliday commented on JBTM-595: ---------------------------------------- Patch does not include a LogFactoryInterface impl. Unlikely to be included in 4.8 if development is required. -- 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

[ https://jira.jboss.org/jira/browse/JBTM-595?page=com.atlassian.jira.plugi... ] David Lloyd commented on JBTM-595: ---------------------------------- LogFactoryInterface yields a AbstractLogInterface - how does one get from LogI18n to AbstractLogInterface? I confess this logging infrastructure is pretty baffling to me -- 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

[ https://jira.jboss.org/jira/browse/JBTM-595?page=com.atlassian.jira.plugi... ] David Lloyd commented on JBTM-595: ---------------------------------- I stuck with LogI18n initially because it was unclear how LogFactory can receive resource bundle information. I guess the key to solving resource bundles will indeed be some kind of nifty subclassing as we are limited to a single resource bundle instance per category. Would you consider simply moving to java.util.logging wholesale, and removing all the facade stuff completely? And by "you" I guess I mean "me", since it's my dumb idea. The only practical difficulty I see would be that I'd have to add a Level class so that you have DEBUG/TRACE instead of JUL's FINE/FINER/FINEST, but that's not too big a deal. The upside would be removing the dep on commons-logging and deleting a bunch of classes. At first glance I think the resource generation stuff would work OK with JUL. -- 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

[ https://jira.jboss.org/jira/browse/JBTM-595?page=com.atlassian.jira.plugi... ] Jonathan Halliday closed JBTM-595. ---------------------------------- Resolution: Done Opted to use LogManager as a non-i18n layer under the existing CLF as it simplifies integration. CLF will need architectural changes to support plugin of i18n capable log systems and it's not worth the hassle at this stage. May revisit once JBoss TAG produces i18n logging standards. -- 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