This discussion is archived
0 Replies Latest reply: Aug 31, 2012 11:09 AM by 959363 RSS

@HandlerChain handlers working in reverse order when using Metro standalone

959363 Newbie
Currently Being Moderated
Hi,
I'm seeing odd behaviour when using the @HandlerChain on my webservices. I have defined 3 jax-ws handlers in a file called "soap-handlers.xml". This all works fine and dandy, but instead of the handlers being called from the top down and back up like I've read on the net. It's starting from the bottom and working up the stack then back down.

Everything I read, says the opposite..That I should be seeing HandlerOne->HandlerTwo->HandlerThree->Webservice->HandlerThree->HandlerTwo->HandlerOne

Theses are all server side protocol handlers as well.

Am I missing something? Or is this working correctly? I've tried running on Jetty and JBoss 5.1 GA and the behaviour is the same running on JDK1.7. We are also using the 2.0.1 version of the JAXWS libraries according to our Maven. We need to use this version because we also use OpenAM and it doesn't appear to work with any newer versions.

<dependency>
<groupId>com.sun.xml.ws</groupId>
<artifactId>webservices-rt</artifactId>
<version>2.0.1</version>
</dependency>

-- SOAP-HANDLERS.XML --

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<javaee:handler-chains xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<javaee:handler-chain>
<javaee:handler>
<javaee:handler-class>org.foo.handler.HandlerOne
</javaee:handler-class>
</javaee:handler>
<javaee:handler>
<javaee:handler-class>org.foo.handler.HandlerTwo
</javaee:handler-class>
</javaee:handler>
<javaee:handler>
<javaee:handler-class>org.foo.handler.HandlerThree
</javaee:handler-class>
</javaee:handler>
</javaee:handler-chain>
</javaee:handler-chains>

Thanks..
- Tim

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points