[jboss-dev-forums] [Design of EJB 3.0] - Re: JBMETA-6, JBMETA-25 resolved jndi name

The DefaultJndiBindingPolicy does not accept the metadata. Rather it takes a summary of the ejb deployment/bean in question: | public interface DefaultJndiBindingPolicy | { | /** | * Returns the JNDI name that should be assigned to this deployment | * based on the information contained in the specified summary | * | * @param summary | * @return | */ | String getJndiName(EjbDeploymentSummary summary); | | String getDefaultRemoteJndiName(EjbDeploymentSummary summary); | | String getDefaultRemoteHomeJndiName(EjbDeploymentSummary summary); | | String getDefaultLocalHomeJndiName(EjbDeploymentSummary summary); | | String getDefaultLocalJndiName(EjbDeploymentSummary summary); | } | public class EjbDeploymentSummary | { | // Instance Members | private String deploymentName; | private String deploymentScopeBaseName; | private String ejbName; | private String beanClassName; | private boolean isLocal; | private boolean isStateful; | private boolean isHome; | private boolean isService; | private ClassLoader loader; | ... | // accessors omitted | } | The determineJndiName(EjbDeploymentSummary) on the base class just implements the default name based on the DefaultJndiBindingPolicy. The entity and session bean metadata still have the determineJndiName() which has the old logic as well as an overriden determineJndiName(EjbDeploymentSummary) which looks at the other sources of jndi names before defaulting to the superclass policy version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146525#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...