In the latest ejb3 release session beans are looked up by:
application name/ejbname/remote (or local)
instead of the fully qualified classname as it was before.
Just wondered - will this change again (or is this agreed upon in the final spec)?
Is this scheme JBoss specific, or is this the way it will be on other EJB3 application servers as well?
The default jndi bindings are not defined in the specification. The current format if JBoss specific. There are no changes to the format planned.
My recommedation is to explicitly define the jndi binding for EJBs through the RemoteBinding/LocalBinding annotation or through the jboss.xml deployment descriptor.