ejb-local-ref is not resolving to metadata localJndiName -------------------------------------------------------- Key: JBAS-5499 URL: http://jira.jboss.com/jira/browse/JBAS-5499 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR1 An ejb-local-ref like: <ejb-local-ref> <ejb-ref-name>ejb/CMP20CalleeLocal</ejb-ref-name> <ejb-ref-type>Entity</ejb-ref-type> <local-home>com.sun.ts.tests.common.ejb.calleebeans.CMP20CalleeLocalHome</local-home> <local>com.sun.ts.tests.common.ejb.calleebeans.CMP20CalleeLocal</local> <ejb-link>CMP20CalleeLocal</ejb-link> </ejb-local-ref> with a jboss.xml like: <entity> <ejb-name>CMP20CalleeLocal</ejb-name> <jndi-name>ejb_ee_bb_session_stateless_argsemantics_CMP20CalleeLocal</jndi-name> </entity> is resolving to the jndi name rather than the local jndi name: ess.argsemantics.CallerBean +++ejb-local-ref(ejb/CMP20CalleeLocal) -> mappedName=null| resolvedJndiName=ejb_ee_bb_session_stateless_argsemantics_CMP20CalleeLocal +++ejb-local-ref(ejb/CMP20CalleeBothLocal) -> mappedName=null| resolvedJndiName=ejb_ee_bb_session_stateless_argsemantics_CMP20CalleeBoth It needs to resolve to the metadata determineLocalJndiName() since that is what the BaseLocalProxyFactory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira