Experts,
This question is for those of you who represent container providers.
The EJB/JMS 2.0 alignment added 2 JNDI lookup options to the standard
sets of the activationConfig properties (see sections 5.4.16.4 and
5.4.16.5 in the latest EJB 3.2 spec). The intended use for these
properties is to allow RAs to configure the endpoint during the
endpointActivation() call. The latter (the endpointActivation() call)
usually happens while MDB container is being created.
The question: if the JCA spec is to change to allow java:comp lookup
during endpointActivation() call, will it be a problem for your MDB
container?
thanks,
-marina