"[EMAIL PROTECTED]" wrote : To avoid being exposed to an implementation detail like the actual global jndi name, you should be using an java ee application client and client side @EJB refs rather than the global jndi lookup.
Scott, that sounds fair. But I'm a bit lost about how that would work technically. Simple use case: I deploy an .ear with an EJB3 archive and a .war containing a Struts application that needs to reference EJB3s. Struts is the client here. What magic would I have to perform to make @EJB annotations work there then? Can you give me a hint? I'm not sure how this would work. S. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3944352#3944352 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3944352 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
