|
From: Eugene K. <eu...@md...> - 2005-08-29 14:02:15
|
Alexandru Popescu wrote: >>> This looks to me pretty unintuitive, because we are talking about >>> after advices. The rules you are exposing are correct, but they apply >>> to around advice. I imagine that this is caused by the fact that >>> Spring doesn't have real before and after advices, but rather it is >>> emulating them using always around (this is true for all proxy based >>> aop solutions). >> >> >> First of all there are explicit Before and After advices >> semantically possible with Spring. It has very little todo that actual >> implementation is using proxy, which is always gives an around advice. > > imo it doesn't matter that you are implementing Before or After as long > as you refere to them as advices/interceptors and they are proxies. You > will always have this ordering, because they are in fact around advices > and the rules for around advices are those exposed before. > > this is just my opinion and I don't see any gain from continuing an > argument on this matter :-). Right. My point is that there is only one collection of advices in Spring bean definitions, so all advice tytes has to be somehow unified and there is nothing wrong to unify them all around advice. And if you think about it this way it is quite intuitive. :-) rergards, Eugene |