Resolution: Works as Designed
Affects Version/s: 1.5.6, 1.5.9
Fix Version/s: None
Environment:Unix, Windows, JVM 1.6.x, Weblogic 10.3
This problem is similar to the one raised at https://jira.springframework.org/browse/SWS-497. However, I do believe that the issue is caused by Spring, not JDOM. Since I couldn't track the problem down in the Spring-WS source code, my opinion is based on the outcome of a 'trial and error' exercise.
Here is the exception I'm getting:
I carried out a number of tests in the Weblogic 10.3 container against a Spring-WS SOAP service. I initially thought that the problem is caused by the javax.xml.soap.MessageFactory setting in JVM. However, I couldn't get satisfactory results after experimenting with various implementation.
Fortunately, I discovered that the problem can be fixed by declaring the following Spring bean amongst the others in my application:
Moreover, when I swap the configuration with an alternative one, for example:
... the problem is apparent again. It is happening regardless of having JVM started with -Djavax.xml.soap.MessageFactory=weblogic.xml.saaj.MessageFactoryImpl. Changing the javax.xml.transform.TransformerFactory JVM setting doesn't help either.
The evidence I presented above clearly indicates that Spring is doing something under the hood that somehow affects the JDOM functionality.
I replicated the problem in Spring-WS 1.5.6 and 1.5.9 and haven't tested the versions in between.