Uploaded image for project: 'JBoss Logging'
  1. JBoss Logging
  2. JBLOGGING-47

Support EAP 5.1 in JBoss Logging 3

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 3.0.0.CR1
    • 3.0.0.Beta4-jboss-logging
    • None
    • None

    Description

      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

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBLOGGING-57 Logic for selecting a provider is too fragile

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBLOGGING-70 JBoss LogManager detection is still incorrect

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Feature Request - Feature requests from customers and/or users JBLOGGING-58 Support setting the logging provider explicitly

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              dlloyd@redhat.com David Lloyd
              pmuiratbleepbleep Pete Muir (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: