It is the org.jboss.metadata in the container project. The three major parts that need doing are: 1) Creating the composite metadata tree from the key scopes 2) Mechansims to deploy metadata at different scopes 3) Adding constructor, method, parameter annotations to the api. I've outlined (1) elsewhere, but it is not trivial because of the "feedback" used to construct the tree, e.g. the deployment determines the cluster. (2) is really an issue for the deployers (3) needs to define a "joinpoint notion" so you can for instance say I want to override the annotations/metadata for this method/constructor I didn't look at how you did this with the org.jboss.repository stuff I stopped doing this before to work on the deployers but now I've got to the stage where I'm going to get back to it with the deployment metadata population/overriding. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3981347#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...