Upgrade JMSRA to support the activation properties required by JMS 2.0 (MQ-193)

[MQ-251] Implement JMSRA activation properties clientId, subscriptionName and subscriptionScope Created: 27/Nov/12  Updated: 19/Feb/13  Resolved: 19/Feb/13

Status: Closed
Project: mq
Component/s: mq-ra
Affects Version/s: 5.0-RI (JMS2.0)
Fix Version/s: 5.0-RI (Sprint 10 - 28)

Type: Sub-task Priority: Major
Reporter: Nigel Deakin Assignee: David Zhao
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Dependency
depends on CONNECTOR_SPEC-1 New methods on MessageEndpointFactory... Resolved
depends on GLASSFISH-19347 Implement new methods on MessageEndpo... Resolved
depends on JMS_SPEC-30 Define mandatory activation config pr... Resolved
Tags: jms-2-implementation

 Comments   
Comment by Nigel Deakin [ 07/Feb/13 ]

When this issue was first logged it was a case of implementing

  • JMS_SPEC-73 (Define how messages from a topic are delivered to clustered application server instances) and
  • JMS_SPEC-30 (Define mandatory activation config properties clientId and subscriptionName)

Since then there has been a change of requirement. JMS_SPEC-73 has been deferred until a later version of JMS and so is not needed for MQ 5.0. I am therefore removing the dependency on this issue.

Please remove the features defined in JMS_SPEC-73, but make sure that the features defined in JMS_SPEC-30 remain.

Comment by David Zhao [ 19/Feb/13 ]

Defer it because subscriptionScope feature is removed from JMS 2.0 spec.

Comment by David Zhao [ 19/Feb/13 ]

This feature is removed from JMS 2.0 spec, so disable it temporally. It will be reopened in future releases if needed.

Generated at Mon Mar 02 15:28:17 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.