Handlers always run in the same order as defined (except logical/payload
handlers activated first), with no reversal in direction between
incoming and outgoing.
Providing handler2 is not a logical handler, as you're saying, I'm
puzzled why it's being activated prior to handler1. CXF bug? I would
try configuring your service-side handlers the official JAX-WS way
(Steps 6-7 here:
http://www.jroller.com/gmazza/entry/jaxws_handler_tutorial), and let us
know if it makes a difference in their execution ordering.
Glen
On 07/24/2012 09:03 AM, Sunil Bapat wrote:
Both handlers that I have below implement SOAPHandler<SOAPMessageContext>.
I was expecting handler1 to be invoked before handler2 (config below),
during the incoming call to the web service and reverse in the outgoing
call.
But the opposite seems to be happening where handler 2 is getting invoked
before handler 1 during the incoming call. I just wanted to know that this
is the expected behavior in which case my assumption was incorrect.
Thanks
Sunil.
On Mon, Jul 23, 2012 at 7:02 PM, Mark Streit <[email protected]> wrote:
Might want to look at these on Glen Mazza's blog:
http://www.jroller.com/gmazza/entry/jaxws_handler_tutorial
http://www.jroller.com/gmazza/entry/jaxwshandlers_to_cxfinterceptors
HTH
Mark
On Jul 23, 2012 5:49 PM, "Sunil Bapat" <[email protected]> wrote:
I have a CXF web service (CXF 2.6.1 or 2.3.1) defined in spring as shown
below.
When this web service is called, I notice that handler 2 is called before
handler 1 during the incoming call.
Is this the expected behavior? I was expecting handler 1 to be called
before handler 2. Just wanted a clarification before I reverse the order.
<jaxws:endpoint id="testEndpoint"
address="/TestService"
implementor="#testBean">
<jaxws:handlers>
<ref bean="handler1" />
<ref bean="handler2" />
</jaxws:handlers>
</jaxws:endpoint>
Thanks
Sunil.
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
