Altered behaviour for JNDI lookup

[zeitiger]

I tried to integrate version 3.x and failed because of the altered behaviour. In reference to weld documentation of integration within a plain Tomcat (and same thing match also to Jetty)

Tomcat only allows you to bind entries to java:comp/env, so the BeanManager will be available at java:comp/env/BeanManager

I know the spec of EE define that it should be java:comp/BeanManager, but within plain servlet container its different. The old custom logic matched this state of reality.

https://github.com/vaadin/cdi/blob/2.0/vaadin-cdi/src/main/java/com/vaadin/cdi/internal/CDIUtil.java#L30

But with the replacement of DeltaSpike 1.7.x this logic now breaks for me.

https://github.com/apache/deltaspike/blob/ds-1.7.2/deltaspike/core/api/src/main/java/org/apache/deltaspike/core/api/provider/BeanManagerProvider.java#L306

[kumm]

There are more workarounds in deltaspike for looking up the BeanManager. By JNDI is just one.
For example BeanManagerProvider is a CDI extension also, so it should receive a BeanManager on an event handler.
I think we should investigate further why all the workarounds are fail for you.

I've setup a sample project, and it runs fine on tomcat8.5, and 7. I've used weld integration method from here. Sample project is https://github.com/kumm/tomcatweld.