nan...@live.com
> Subject: Re: Issue CXF-4181
> Date: Fri, 23 Mar 2012 14:13:51 -0400
>
>
> Just committed a fix for this to trunk using Aki's unit test. Can you and
> Aki take a quick look?
>
> Basically, the SOAP Envelope/Body is stored on the message as a DOM n
Just committed a fix for this to trunk using Aki's unit test. Can you and
Aki take a quick look?
Basically, the SOAP Envelope/Body is stored on the message as a DOM node.
Thus, when we parse the fault to the DOM, we can actually parse it right
into the correct place in the original DOM.
at do you think?Waiting for
other proposals :).Regards,C.
> Date: Fri, 23 Mar 2012 15:34:15 +0100
> Subject: Re: Issue CXF-4181
> From: elak...@googlemail.com
> To: dev@cxf.apache.org
>
> Hi,
> I attached a unit test for this problem to your jira ticket.
>
> I thought a q
Hi,
I attached a unit test for this problem to your jira ticket.
I thought a quick solution is to copy all the namespace bindings from
the reader object to the root dom element but the public API does not
have an iterator to access all the bindings. So, that didn't work.
Someone might have a simp
Hello,This issue is because the Soap12FaultInInterceptor.unmarshalFault
receives a XMLStreamReader only for the Fault element. This is because it is
what the SAAJInInterceptor.handleMessage does with the XMLSreamReader content
when the message is a fault.Well, I think this issue requires a lot
