[SWS-492] Maven POM uses incorrect stax-api dependency Created: 09/Mar/09  Updated: 04/May/12  Resolved: 12/May/09

Status: Closed
Project: Spring Web Services
Component/s: OXM, XML
Affects Version/s: None
Fix Version/s: 1.5.7

Type: Improvement Priority: Major
Reporter: Patrick Crocker Assignee: Arjen Poutsma
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
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.



 Comments   
Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Fri Dec 15 06:38:35 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.