On 11/01/2013 18:41, Jesper Pedersen wrote:
> On 01/11/2013 01:25 PM, Nigel Deakin wrote:
>>> Given there is access to java:comp/UniqueMDBName during
>>> endpointActivation() would that cover your use-cases ?
>>>
>>> Or would still need a value from BootstrapContext that is unique
>>> across a cluster ?
>>>
>>
>> I still need getInstanceName() (as defined in CONNECTOR_SPEC-1?) or an
>> equivalent. How would this digger from BootstrapContext.getUniqueId()?
>>
>
> There is no 'instance name' for a BootstrapContext, but getUniqueId() would contain the functionality you are looking for.
>
> The format of the identifier will be discussed based on your request.
>
I look forward to your response.
Siva has asked me to explain why these two methods need to return a specific number of characters.
It's because there is a limit to the length of a durable subscription (the draft JMS 2.0 spec defines this as 128). The
container is in a better position to know how to shorten the name (and do so without losing human-readability) without
losing the defined level of uniqueness than an individual call to endpointActivation.
I have just spotted that the list of valid characters I requested in
http://java.net/jira/browse/CONNECTOR_SPEC-1 is
slightly out of date: the draft JMS 2.0 spec defines the characters valid in a durable subscription name are: Java
letters, Java digits, Underscore (_), Dot (.) and Minus (-).
Nigel