While you deserved the thrashing that Gavin and Bill just gave you :-), I'll be a little more diplomatic.
The example you gave only relies on the classname of the bean because that's the default naming convention (if you don't name it yourself). If you can come up with a more rational, common-sensical default for your JNDI name, well... you should have spoken up during the EJB3 spec committee's public discussions. But - if you want the decoupling you mention, you merely have to follow Bill's example - you use EJB3 annotations (or, optionally, an XML config) to define the lookup names. "StatelessCalculator/remote" is merely the default that the container comes up with if you elect NOT to define the name yourself. If you don't like it, name it yourself via the name= annotation attribute. You really should read alittle more deeply into a subject before attempting the arrogant route. Reading the specification would have been the first thing you should have checked and the answer would have been found there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3932649#3932649 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3932649 ------------------------------------------------------- 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
