OK I found what the problem is (for my case at least): The code I was using to request the Session object from JNDI was running as a unit test case external to JBoss itself. (ie. as a JBoss client, rather than as a session bean or mbean). When I put this same code inside a session bean the Session object resolved fine!
Is this a bug or a feature? Should client applications be able to request the MailService from JNDI and get an appropriate remote proxy object? If this is indeed the desired behaviour, would it not be better to throw some kind of NamingException to indicate that a remote interface is not available for the given object name, rather than just returning null? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3930262#3930262 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3930262 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
