+ Spring Web Services works under Java 1.4, but it requires some effort to make it work. Java 1.4 is + bundled with the older XML parser Crimson, which does not handle namespaces correctly. Additionally, + it is bundled with an older version of Xalan, which also has problems. + Unfortunately, placing newer versions of these on the class path does not override them. + See + this FAQ + entry on the Xalan site, and also + this entry + on the Xerces site. +
++ The only solution that works is to add newer versions of Xerces and Xalan in the lib/endorsed + directory of your JDK, as explained in those FAQs. +
++ For some reason, Apple decided to include a Java 1.4 compatibility jar with their JDK 1.5. This jar + includes the XML parsers which were included in Java 1.4. No other JDK distribution does this, so it + is unclear what the purpose of this compatibility jar is. +
++ The jar can be found at + + /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/.compatibility/14compatibility.jar + + . + You can safely remove or rename it, and the tests will run again. +
+| Application Server | +SAAJ Version | +
|---|---|
| BEA WebLogic 8 | +1.1 | +
| BEA WebLogic 9 | +1.2 | +
| IBM WebSphere 6 | +1.2 | +
| SUN Glassfish 1 | +1.3 | +
Additionally, Java SE 6 includes SAAJ 1.3.
+If you get the following stack trace:
+
+ org.springframework.beans.factory.BeanCreationException: Error creating bean with name
+ 'org.springframework.ws.soap.saaj.SaajSoapMessageContextFactory#e4cb82' defined in ServletContext
+ resource [/WEB-INF/springws-servlet.xml]: Invocation of init method failed;
+ nested exception is java.lang.NoSuchMethodError:
+ javax.xml.soap.MessageFactory.newInstance(Ljava/lang/String;)Ljavax/xml/soap/MessageFactory;
+ Caused by:
+ java.lang.NoSuchMethodError:
+ javax.xml.soap.MessageFactory.newInstance(Ljava/lang/String;)Ljavax/xml/soap/MessageFactory;
+
+ + Like most J2EE libraries, SAAJ consists of two parts: the API that consists of interfaces ( + saaj-api.jar + ) and the implementation ( + saaj-impl.jar + ). + The stack trace is due to the fact that you are using a new version of the API (SAAJ 1.3), while + your application server provides an earlier version of the implementation (SAAJ 1.2 or even 1.1). + Spring-WS supports all three versions of SAAJ (1.1 through 1.3), but things break when it sees + the 1.3 API, while there is no 1.3 implementation. +
++ The solution therefore is quite simple: to remove the newer 1.3 version of the API, from the class + path, and replace it with the version supported by your application server. +
++ The &WSDL query parameter is a way to get a WSDL of a class. In SWS, a service is generally not + implemented as a single class, but as a collection of endpoints. +
++ There are two ways to expose a WSDL: +