[SWS-930] NoSuchMethodError when using Axiom 1.2.14 Created: 18/Dec/15  Updated: 11/Apr/16  Resolved: 11/Apr/16

Status: Closed
Project: Spring Web Services
Component/s: None
Affects Version/s: 2.2.4
Fix Version/s: 2.3.0

Type: Bug Priority: Minor
Reporter: Andy Wilkinson Assignee: Greg Turnquist
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The changes made for SWS-922 have resulted in Spring Web Services no longer working with Axiom 1.2.14. Specifically the move to using getSOAPMessage in place of the, deprecated in 1.2.15, getSoapMessage. IMO, it would be preferable to continue to use getSoapMessage and suppress the deprecation warning. This approach will make things compatible with Axiom 1.2.14 and 1.2.15.



 Comments   
Comment by Andy Wilkinson [ 18/Dec/15 ]

The problem can be reproduced by building against the Spring IO Platform. For example:

./gradlew clean springIoCheck -PJDK8_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0.jdk/Contents/Home -PplatformVersion=2.0.0.RELEASE --continue

You'll see numerous test failures in spring-ws-core, all with this underlying cause:

java.lang.NoSuchMethodError: org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPMessage()Lorg/apache/axiom/soap/SOAPMessage;
	at org.springframework.ws.soap.axiom.AxiomSoapMessageFactory.createAxiomSoapMessage(AxiomSoapMessageFactory.java:274)

Comment by Mark Diskin [ 18/Dec/15 ]

Also would make sense to current axiom 1.2.16 (not 15)

Comment by Greg Turnquist [ 11/Apr/16 ]

Changed release version.

Generated at Sat Dec 16 18:40:56 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.