Add to this mix the ejb3 metadata bridge which extends mdr with a facility to implement the logic of resolving the right metadata to an annotation. So you end up with a BridgedMetaDataLoader which has multiple MetaDataBridges. The actual implementations of MetaDataBridges are within the specific components, so for example ejb3-interceptors has all the knowledge of interpreting annotations and metadata. That's how I would like to keep: the functional component dictates that logic. Right now the connection between an AOP domain and the EJB is coded in Ejb3Deployment. So on an EJB container (which delegates to a ManagedObjectAdvisor) has the full view of all annotations. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161701#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...