[jboss-dev-forums] [Design of POJO Server] - Re: appclient remote home regression

scott.stark@jboss.org do-not-reply at jboss.com
Tue Jul 22 15:35:17 EDT 2008


So 


  |                // Determine the jndi name for the reference interface
  |                String iface = getInterface(ref);
  |                //LegacyEjb3JndiPolicy policy = new LegacyEjb3JndiPolicy();
  |                String containerJndiName = target.getBeanMetaData().determineJndiName();
  |                if(containerJndiName != null)
  |                   ref.setResolvedJndiName(containerJndiName);
  | 

and the metadata determineJndiName() is implemented by JBossSessionPolicyDecorator.determineJndiName(), which calls JBossSessionPolicyDecorator.determineResolvedRemoteBusinessDefaultJndiName(). This is for an ejb3x remote reference, not an ejb2x remote home reference. The call to getInterface(ref) is unused. The resulting iface should be getting passed into determineResolvedJndiName(String iface) so the iface can be recognized as a home rather than a remote business interface. 

What we need is a comprehensive metadata unit test that takes each type of ejb reference metadata, and resolves a jndi name for both ejb2x, ejb3x bean metadata. This is what the MappedReferenceMetaDataResolverDeployer needs to set each reference resolved jndi name.


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

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



More information about the jboss-dev-forums mailing list