Some things can not be checked in metadata, because they require the correct class loader. For example whether a remote interface is really an interface and extends EJBObject. This is different for the annotation meta data creator, it has classes to work with. So it can do more checks. As a post condition it should not be allowed to create invalid meta data. I think the validations should be in jboss-metadata, but care must be taken that they should not be intertwined with code that performs a different function. In the end, somewhere in the deployer chain something like: Set<InvalidConstraint<JBossMetaData>> violations = someValidator.validate(jbossMetaData, "ejb3"); should occur. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152989#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...