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 (Created) (JIRA)" <de...@tuscany.apache.org> on 2012/02/22 03:46:52 UTC
[jira] [Created] (TUSCANY-4019) scaOperationName being set on
response messages
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
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
[jira] [Resolved] (TUSCANY-4019) scaOperationName being set on
response messages
Posted by "Jennifer A Thompson (Resolved) (JIRA)" <de...@tuscany.apache.org>.
[ 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
[jira] [Reopened] (TUSCANY-4019) scaOperationName being set on
response messages
Posted by "Jennifer A Thompson (Reopened) (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jennifer A Thompson reopened TUSCANY-4019:
------------------------------------------
The scaOperationName is used by Tuscany for correlating non-persisted async messages, so removing this value caused failures in async responses.
> 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
[jira] [Updated] (TUSCANY-4019) scaOperationName being set on
response messages
Posted by "Jennifer A Thompson (Updated) (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jennifer A Thompson updated TUSCANY-4019:
-----------------------------------------
Attachment: Tuscany-4019.patch
> 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
[jira] [Resolved] (TUSCANY-4019) scaOperationName being set on
response messages
Posted by "Jennifer A Thompson (Resolved) (JIRA)" <de...@tuscany.apache.org>.
[ 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