You can tell which version(s) of SOAP the service supports by looking at the namespace for the SOAP WSDL binding extensions, e.g. what's the namespace bound to the "soap" prefix for the <soap:body use=<literal"/> definition.
The WSDL should fully define the supported bindings for the service, and you should be able to generate a stub from the WSDL, which should generate a valid message for you.
But I'm highly suspect of the service if it can't handle a SOAPAction HTTP header.
Anne
On 5/17/06, Roy <[EMAIL PROTECTED]> wrote:
Yes I have noticed that in SOAP v1.1 this is a mandatory field in Http Header. If i generate the code by using the attribute in wsdl2Javathat changes the SOAP version to 1.2 will i have an effect? I saw in the SOAP 1.2 specification that the SOAPAction field is optional.
If this doesn't work how can i change the header before i send the call request?Can you please tell me a way to do this?
Thank you
Roy
Anne Thomas Manes < [EMAIL PROTECTED]> έγραψε:It's not a valid SOAP 1.1 over HTTP message if you omit the SOAPAction header. Axis will not permit you to generate an invalid message. You will have to intercept the message after it leaves Axis and remove the header.
On 5/17/06, Roy <[EMAIL PROTECTED]> wrote:Hello,
I am using AXIS to call a web service with a static stub client.I have a problem with the HttpHeader generated from AXIS. I want to omit completely the SOAPAction field because the web service i want to call isn't able to understand this field. I have have set the SOAPAction value to "" but i had the same results. How can i remove it completely?
Thank you.
Χρησιμοποιείτε Yahoo!
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων
http://login.yahoo.com/config/mail?.intl=gr
Χρησιμοποιείτε Yahoo!
Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων
http://login.yahoo.com/config/mail?.intl=gr
