This is one we've known about for some time, and I'd like to get a definitive plan together and stick to it.
The metadata provided by jboss-metadata does not account for an AspectDomain (ie. information that may have been tacked on by AOP), and right now we've got two models:
* EJB3 Core (container.getAnnotation(MyAnnotation.class)
* jboss-metadata (myMetaData.getMyAnnotation());
In EJB3 Proxy I'm using the jboss-metadata model, which due to being an incomplete view, regresses the EJB3 TestSuite "defaultremotebindings" for example.
<!-- This is not available in JBossSessionBeanMetaData presently --> <annotation expr="!class(@org.jboss.ejb3.annotation.RemoteBinding)"> @org.jboss.ejb3.annotation.RemoteBinding (jndiBinding="DefaultedStateless", factory = "RemoteProxyFactory", interceptorStack="", clientBindUrl = "") </annotation>
I have a todo to review the aop deployers to see how they can define a management view of the aspects in a deployment. We certainly need to be moving towards some annotation metadata. Both BeanMetaData and ServiceMetaData have this notion.