The correct way to look up resource in Java EE is to use the local name (a.k.a. logical name) of the resource rather than the actual JNDI name of the resource. You can run the following sample and see the difference:

@Stateless() @WebService() public class VisitorRegistrationService {

// The actual JNDI name is mail/FossDemoMailSession // where as the local name is mail/MailSession. @Resource(name="mail/MailSession", mappedName="mail/FossDemoMailSession") Session mailSession; // inject a Mail Session /** * Web service operation */ @WebMethod public int registerVisitor( String name, String email) { try { InitialContext ctx = new InitialContext(); Object a = ctx.lookup("mail/FossDemoMailSession"); Object b = ctx.lookup("java:comp/env/mail/MailSession"); System.out.println(a); System.out.println(b); } catch(Exception e) { e.printStackTrace(); } return 0; } }

Looking up the resource using the actual JNDI name (mail/FossDemoMailSession) returns com.sun.enterprise.deployment.MailConfiguration@49d560 object, where as if you use java:comp/env/mail/MailSession, it returns javax.mail.Session@157bbd4.

To try out yourself, just compile, jar and deploy. Create a MailSession using admin gui and give it a name mail/FossDemoMailSession. You can test the program by using the web service test client that is available in the admin gui.

glas...@javadesktop.org wrote: