[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

Oracle Application Server 10g


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


This stax jar file incorrectly includes the following classes:


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.

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Tue Oct 23 22:27:11 UTC 2018 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.