My problems with Proxies and Scott's with JNDI Metadata have converged here. The solution that will enable us to further decouple and get resolution more in-line with the current direction is to add the "resolvedJndiName" property accessors to JBossEnterpriseBeanMetaData, effective metadata-1.0.0.Beta12. It'll then be the responsibility of the MappedReferenceMetaDataResolverDeployer to properly resolve the JNDI name in the case of @RemoteBinding overrides. An issue exposed here is that @RemoteBindings(Array) is non-deterministic at the class level in the case that more than one interface is defined on the bean. For now, I'll assume that each @RemoteBinding in the specified array should be used on each of the business interfaces (creating multiple bindings). Still to be covered is the handling of "getInvokedBusinessInterface()" under this mechanism, I'm looking into those tests now. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4148716#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...