Hiya Tomasz. anonymous wrote : Yes it works. I'm impressed. Thanks, I aim to please ;-)
anonymous wrote : Ok. But still it is a workaround, although smart and works for this example. I wouldn't call it a workaround, just a clean design that refactors common code and is based on the JBoss API :-) anonymous wrote : But what about a whole aspect of before advice methods? To put, say persistance logic in one Aspect class. Not one separate interceptor for every core method (these 30 methods ;) ) . | You know: beforeGetCustomers(), beforeRentAHouse(), beforeAnotherCoreMethod(), etc.. | | It isn't so simple now. You'll end up with 30 interceptors (extend AbstractInterceptor) or one aspect extending MyCustomAspect where you'll have 30 methods like this one... ouh my.. I'm scared of the code I see.. I won't write it... I certainly wouldn't want to write it that way but I can think of two alternatives that are cleaner, depending on your use case. I must admit that if I was faced with an aspect containing 30 advices then I would be wondering whether the design was correct. Is this connected with your pervayler library? If so, we can take this offline. anonymous wrote : Wouldn't be it simpler to have: It would certainly be simpler for your 30 advices aspect. Personally I like the current implementation ;-) Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849699#3849699 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849699 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
