Posted by chrizzz
on June 10, 2010 at 10:24 AM PDT
I'm trying to use JAX-WS on WebLogic 10.3 as a WS Client consuming a Web Service on a WebLogic 9.2 server.
The problem I have is that when I add an attachment part in a SOAPHandler, the JAX-WS implementation does not include a Start parameter in the Content-Type header. Apparently this should not be needed, but the WS implementation on the server seems to require it. Response message is:
"java.io.IOException: Could not parse SOAP message. Remaining stream ... javax.xml.soap.SOAPException: No start attachment specified in the Multipart/Related document"
There is no Content-Id on the SOAP part either.
User-Agent header says the JAX-WS version on WebLogic 10.3 (client side) is: Oracle JAX-WS 2.1.3-07/10/2008.
My question is: Does anyone know a workaround for this on the client side (WebLogic 10.3)?
Thanks in advance!