anonymous wrote : What type of simplicity are you talking about? I was talking about the simplicity at runtime, i.e. calling the aspects, and not during bytecode annotation.
anonymous wrote : The case we're discussing (types of advices) is simple to imagine. Come on.. It is very simple to imagine and to implement but it is a syntactic modification to the interceptors, not a necessary one (which I think was Bill's point). There is no 'missing functionality' as the results can be achieved with the current code. anonymous wrote : Yeah, and I thought for a moment aspects and AOP frameworks were for ease of development.. They are but you still have to write the aspect before it can be of use. Hopefully I have done that, or at least started, with the code I supplied. anonymous wrote : What about other people who will need similar functionallity as I? Will we tell them: use try-catch-finally or adopt Kev's sollution? I would hope that they would look at my solution, think about improving it and then use what they feel fits best. Think of my solution as the PrintWriter that surrounds the Writer ;-) Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851308#3851308 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851308 ------------------------------------------------------- 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
