[
https://issues.apache.org/jira/browse/TUSCANY-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jennifer A Thompson resolved TUSCANY-4019.
--
Resolution: Won't Fix
Although the specification says the scaOperationName is to be passed on service
requests and callsbacks it doesn't explicitly state that the scaOperationName
is not to be passed on the responses. So Tuscany used scaOperationName to
correlate non-persistent async response messages.
Although this could be implemented another way, it seems unlikely for this to
have a large impact on users.
> 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
