|
> Are you using code gen'ed stuff or ServiceClient
api ? I’m using ServiceClient API. > How did you switch SOAP 1.1 and SOAP 1.2 ? Using the setSoapVersionURI method. > Can we see your client code ? Yes, here it is: Options options = new Options(); options.setSoapVersionURI(SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI); options.setTo(new EndpointReference(SOAP_ENDPOINT)); options.setProperty(Constants.Configuration.ENABLE_MTOM,
Constants.VALUE_FALSE); options.setTransportInProtocol(Constants.TRANSPORT_HTTP); options.setAction("process"); ServiceClient sender = new ServiceClient(); sender.setOptions(options); sender.sendReceive(root); -----Original Message----- Are you using code gen'ed stuff or ServiceClient api ? How did you switch SOAP 1.1 and SOAP 1.2 ? Can we see your client code ? -- Chinthaka > Hello, > > > > I’m still trying to send MTOM attachments. Because until now I
haven’t > fixed my "Invalid Content Type Field in the Mime
Message" problem (see > previous post) I have disabled MTOM optimization. > > > > But here comes the next problem, if I use SOAP 1.2, I get: > > > > AxisFault: Operation Not found EPR is http://localhost:8081/...
and WSA > Action ="" null > > > > No problems if I switch to SOAP 1.1 on client-side. > > > > What do I have to do, or what is missing to make my client-code
SOAP 1.2 > compatible? > > > > Regards, > > Sebastian > > > |
- [Axis2] Operation Not found .. and WSA Action = null Sebastian Szczygiel
- Re: [Axis2] Operation Not found .. and WSA Action... Eran Chinthaka
- RE: [Axis2] Operation Not found .. and WSA Action... Sebastian Szczygiel
- Re: [Axis2] Operation Not found .. and WSA Ac... Eran Chinthaka
- RE: [Axis2] Operation Not found .. and WSA Action... Sebastian Szczygiel
- Re: [Axis2] Operation Not found .. and WSA Ac... Eran Chinthaka
