SaajSoapMessage does not work if content type includes parameters [SWS-32] about spring-ws HOT 4 CLOSED

Luke Hamaty commented

More info:
Apparently my runtime environment was picking up jboss-saaj.jar from JBoss 4.0.4GA. The Sun JWSDP 1.6 saaj.jar does not exhibit this behavior (it apparently strips the encoding= part on its own).
The jboss-saaj.jar also does not set the content type on the created response message, which causes similar problems in org.springframework.ws.transport.http.MessageHandlerAdapter#handle, with no easy fix.

So, this is really a SAAJ implementation compatibility issue, possibly peculiar to the JBoss implementation, and typical of the tiny details that bedevil WS standards!

Sorry for any confusion.

from spring-ws.

Arjen Poutsma commented

Yeah, SAAJ is part of the J2EE 1.4 spec, so your application server probably uses its own version.

Thanks for the fix! I will include it now.

With regard to the response message, I think I can fix that in the SaajSoapMessageContext#createSoapMessageInternal. Basically, we can just copy the content type from the request message, to make sure that the SOAP version stays the same.

from spring-ws.

Arjen Poutsma commented

Actually, the getVersion() check can be simplified and less fragile by always returning SoapVersion.SOAP_11, since SAAJ 1.2 is SOAP 1.1 only.

SAAJ 1.3 does require the Content-Header check, though.

from spring-ws.

Arjen Poutsma commented

The issue reported has been fixed, but unfortunately there are other problems with JBoss's SAAJ implementation.
See http://forum.springframework.org/showthread.php?t=26634 and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=86580

from spring-ws.