[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: 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] [Commented] (TUSCANY-4017) Tuscany needs to process profile intents as in OSOA
[ https://issues.apache.org/jira/browse/TUSCANY-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13217216#comment-13217216 ] Simon Laws commented on TUSCANY-4017: - Another thought. We collate the policy information from the composite, component, reference/service, binding hierarchy onto Endpoints and EncpointReferences. I don't believe we push that back to bindings. So if you look at the binding I can well believe you still see "exactlyOnce". If you look at the Endpoint or EndpointReference you should see "atleastOnce"/"atMostOnce". > Tuscany needs to process profile intents as in OSOA > --- > > Key: TUSCANY-4017 > URL: https://issues.apache.org/jira/browse/TUSCANY-4017 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Policy >Affects Versions: Java-SCA-2.0-Beta3 >Reporter: Rashmi Hunt >Assignee: Simon Laws > Fix For: Java-SCA-2.x > > > In OASIS Tuscany implementation, 'exactlyOnce' intent is returned as is when > I tried to get intent name > from PolicySubject. > In OSOA Tuscany, if 'exactlyOnce' intent is defined in the composite, Tuscany > used to return it as > 'atleastOnce'/'atMostOnce' as intent name ( > PolicyComputationUtils.expandProfileIntents()) , which > seems to be missing in OASIS implementation -- 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
[ 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
