You'll have to show me why it is easier. Take the pathological case:
1) A bean is requested to be deployed that has the security annotation, BUT the bean class is not deployed yet so we don't this yet. 2) When the bean class is deployed it then knows it needs to add the aspect and metadata, but the aspect class is not deployed yet. It does know enough to add the metadata to construct the aspect once the class is available. 3) The aspect class is deployed we can look at it and see whether it has other dependency injections. etc... Once all dependencies are satisfied it can then fully construct the aspect, meaning it can construct the container which in turn means the bean is now fully deployed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861602#3861602 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861602 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
