[TUSCANY-2835] JMS Binding does not save operation names unless there are properties.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Java-SCA-1.4
• Fix Version/s: Java-SCA-1.x
• Component/s: Java SCA JMS Binding Extension
• Environment: All
• Assignee: Daniel O. Becker
• Reporter: Daniel O. Becker
• Created: 10/Feb/09 16:00
• Updated: 19/Sep/10 11:30
• Resolved: 10/Feb/09 20:36

Description

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."