[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [aspectj-users] Drawbacks of AOP
|
> To me this is the kind of thing that should be handled declaratively in a deployment descriptor and
> applied by some sort of runtime container (not nesc. EJB, but along those lines). To me, implementing
> things like transaction management, security, etc. as an aspect leads to hidden complexity and thereby
> can render the code unmaintainable.
...
> I certainly agree with you that these crosscutting concerns don't belong in the code itself, but I just
> think the deployment descriptor approach is a better one than using aspects. Just because we can solve
> these problems with aspects, doesn't mean aspects are the best way to solve these problems. These
> concerns are the kind that should be handled in a container or runtime framework in my opinion.
That's identical, though. One could write an aspect that parses that exact same deployment descriptor and accomplish the same thing with an aspect.
It's simply a matter of syntax for maintenance.
-joel
