"adrian(a)jboss.org" wrote : I've committed this change. It's not really the full thing. | | Instead of using metadata directly, I've had to hack a subclass of AOP's | AnnotationRepository. | | This is because | 1) There are many places in EJB3 using the annotation repository directly | instead of advisor(container).resolveAnnotation or invocation.resolveAnnotation. | These just need fixing I'm thinking to make the Advisor an association of the EJBContainer instead of a super class. What do you think about that? For annotation (/metadata) resolving there everybody must use the getAnnotation methods on the EJBContainer. ResolveAnnotation is also not allowed. "adrian(a)jboss.org" wrote : | 2) The use of metadata rather than AnnotationRepository is not complete | in aop advisor's. | | Both of these need fixing. | | I also don't register the metadata in the metadata repository yet. | This is because I couldn't locate a reliable place to do the (un)register | where it wouldn't leak. | The ejb3 container lifecyle handling needs tidying up (defining properly?). | This is where the trouble of aop.xml starts. If it's augmenting we must have it before we process metadata. If it's using then it must run after processing of metadata. We keep pushing this forward to see how far we can get. The lifecycle itself should be according to http://wiki.jboss.org/wiki/Wiki.jsp?page=EJB3Q32007 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107662#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...