Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-492

Maven POM uses incorrect stax-api dependency

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.5.7
    • Component/s: OXM, XML
    • Labels:
      None
    • Environment:
      Oracle Application Server 10g

      Description

      These POMs all reference the stax:stax-api:1.0.1 (groupId:artifactId:version) dependency for the 'jdk14-jdk15' profile.

      http://repo2.maven.org/maven2/org/springframework/ws/spring-ws-parent/1.5.6/spring-ws-parent-1.5.6.pom
      http://repo2.maven.org/maven2/org/springframework/ws/spring-oxm/1.5.6/spring-oxm-1.5.6.pom
      http://repo2.maven.org/maven2/org/springframework/ws/spring-xml/1.5.6/spring-xml-1.5.6.pom

      This stax jar file incorrectly includes the following classes:

      javax.xml.namespace.NamespaceContext
      javax.xml.namespace.QName

      When deploying on Oracle Application Server 10g, this will cause the following exception:

      Caused by: java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
              at com.sun.xml.bind.v2.model.impl.RuntimeBuiltinLeafInfoImpl.<clinit>(RuntimeBuiltinLeafInfoImpl.java:224)
              ...

      The work-around is to exclude the stax:stax-api:1.0.1 dependency and include the javax.xml.stream:stax-api:1.0-2 dependency. This jar file only includes classes in the javax.xml.stream package and does not include any extraneous packages or classes.

        Activity

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            patrick.crocker@gmail.com Patrick Crocker
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: