Hi Mansour, OK, got the point. Actually, you are using a wicket extension to manage @EJB injection.
By default, i guess it's looking for resources in the Environment Naming Context (java:comp/env). Under Tomcat and AFAIR, when you get a Context instance (new InitialContext()), Tomcat overrides your jndi properties in order to set Tomcat ones before any other. Anyway, I gonna checkout Wicketstuff sources in order to look how they manage resource injections. In the mid time, could you have a look and try with openejb: prefix (using the Naming Strategy i guess)? It should automatically switch from Tomcat naming to OpenEJB naming if you use that prefix. Let us know please. Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/Openejb-web-application-and-jndi-properties-problem-tp3102659p3171799.html Sent from the OpenEJB User mailing list archive at Nabble.com.
