Github user kylape commented on the pull request:
https://github.com/apache/cxf/pull/25#issuecomment-61220541
Okay, I reproduced the issue with CXF 3.0.2 and verified it is resolved in
my build of the master branch today.
Just FYI -- in JBoss I only had to add this code:
```
final Service service = Service.create(wsdl, ns);
service.setHandlerResolver(new HandlerResolver() {
public List<Handler> getHandlerChain(PortInfo info) {
return handlerChain;
}
});
```
because the JBossWS integration calls `setHandlerChain` for every
invocation to ensure handler order (perhaps that could be improved upon as
well?). When using CXF without JBossWS integration, I had to call
`((BindingProvider)port).getBinding().setHandlerChain(handlerChain)` for every
invocation to reproduce the issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
