This was an oversight, and I'll correct it with the next update
(currently on hold until I finally get JiBX beta 4 out). It's a stupid
kind of legacy issue, since SOAPAction is basically unnecessary with
doc/lit web services, but it is still required to be present (with the
value an empty string) for WS-I compatibility.
- Dennis
Andrew Butchart wrote:
When I use JibXSoap as a client to a Axis (Message) Web Service - Axis complains that
the
HTTP header, SOAPAction is missing. I am not sure if this header is required by the
SOAP (and it doesn't seem to have much use) but
a facility where one could add HTTP headers to the outgoing SOAP message would be
useful.
Something like the SOAPContext.getSendHTTPHeaders() ?
For the moment I have just added a the line:
conn.setRequestProperty("SOAPAction","\"\"");
to the SOAPClient.call method just before the body of the HTTP request is set.
Cheers,
Andrew
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
jibx-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jibx-users
