aaron aston <[EMAIL PROTECTED]> writes:
> 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.
That's good news: this did work at some point.
> 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?
In my code, as follows:
stub._getServiceClient().engageModule(
new javax.xml.namespace.QName( org.apache.axis2.Constants.MODULE_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.
I had commented that line out, as I wasn't sure I wanted to enable
addressing for every operation. Still, I tried to remove the call
above from my code and enable addressing in the axis2.xml file as you
suggest, but I get the same output.
Interesting discovery: the output I reported yesterday came with an
XMLBeans binding. Today I've been experimenting with JiBX
again. Without the addressing module engaged, the serialized SOAP
message looks fine. With addressing engaged, I see the following
error:
Exception in thread "main" org.apache.axiom.om.OMException: SOAPEnvelope must
contain a body element which is either first or second child element of the
SOAPEnvelope.
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getBody(SOAPEnvelopeImpl.java:145)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.addChild(SOAPEnvelopeImpl.java:106)
at
org.apache.axiom.soap.impl.llom.SOAPEnvelopeImpl.getHeader(SOAPEnvelopeImpl.java:84)
at
org.apache.axis2.handlers.addressing.AddressingOutHandler$WSAHeaderWriter.<init>(AddressingOutHandler.java:140)
at
org.apache.axis2.handlers.addressing.AddressingOutHandler.invoke(AddressingOutHandler.java:106)
at org.apache.axis2.engine.Phase.invoke(Phase.java:383)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:203)
at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:433)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:330)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
That adds some evidence to the out-of-order problem witnessed with the
XMLBeans output.
--
Steven E. Harris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
