Ignore this one. It was meant for another email.
-marina
Marina Vatkina wrote:
> Let me know if you see a problem with having the same rules in all 3
> (LC interceptor will say "if executed in a transactional context" for
> the rollback rule.
>
> thanks,
> -marina
>
> -------- Original Message --------
> Subject: [jsr345-experts] Lookup strings in activationConfig?
> Date: Fri, 30 Nov 2012 14:15:46 -0800
> From: Marina Vatkina <marina.vatkina_at_oracle.com>
> Reply-To: marina.vatkina_at_oracle.com
> To: jsr345-experts_at_ejb-spec.java.net
>
>
>
> 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
>
>
>