What I'm testing right now is addition of EjbDeploymentSummary,
DefaultJndiBindingPolicy to metadata under the org.jboss.metadata.ejb.jboss.jndipolicy.spi
and the addition of a determineJndiName(EjbDeploymentSummary) method on
JBossEnterpriseBeanMetaData that will load the policy if the default is needed. If there
is no policy it will use an
org.jboss.metadata.ejb.jboss.jndipolicy.plugins.EjbNameJndiBindingPolicy to derive the
jndi names from the ejb-name.
The ejb3 variations of these api can be noop subclasses for backward compatibility if
needed.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146482#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...