Hi Wes,
Sorry, I didn't express myself correctly, I mean the cxf soap binding jar,
the command line tools is ok, it included all the cxf jars.
when you run the wsdl2java in a maven plugin, you have to put the cxf
soap binding jar into your classpath,
otherwise wsdl2java will not generate the extra soap header as a
parameter even if you specify the 'exsh' argument
Regards,
James
James,
Thanks for your response.
Where can I find an example of the correct SOAP binding for one of these
extended SOAP header messages?
Wes
-----Original Message-----
From: James Mao [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 11, 2007 9:22 PM
To: [email protected]
Subject: Re: Adding headers to soap request
Gamble, Wesley (WG10) wrote:
What is the -exsh flag on wsdl2java supposed to do for you? What does
"Enables or disables processing of extended soap header message
binding." mean? How would I know the difference between a regular and
an extended soap header message?
As per the jaxws spec (2.6.2.1) The out of band soap headers are
optional to map to a parameter,
So in tools there's an argument "-exsh", if set to true, you will get an
extra parameter for the header.
And it require the soap binding, you have to put the soap binding in
your classpath.
