I'm also using Axis2 on the client, with WS-Addressing. My requests
have the header first, and no empty header like you're seeing. I'm
using v1.1.1.
I'm new to Axis2, so I don't really know what to suggest to help
you; I just wanted you to know that it works for me ...
How did you 'engage' addressing? I'm using an axis2.xml config file
(ie: I don't do configuration 'in code'), and I have a
<module ref="addressing"/>
therein.
Aaron.
On 2-Apr-07, at 10:14 PM, Steven E. Harris wrote:
I'm using AXIS2 to write a client, and I figured out how to engage the
addressing module. Testing reveals some odd behavior.
With addressing engaged, AXIS2 emits a SOAP request with this
structure:
<soapenv:Envelope
xmlns:wsa="http://www.w3.org/2005/08/addressing";
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
<soapenv:Header />
<soapenv:Body>
...
</soapenv:Body>
<soapenv:Header>
<wsa:To>...</wsa:To>
<wsa:MessageID>...</wsa:MessageID>
<wsa:Action>...</wsa:Action>
</soapenv:Header>
</soapenv:Envelope>
Notice the extra Header /after/ the Body? Surely that can't be
right. Has anyone else noticed this behavior?
--
Steven E. Harris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________
Aaron Aston | Twisted Pair | 905.852.0950
