before/after returing/after throwing could easily be added to JBoss AOP with a day of work,
But.... Again, I still see this as nothing more than you wanting to avoid having a try/catch/finally block, or to avoid calling invocation.invokeNext(). IMNSHO, ordering of aspects and how the aspect is executed in the Java call stack is very important to understand as an aspect developer. A smaller API is always better IMO. IMO, you're just talking about syntax sugar here and I'm still not convinced that the semantics of around don't give you what you need. Bill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851144#3851144 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851144 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
