You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jennifer A Thompson (Resolved) (JIRA)" <de...@tuscany.apache.org> on 2012/02/24 11:47:48 UTC

[jira] [Resolved] (TUSCANY-4019) scaOperationName being set on response messages

     [ https://issues.apache.org/jira/browse/TUSCANY-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jennifer A Thompson resolved TUSCANY-4019.
------------------------------------------

    Resolution: Fixed

Fixed in revision 1293172.
                
> scaOperationName being set on response messages
> -----------------------------------------------
>
>                 Key: TUSCANY-4019
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-4019
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA JMS Binding Extension
>    Affects Versions: Java-SCA-2.x
>            Reporter: Jennifer A Thompson
>             Fix For: Java-SCA-2.x
>
>         Attachments: Tuscany-4019.patch
>
>
> Per the JMS Binding specification,  scaOperationName should be set when "receiving a request at a service, or a callback at a reference" (line399-400), so it should not be set for reply messages. However the HeaderServiceInterceptor.processResponse message is calling:
> responseMessageProcessor.setOperationName(operationName, jmsMsg);
> Which sets the scaOperationName of the request in the response message. This line should be removed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira