Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <20790358.1167198501057.JavaMail.jira@brutus>
Date: Tue, 26 Dec 2006 21:48:21 -0800 (PST)
From: "Bharath Ganesh (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Created: (CXF-336) JAX-WS Handler on client side not working
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

JAX-WS Handler on client side not working
-----------------------------------------

                 Key: CXF-336
                 URL: http://issues.apache.org/jira/browse/CXF-336
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 2.0-M1
            Reporter: Bharath Ganesh


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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira