I don't see any problem with the code. Can you send your SOAP request
thru tcp mon and send us the request soap message together with http
headers (of course u can remove sensitive information, if any :) )

BTW, why did u explicitly disable MTOM ? Does this message contains
attachments ?

-- Chinthaka

Sebastian Szczygiel wrote:
>> 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-----
> From: Eran Chinthaka [mailto:[EMAIL PROTECTED]
> Sent: Montag, 8. Mai 2006 15:11
> To: [email protected]
> Subject: Re: [Axis2] Operation Not found .. and WSA Action = null
> 
>  
> 
> 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
> 
>  
> 
>  
> 
> Sebastian Szczygiel wrote:
> 
>> 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
> 
>>
> 
>> 
> 
>>
> 
>  
> 
>  
> 


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to