From 419d51e0af45aaae469f634dc9002f48756c791a Mon Sep 17 00:00:00 2001
From: Arjen Poutsma
- NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
+NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
Most often, this exception is related to an older version of Xalan being used. Make sure to upgrade @@ -118,15 +118,15 @@
* = See below. -
-** = See below. -
+* = See below.
+** = See below.
+*** = See below.
Additionally, Java SE 6 includes SAAJ 1.3.
@@ -136,13 +136,13 @@If you get the following stack trace:
- org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.ws.soap.saaj.SaajSoapMessageFactory' 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;
+org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.ws.soap.saaj.SaajSoapMessageFactory' 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
@@ -164,14 +164,14 @@
- Weblogic 9 has a known bug in the SAAJ 1.2 implementation: it implement all the 1.2 interfaces,
+ WebLogic 9 has a known bug in the SAAJ 1.2 implementation: it implement all the 1.2 interfaces,
but throws UnsupportedOperationExceptions when you call them.
Confusingly, the exception message is This class does not support SAAJ 1.1, even though
it supports SAAJ 1.1 just fine; it just doesn't support SAAJ 1.2.
See alsothis BEA forum post.
- Spring-WS has a workaround for this, we basically use SAAJ 1.1 only when dealing with Weblogic 9.
+ Spring-WS has a workaround for this, we basically use SAAJ 1.1 only when dealing with WebLogic 9.
Unfortunately, other frameworks which depend on SAAJ, such as XWSS, do not have this workaround.
These frameworks happily call SAAJ 1.2 methods, which throw this exception.
+ Weblogic 10 ships with two SAAJ implementations. By default the buggy 9.x implementation is used + (which lives in the package weblogic.webservice.core.soap), + but there is a new implementation, which supports SAAJ 1.3 + (which lives in the package weblogic.xml.saaj). + By looking at the DEBUG logging when Spring Web Services starts up, you can see which SAAJ + implementation is used. +
+
+ To use this new version, you have to create a message factory bean like so:
+