JMS Binding does not conform to the specification when creating JMS queues
--------------------------------------------------------------------------
Key: TUSCANY-1836
URL: https://issues.apache.org/jira/browse/TUSCANY-1836
Project: Tuscany
Issue Type: Bug
Components: Java SCA JMS Binding Extension
Affects Versions: Java-SCA-1.0
Environment: SVN Revision #582742
Linux
Reporter: Mark Combellack
Priority: Minor
Fix For: Java-SCA-Next
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
