[jboss-jira] [JBoss JIRA] Commented: (JBLOGGING-47) Support EAP 5.1 in JBoss Logging 3

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/JBLOGGING-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589424#comment-12589424 ] 

David Lloyd commented on JBLOGGING-47:
--------------------------------------

The most likely fix here is to test for the existence of the method(s) required by JBoss Logging.  If not found, fall thru (in the EAP 5 case the log4j provider will be correctly chosen).

> Support EAP 5.1 in JBoss Logging 3
> ----------------------------------
>
>                 Key: JBLOGGING-47
>                 URL: https://issues.jboss.org/browse/JBLOGGING-47
>             Project: JBoss Logging
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 3.0.0.Beta4-jboss-logging
>            Reporter: Pete Muir
>            Assignee: David Lloyd
>
> If you try to use JBoss Logging 3 in EAP 5.1 you get
> Caused by: java.lang.NoSuchMethodError: org.jboss.logmanager.LogContext.getAttachment(Ljava/lang/String;Lorg/jboss/logmanager/Logger$AttachmentKey;)Ljava/lang/Object;
> 	at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:52)
> 	at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47)
> 	at org.jboss.logging.Logger.getLogger(Logger.java:2164)
> 	at org.jboss.logging.Logger.getLogger(Logger.java:2189)
> As the LogManager is too old. We should add a provider for older versions of LogManager

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira