[TUSCANY-1836] JMS Binding does not conform to the specification when creating JMS queues

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Java-SCA-1.0
• Fix Version/s: Java-SCA-1.1
• Component/s: Java SCA JMS Binding Extension
• Environment: SVN Revision #582742; Linux
• Patch Info: Patch Available
• Assignee: Simon Laws
• Reporter: Mark Combellack
• Created: 08/Oct/07 14:59
• Updated: 19/Sep/10 11:27
• Resolved: 09/Oct/07 13:54

Description

Currently, the way that the JMS Binding creates JMS queues is not compliant with the SCA JMS Binding specification.

Currently it looks for the JMS Queue. If it does not exist, it will attempt to create it if the create mode is CREATE_ALLWAYS.

The JMS Binding specification says:

137 • /binding.jms/destination/@create - indicates whether the destination should be created
138 when the containing composite is deployed. Valid values are "always", "never" and
139 "ifnotexist". The default value is "ifnotexist". If "always" is specified and the corresponding
140 resource already exists, then this should be considered an error.

The current implementation does not handle the following scenarios correctly:

• Queue existing and "always" specified
• No support for "ifnotexist"

Also, throughout the code CREATE_ALLWAYS is spelt wrongly.