You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/08 20:38:42 UTC

[jira] [Resolved] (CXF-3956) JAX-WS HandlerResolver consulted for ServiceImpl.createPort, but not for createDispatch

     [ https://issues.apache.org/jira/browse/CXF-3956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Kulp resolved CXF-3956.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5.1
                   2.4.5
                   2.3.8
    
> JAX-WS HandlerResolver consulted for ServiceImpl.createPort, but not for createDispatch
> ---------------------------------------------------------------------------------------
>
>                 Key: CXF-3956
>                 URL: https://issues.apache.org/jira/browse/CXF-3956
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Eirik Bjorsnos
>            Assignee: Daniel Kulp
>             Fix For: 2.3.8, 2.4.5, 2.5.1
>
>
> Using 2.5.0, service.setHandlerResolver has no effect when later creating a Dispatch:
> Service service = Service.create(wsdl, SERVICE_QNAME);
> service.setHandlerResolver(new MyHandlerResolver());
> Dispatch<SOAPMessage> dispatch = service.createDispatch(PORT_QNAME, SOAPMessage.class, Service.Mode.MESSAGE);
> List<Handler> handlerChain = dispatch.getBinding().getHandlerChain();
> handlerChain.add(new SomeHandler());
> dispatch.getBinding().setHandlerChain(handlerChain);
> SomeHandler is invoked, but any handlers returned by MyHandlerResolver.getHandlerChai() are ignored.
> Is this a bug in the CXF JAW-WS implementation?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira