[
https://issues.apache.org/jira/browse/TUSCANY-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker resolved TUSCANY-2835.
---------------------------------
Resolution: Fixed
Fixed in branch 1.x at revision: 743094
> JMS Binding does not save operation names unless there are properties.
> ----------------------------------------------------------------------
>
> Key: TUSCANY-2835
> URL: https://issues.apache.org/jira/browse/TUSCANY-2835
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Affects Versions: Java-SCA-1.4
> Environment: All
> Reporter: Dan Becker
> Assignee: Dan Becker
> Priority: Minor
> Fix For: Java-SCA-Next
>
>
> Christopher Ortiz: "I believe there is still a problem with the way the
> OperationProperties element is being processed in the JMSBinding. The new
> method getOperationNames() will return the keySet from the
> operationProperties map. However, operationProperties is the map of
> 'property' found in the 'header' subelement of OperationProperties. If no
> header element with a property is present in OperationProperties, the
> operationProperties name (opName) is never set in this map.
> When the 'operations properties' element is parsed in JMSBindingProcessor in
> parseOperationProperties, the operation Name attribute (opName) is retrieved
> from the reader. But it is not saved anywhere. The nativeOperation
> attribute is read next. If it is present, it is set to a map with the opName
> as a key. But since the NativeOperation attribute is optional, it may not be
> present, and the opName is not preserved."
> Dan Becker: "I see what you're saying. It sounds like we need to add
> operation names, even if there are no properties for the operation name."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
