So this was likely introduced in tandem with fixes for JBMETA-78. http://fisheye.jboss.org/changelog/JBossAS/?cs=76015 So the tests were also aligned to match: http://wiki.jboss.org/wiki/DevJNDIBinding ...which *does* call for a base name in EJB2.x Homes. Or are we confusing "EJB2.x Homes" for "EJB2.x View of EJB3"? If so, can we further remove *all* determine* logic from the object model and apply the LegacyEjbJndiPolicy to EJB2.x deployments via a new Deployer, much like I'm doing w/ BasicJndiBindingPolicy for EJB3? We're *still* fighting against each other in circles. :) I think the refactoring done in jboss-metadata to remove the JNDI Policy from the caller is the right direction in which to head, but please let me know how to want to handle the above. Also note, BasicJndiBindingPolicy *is* for EJB3...EJB2.x should be using another policy. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166047#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...