sense to you?
Cheers,
Eoghan
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Fri 14/11/2008 15:26
To: dev@cxf.apache.org
Cc: Eoghan Glynn
Subject: Re: why does the SOAP CheckFaultInterceptor run in the POST_PROTOCOL
phase?
Actually, I remember why I put it that late
Folks,
Is there any reason why the SOAP CheckFaultInterceptor runs in the
POST_PROTOCOL phase, as opposed to PRE_PROTOCOL?
The net result is handleFault() is never called for a client-side JAX-WS
SOAPHandler, as the CheckFaultInterceptor (which is responbile for determining
if a fault is
On Friday 14 November 2008 10:27:55 am Eoghan Glynn wrote:
Folks,
Is there any reason why the SOAP CheckFaultInterceptor runs in the
POST_PROTOCOL phase, as opposed to PRE_PROTOCOL?
Well, the basic reason is that to check for a fault, it needs to look at the
first element in the body. The
Actually, thinking about it some more
Another fix MAY be to just update the JAXWSHandlerInvoker to look at the
SOAPMessage (since it had to part the thing into the SAAJ model anyway) and
have it call handleFault instead of handleMessage if the body contains a
fault.
Dan
On Friday 14
Thanks for the quick response Dan, some comments inline ...
Is there any reason why the SOAP CheckFaultInterceptor runs in the
POST_PROTOCOL phase, as opposed to PRE_PROTOCOL?
Well, the basic reason is that to check for a fault, it needs to look at the
first element in the body. The
Actually, I remember why I put it that late.
The CheckFaultOut stuff HAS to occur after anything related to SAAJ/DOM is
done.When it gets there, the XmlStreamReader sits at the first child of
the soap:body. However, that might NOT be an element. It may be
whitespace. However,
