Hi
For those who couldn't participate in this week's call, could you please
share your inputs on these two questions by Thursday (Jan 24) PT EoD? I
would like to get these responses soon so that I can add these two
important to the draft I shall send by the end of this week, and we will
have more time to vet the spec changes.
Please read the minutes of today's meeting (email subject:"Minutes for the
meeting of Jan 23") and some of the EG ML threads
on these issues.
1. Providing an ActivationName to the RA (CONNECTOR_SPEC-1):
We have two choices:
- Choice #1: Introduce MessageEndpointFactory.getActivationName, and have
the JMS RA use them.
- Choice #2a: Upgrade or extend the MEF interface (for instance introduce
a new
ActivationNameMessageEndpointFactory that extends MessageEndpointFactory
and adds a method String getActivationName()). JMS spec must be required
to pass in instances ActivationNameMessageEndpointFactory for JMS
MessageEndpoints, and the JMS RA uses the
ActivationNameMessageEndpointFactory to get the activation name.
ACTION: Please state your choice or alternative ideas.
2. Resource Definition Annotations:
There has been discussions on how a resource adapter name could be used to
identify a deployment of a RAR, and how such Resource Definition
annotations can be used in a portable manner in most development usecases.
We have also discussed some vendor-specific concerns on these.
ACTION: Could you share your inputs
on those discussions and whether we should defer them? If your choice is
to defer, please state what technical reasons are there to defer them, and
in particular what additional information that we don't have today would
be gained if we defer to a future release.
Thanks
--Siva.