[esb-issues] [JBoss JIRA] Commented: (JBESB-3083) Wise SOAPClient action is unable to invoke oneway methods on the endpoints

[Kevin Conner (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12502452#action_12502452 ] 

Kevin Conner commented on JBESB-3083:
-------------------------------------

The point of making the single AOP change is so that we can get this working without having to modify the clients.  This change will make it appear the same as a request/response which returned a null.

Callers *could* check but, given that oneway has never worked, nobody should be relying on the current (broken) behaviour.  We are defining the behaviour now.

> Wise SOAPClient action is unable to invoke oneway methods on the endpoints
> --------------------------------------------------------------------------
>
>                 Key: JBESB-3083
>                 URL: https://jira.jboss.org/jira/browse/JBESB-3083
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.7
>            Reporter: Boris Belovic
>            Assignee: Tom Fennelly
>            Priority: Critical
>             Fix For: 4.7 CP1
>
>         Attachments: server.log, soap-wise-oneway-and-twoway, wise_oneway.tar.bz2, wise_oneway_and_twoway.tar.bz2
>
>
> Wise SOAPClient action is unable to invoke oneway methods (methods annotated with javax.jws.Oneway annotation) on WS endpoints. It looks like webservice WSDL is parsed correctly, but after that no statements from oneway method body are executed. We tested this with very simple webservice (see attached file) containing one oneway method with System.out.println() statement. After WSDL was parsed, there was no further output from webservice method.
> Invocation of twoway methods on WS endpoint is working correctly (without any problems/exceptions and with expected results).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira