[jboss-jira] [JBoss JIRA] (WFLY-4643) SOAP Handlers only executing on prestage when using JAX-WS standards

[Derrick Sutherland (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068918#comment-13068918 ] 

Derrick Sutherland commented on WFLY-4643:
------------------------------------------

Ahh after digging through Apache CXF 1.7.3, it turns out your implementation skips the SOAPHandler handleMessage if a fault code is returned.  I find that interesting as the spec says nothing about skipping the handler if a fault is returned.  I presumed both the handleMessage and handleFault methods would be called upon that happening.  If this is considered normal behavior, this really should be explicitly stated.  If not, CXF should be altered to match the J2EE spec.  Sorry for any trouble this may have caused.


> SOAP Handlers only executing on prestage when using JAX-WS standards
> --------------------------------------------------------------------
>
>                 Key: WFLY-4643
>                 URL: https://issues.jboss.org/browse/WFLY-4643
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Web Services
>         Environment: Wildfly 8.2.0.Final on RHEL 6.5
>            Reporter: Derrick Sutherland
>            Assignee: Alessio Soldano
>
> When a handler is attached the client of a JAX-WS service, only the outbound request is intercepted.  The inbound reponse isn't.  Furthermore, the reverse applies to any JAX-WS service handle when using the @HandlerChain annotation.  An example of a client-side handlers usage is depicted below:
> {code:title=TestServlet.java|borderStyle=solid}
>     List<Handler> handlers=new ArrayList<Handler>();
>     handlers.add(new DemoHandler());
>     Service service = Service.create(new URL(http://example.com/demoWs?wsdl"), new QName(DemoWsInterface.TARGET_NAMESPACE, "DemoWs"));
>     demoWs=service.getPort(DemoWsInterface.class);
>     ((BindingProvider) demoyWs).getBinding().setHandlerChain(handlers);
> {code}
> And the handleMessage function in my handler is as such:
> {code:title=DemoHandler.java|borderStyle=solid}
>     public boolean handleMessage(SOAPMessageContext msgContext) {
>        Boolean outbound = (Boolean) msgContext.get(MessageContext.MESSAGE_OUTBOUND_PROPERTY);
>        if(outbound)
>            System.out.print("Outbound soap request");
>        else
>            System.out.print("Inbound soap response");
>        return true;
>     }
> {code}
> Everytime the client is used, the message "Outbound soap request" is displayed.  However, the inbound message is never displayed when the response comes back.  This should not be the case as the J2EE specification states a handler should receive the inbound and outbound soap messages on both the client and service.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)