"wolfc" wrote : Some things can not be checked in metadata, because they require the correct class loader. I'd intended for these to be done from the context of the Annotation Processing Deployers, where the CL is available. "wolfc" wrote : In the end, somewhere in the deployer chain something like: | Set<InvalidConstraint<JBossMetaData>> violations = someValidator.validate(jbossMetaData, "ejb3"); | should occur. How about: Set<InvalidConstraint<JBossMetaData>> violations = new HashSet<InvalidConstraint<JBossMetaData>>(); | violations.addAll(ejb21ViewCompleteValidator.validate(jbossMetaData)); | violations.addAll(validBusinessInterfaceValidator.validate(jbossMetaData)); | violations.addAll(validEjb21InterfaceValidator.validate(jbossMetaData)); | ...etc... Then we can process all the validation failures and report them to the bean developer together, as opposed to failing on the first error only and hiding the rest. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4153026#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...