Ongoing MTOM issues
I am running a WebService on Websphere. When I access the WebService with SoapUI and use MTOM, then Websphere throws a SoapFault before it ever gets to my code. According to IBM, this is a SoapUI issue and not a Websphere issue:
I think there may be some subtle problem with the way soapui is composing the attachment. I took the customer's wsdl and code and from that built a service. I also built a client, but one that uses the jvm's reference implementation of jax-ws rather than soapui.
Using that client, I was able to send mtom attachments to the service and the service could demarshall them without a problem. The client contains a local copy of the wsdl with the port number shifted so a tcp-monitor can be used. I confirmed that attachments are being sent and not base-64 encoded.
Does anyone have any ideas?
Thanks
Ron
I think there may be some subtle problem with the way soapui is composing the attachment. I took the customer's wsdl and code and from that built a service. I also built a client, but one that uses the jvm's reference implementation of jax-ws rather than soapui.
Using that client, I was able to send mtom attachments to the service and the service could demarshall them without a problem. The client contains a local copy of the wsdl with the port number shifted so a tcp-monitor can be used. I confirmed that attachments are being sent and not base-64 encoded.
Does anyone have any ideas?
Thanks
Ron