JBoss development,
A new message was posted in the thread "Optimizing aop lifecycle":
http://community.jboss.org/message/518420#518420
Author : Ales Justin
Profile :
http://community.jboss.org/people/alesj
Message:
--------------------------------------------------------------
Anyway, the question I really had was: am I ok to expose the
add/removeAnnotationPlugin() methods in the BeanAnnotationAdapter interface
No. :-)
That is useless impl detail, that shouldn't be part of BAA.
This is what I would do
(1) expose Default/Common BAA as a bean, with callbacks on add/remove plugin (we
might/should already be doing this)
(2) re-write <lifecycle-x> element to BeanMetaDataFactory handling to do config
checks, and then produce LifecycleAnnotationPlugin bean
This way (1) will pick up (2), w/o any need of knowing add/remove plugin impl detail
--> less code as you don't need that last few lines; start, stop, getBAA. ;-)
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/518420#518420