Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-9572 Upgrade JBoss Pojo Cache to 3.0.1
  3. JBPAPP-9198

jbosscache-pojo.jar/META-INF/pojocache-aop.xml does not declare a namespace

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.2
    • AOP
    • None
    • Release Notes
    • Low
    • Hide
      Previously, JBoss Pojo Cache's pojocache-aop.xml was missing a namespace on the <aop> tag. Consequently, if jbosscache-pojo.jar was packaged in a location scanned by deployment scanners, the JBossXBRuntimeException was thrown. The namespace has been added to the <aop> tag and the JBossXBRuntimeException is no longer thrown in this scenario.
      Show
      Previously, JBoss Pojo Cache's pojocache-aop.xml was missing a namespace on the <aop> tag. Consequently, if jbosscache-pojo.jar was packaged in a location scanned by deployment scanners, the JBossXBRuntimeException was thrown. The namespace has been added to the <aop> tag and the JBossXBRuntimeException is no longer thrown in this scenario.
    • Documented as Resolved Issue
    • NEW

      <aop> ... </aop>

      should be

      <aop xmlns="urn:jboss:aop-beans:1.0">

      Without that if the jar ends up in a deployment, and a deployer scans the file, JBossXB barfs as shown in the forum thread.

      Original community JIRA: https://issues.jboss.org/browse/PCACHE-84

              rhn-support-dereed Dennis Reed
              tfonteyn Tom Fonteyne (Inactive)
              Eva Kopalova Eva Kopalova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: