Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-2298

Patch commons-logging so that Jasper doesn't use a deployment's logj4.jar when compiling a JSP in that deployment

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 4.3.0.GA_CP07
    • 4.3.0.GA_CP03
    • Other
    • None
    • Release Notes

    Description

      If a deployment (e.g. a WAR) packages its own log4j.jar then Jasper will use that log4j.jar when compiling the deployment's JSPs. This can cause unexpected behavior. Jasper should use JBoss' log4j.jar.

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. JBAS-7120 Patch commons-logging so that Jasper doesn't use a deployment's logj4.jar when compiling a JSP in that deployment

          • 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.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-3332 Patch commons-logging so that Jasper doesn't use a deployment's logj4.jar when compiling a JSP in that deployment

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Support Patch - A one-off patch related to a customer support case, provided by Support and not Engineering JBPAPP-2231 Patch commons-logging so that Jasper doesn't use a deployment's logj4.jar when compiling a JSP in that deployment

          • 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

          Activity

            People

              rhn-support-jawilson Jimmy Wilson
              rhn-support-jawilson Jimmy Wilson
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: