[jsr345-experts] JMS spec dropped requirement for the resource adapter to be able to automatically generate a valid subscription name (was Proposals for MDB and RA standardisation (JMS_SPEC-30,55,54,25,73))

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]

From: Marina Vatkina <marina.vatkina_at_oracle.com>
Date: Thu, 28 Feb 2013 11:10:05 -0800

Experts,

This is a followup on the thread called "Proposals for MDB and RA
standardisation (JMS_SPEC-30,55,54,25,73)".

The JMS spec has dropped the requirement listed in JMS_SPEC-73 - for the
resource adapter to be able to automatically generate a valid
subscription name.

If you are interested in the details of why this happened, read the
detailed email Nigel sent to the JMS EG explaining the problem:
http://java.net/projects/jms-spec/lists/jsr343-experts/archive/2013-01/message/57

I've updated the EJB spec to match the following changes to the JMS spec
(see Nigel's message
http://java.net/projects/jms-spec/lists/jsr343-experts/archive/2013-02/message/15
for the final changes to the JMS spec):

* The subscriptionScope property has been removed
* The clientId and subscriptionName properties no longer have behaviour dependent on subscriptionScope being set
* The feature that allowed subscriptionName to be left unset if subscriptionScope was Instance or Cluster has been removed

-marina