Hi
AFAIK there is nothing making it mandatpry to work + are you sure it works
after? JNDI portability is not trivial.
Using global names can help.
Le 7 sept. 2015 04:36, "manz" <oren.manz...@elbitsystems.com> a écrit :
> Hello,
>
> I am using cdi extension' which is using jndi resources from java:comp/env
>
> While TomEE is firing the cdi extension 'AfterDeploymentValidation' event,
> the jndi java:comp/env is not populated.
>
> Can anybody confirm that this is BUG in TomEE (in JBoss there is NO problem
> to lookup for jndi resources while the 'AfterDeploymentValidation' is
> fired).
>
> import javax.enterprise.event.Observes;
> import javax.enterprise.inject.spi.AfterDeploymentValidation;
> import javax.enterprise.inject.spi.BeanManager;
> import javax.enterprise.inject.spi.Extension;
> import javax.naming.InitialContext;
> import javax.naming.NamingException;
>
> public class SimpleCdiExtension implements Extension {
>
> public void afterDeploymentValidation(@Observes
> AfterDeploymentValidation event, BeanManager beanManager) {
> System.out.println("Initializing SimpleCdiExtension");
>
> Context context = new InitialContext();
> DataSource dataSource = (DataSource)
> context.lookup("java:comp/env/my_jndi_datasource");
>
> // java:comp/env is empty here can't lookup for jndi resources
> // java:comp/env/comp/my_jndi_datasource does not exist either
> }
>
> }
>
> I am using TomEE Plus 1.7.1
>
> Regards,
>
> manz
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/jndi-path-java-comp-env-is-empty-on-cdi-extension-AfterDeploymentValidation-event-tp4676136.html
> Sent from the TomEE Dev mailing list archive at Nabble.com.
>
