We need to change our deployment mechanisms to be focused on an object metamodel rather than a mismash of annotations and a metamodel. The idea of using annotations as a metamodel was interesting but a failure. Why do we need to do this? Well, in JBoss 5, different layers will need to be able to override/modify deployment metadata. For example, EAR metadata may introduce security role mappings or a default security domain. Another reason is that the profile service may want to override and serialize an object model so that a management tool can change metadata at runtime. Once we get the current deployers ported and working for the JBoss 5 model, we need to go back and refactor things. Bill View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977298#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...