[jboss-dev-forums] [Design of POJO Server] - Re: [jboss-metadata] EJB mappedName as a Base?

[wolfc]

I consider http://wiki.jboss.org/auth/wiki/DevJNDIBinding to be authoritative on resulting JNDI names. The policy is just another means to get these results. If we want to change or expand these, that should be done first.

The only thing that differs from Glassfish is how we handle a bean with 1 home interface. That's why we have the (unsupported) option to disable JBMETA-11 checking.

In future I want to go to a mapped name which can contain expressions:
@Stateless(mappedName="java:global/env/$s:optional(${appName}/)${moduleName}/${beanName}#${interface}")
Which we should be able to realize with another policy implementation and then it should be EJB 3.1 compliant.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164384#4164384

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4164384