For now I've deprecated the "determine" logic from the Object Model (see JBMETA-68) but EJB2.x still relies on these methods. So the new EjbMetadataJndiPolicyDecoratorDeployer will decorate EJB3 deployments only with a JNDI Binding Policy. So adding new JNDI Policies later should be a natural progression towards providing an EL-based implementation. The hitch here is that jboss-metadata tests are not for EJB2, and these are not backwards-compatible (because they're not wrapped ie. getJndiName uses the old logic). So MappedReferenceMetadataResolverDeployer must still reference the @Deprecated methods I'd like to remove. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4164385#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...