"scott.stark(a)jboss.org" wrote : The org.jboss.metadata from the metadata project, for example: | https://svn.jboss.org/repos/jbossas/projects/metadata/trunk/src/main/java... | | is not usable as a replacement for the server project version, because its abstract. Its also not a complete replacement for the existing version. How was this generated, and why is the MethodMetaData abstract? | It isn't possible to provide a complete mapping of some of the metadata without going through a long winded and unnecessary mapping/combining process of the different parts of the model. The method metadata is stored in multiple places. If we'd had interfaces in the correct places in the original model then we could do a lot more. In practice it isn't necessary. The MethodMetaData is never accessed for everything all at once. So we just provide delegates for the aspect where it is used. e.g. There is a getTransactionMethods() in the old BeanMetaData so we create a delegate that only gives access to the transaction attributes of the method. Or similarly for permissions. https://svn.jboss.org/repos/jbossas/projects/metadata/trunk/src/main/java... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086033#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...