cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jervis Liu (JIRA)" <>
Subject [jira] Assigned: (CXF-336) JAX-WS Handler on client side not working
Date Thu, 04 Jan 2007 03:04:27 GMT


Jervis Liu reassigned CXF-336:

    Assignee: Jervis Liu

> JAX-WS Handler on client side not working
> -----------------------------------------
>                 Key: CXF-336
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-WS Runtime
>    Affects Versions: 2.0-M1
>            Reporter: Bharath Ganesh
>         Assigned To: Jervis Liu
> After the JAX-WS portable artifacts on client side are generated with the WSDLtoJava
tool, if JAX-WS handlers are set on the generated service class, the handlers are not invoked
by the CXF client runtime. 
> The handlers are set using the Service API (service.setHandlerResolver())
> The same works fine if i set the handler like: 
> ((BindingProvider)port).getBinding().getHandlerChain().add(new MySOAPHandler());
> whereas the following does not work: 
> service.setHandlerResolver(new MyHandlerResolver()); //where MyHandlerResolver would
add MySOAPHandler to the chain. 
> port=service.getXXXPort();
> port.sayXXX();
> Also if the handlers are set with the @HandlerChain annotation of the generated service
class at client side, they are not picked up. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message