[jbossws-issues] [JBoss JIRA] Updated: (JBWS-3293) Handler not invoked in WS call on the client side when using dispatch and creating service without WSDL

Handler not invoked in WS call on the client side when using dispatch and creating service without WSDL ------------------------------------------------------------------------------------------------------- Key: JBWS-3293 URL: https://issues.jboss.org/browse/JBWS-3293 Project: JBoss Web Services Issue Type: Bug Security Level: Public(Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assignee: Richard Opalka Anil Saldhana wrote: --- Hi, In PicketLink, we are creating a Dispatch without considering the WSDL as follows: ============= Service jaxwsService = Service.create(service); jaxwsService.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING, config.getEndPointAddress()); Dispatch<Source> dispatch = jaxwsService.createDispatch(portName, Source.class, Mode.PAYLOAD); ========== Now, I want to inject one of my Jaxws handlers: =========== Binding binding = dispatch.getBinding(); BinaryTokenHandler binaryTokenHandler = new BinaryTokenHandler(); handlers.add(binaryTokenHandler); binding.setHandlerChain(handlers); ============ But the outgoing WS call does not go through my handler. But, if the Dispatch was created with the knowledge of WSDL something like: ============ Service service = Service.create(wsdl, serviceName); WSTest port = service.getPort(new QName("http://ws.trust.test.picketlink.org/";, "WSTestBeanPort"), WSTest.class); BindingProvider bp = (BindingProvider)port; bp.getRequestContext().put(SAML2Constants.SAML2_ASSERTION_PROPERTY, assertion); List<Handler> handlers = bp.getBinding().getHandlerChain(); handlers.add(new SAML2Handler()); bp.getBinding().setHandlerChain(handlers); =============== Then I see that the handler is invoked during the WS call on the client side. Any thoughts? This is driving me nuts for 10 days now. :) Regards, Anil ---