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

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

      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.

        1. build.log
          88 kB
        2. commons-logging-1.1.0-jboss.diff-ur.patch
          4 kB
        3. commons-logging-1.1.0-jboss-cltestscommented.patch
          8 kB
        4. commons-logging-1.1.0-jboss-cltestsworking_use_tccl_true.patch
          26 kB
        5. commons-logging-1.1.0-jboss-cltestsworking.patch
          26 kB

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

              Created:
              Updated:
              Resolved: