Issue Details (XML | Word | Printable)

Key: GLASSFISH-19054
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Duplicate
Priority: Major Major
Assignee: marina vatkina
Reporter: Nigel Deakin
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
glassfish

Implement new predefined JNDI name java:comp/UniqueMDBName

Created: 05/Sep/12 02:39 PM   Updated: 14/Nov/12 02:08 PM   Resolved: 05/Sep/12 05:07 PM
Component/s: ejb_container
Affects Version/s: 4.0
Fix Version/s: None

Time Tracking:
Not Specified

Tags:
Participants: marina vatkina and Nigel Deakin


 Description  « Hide

In the draft EJB 3.1 spec, section 5.7.3 "Unique Identifier for JMS Message-Driven Bean" states:

The Container Provider must make a name which uniquely identifies the deployed MDB in an application server instance, available in the JNDI naming context under java:comp/UniqueMDBName so that it can be looked up by the resource adapter when its endpointActivation method is called. The resource adapter may use this name when constructing a default durable subscription name.

This issue requests the implementation of this feature.



Nigel Deakin added a comment - 14/Nov/12 02:08 PM

This issue is superseded by Superseded by GLASSFISH-19347 and is not longer required.


marina vatkina added a comment - 05/Sep/12 05:07 PM

Nigel Deakin added a comment - 05/Sep/12 02:40 PM

This issue blocks MQ-193.