While working on some of the integration points for ejb3-nointerface component, i noticed that the ejb3-deployers-jboss-beans.xml in "core" has MC beans from across various other components (like ejb3-deployers) on which "core" never even depends (not even transitively). For example, we have the: | <bean name="Ejb3MetadataProcessingDeployer" | class="org.jboss.ejb3.deployers.Ejb3MetadataProcessingDeployer" /> The org.jboss.ejb3.deployers.Ejb3MetadataProcessingDeployer comes in from the ejb3-deployers component on which core has no dependency. I am planning to move that bean definition out to a ejb3-blah-what-do-we-call-this-jboss-beans.xml in the ejb3-deployers component. This way, it will be more tied to the ejb3-deployers component and any changes to the bean internals, in a new version can be managed within this components. Any thoughts around this? Although it doesn't directly affect backward compatibility (i.e. we still ship this bean, although in a new file and a different component) is there anything else that i should be concerned about while moving this? P.S: This is just one example. There are many other MC bean configs in that file which probably need to be moved to their own components. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269645#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...