"scott.stark(a)jboss.org" wrote : anonymous wrote : This will fix JBMETA-42, but cause regression in ResolvedJndiNameUnitTestCase, which looks like it's testing for wrong resolved JNDI Names anyway. Base should be the EJB Name, not the Default JNDI Name, right? | No, if there is a given jndi name, it should be the unique root context for any other derivative jndi bindings. We are always given a jndi name in the tck tests, so this is what we are focusing on. The only time an ejb name should come into the picture is when there is no explicit jndi-name/mapped-name given. | That can't be. All jndi names must be unique or you'll get a NotContextException. As already shown by Andrews prototype, my original idea of having the object factory bound at at a base jndi name turned out to be a 'Bad Idea (tm)'. So the tests in ResolvedJndiNameUnitTestCase are out-dated in that respect. What I also said was that the final jndi name is overridable. So if a jndi-name is set in jboss.xml then beanMD.determineResolvedJndiName(KnownInterfaces.REMOTE, null); must return that jndi-name. This is just plain wrong in ResolvedJndiNameUnitTestCase. There is a side issue where JBossWS expects to find a home interface on the jndi name. This might also be the case for EJB 2.1 compatibility. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152274#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...