This is related to making the naming context available during end point
Looking at all the upstream issues :
the expectation is that the connectionFactoryJndiName and
destinationLookup activation-config property values are made available
via JNDI lookup during end point activation.
Connector Spec so far has not defined anything about naming context
availability and is being clarified in the current iteration of the
specification (Connector 1.7) that naming context can be made available
during end point activation.
Connector specification / implementation does not define/do anything
specific w.r.t the "connectionFactoryJndiName", "destinationLookup"
activation-config property as these are protocols between MDB Container
and JMS RA.
Currently, there is no JNDI naming context setup when MDB Container
calls connector container to do end point activation.
Requesting EJB team (Srini) to evaluate making the naming context available before
calling connector container to setup the end point.
[Ref : org.glassfish.ejb.mdb.MessageBeanContainer, line 225 that sets up
the end point by calling "messageBeanClient_.setup(this)" ]
I would also assume that resources indicated by the "connectionFactoryJndiName" and
"destinationLookup" activation-config property values would be set as
part of this, if those resources are defined via the MDB application (eg: @JMSConnectionFactoryDefinition, @JMSDestinationDefinition).
To clarify this further :
JMS RA will be doing the lookup of the resources where the
resource-names are defined in the "activation-spec" configuration
properties by name "connectionFactoryJndiName" and "destinationLookup".
So, those resources should be made available in JNDI for JMS RA to
These resources may be from :
a) vendor specific resources (eg: create-jms-resource --restype
b) A @JMSDestinationDefinition annotation defined in a component (eg: an
EJB) of the application that also has the MDB being deployed.