This is in regards to EJBTHREE-617 Maybe a generic metadata facility would be a better approach rather than a specifc jndi binding setting in jboss-app.xml? This way EAR subdeployment types can evolve without having to change EAR Deployer code. EARs already have the concept of additional metadata. This probably coincides with the Profile service as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3956970#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...