November 29, 2001
"[...] btw, have I mentioned that AOP is cool? No?
uhm.. it is.. you'll see.."
July 23, 2003
"AOP itself is great but what is interesting are the aspects
built on top and middleware we build out of them. AOP for the
beauty of it isn't really relevant to system designers. AOP for
systems is nirvana though. [...] middleware aspects are AOP's
September 23, 2003
"Note that most framework of AOP DO NOT BOTHER WITH THE ASPECTS. They
don't ship "aspects" they define frameworks for them (including JBossAOP),
which is why we all talk about the "logging" aspects which btw may not be
the best candidate (it is very contextual) but that is another discussion.
THE CROWN JEWEL OF AOP in MIDDLEWARE are the aspects themselves.
JBoss 4 ships aspects."
September 28, 2003
"Applicability of AOP. What kind of problems are solved with AOP?
in my mind insertion of really orthogonal concerns in the flow.
That is why middleware is so relevant as an AOP enabled framework.
AOP for applications? I will doubt until proven wrong (not to say
that I am right on that point). EXTENSION of user applications with
TheServerSide TechTalk interview
"I think AOP is going to be very, very important. I think in the long term AOP
is going to change the way we design applications. I think in the short to
medium term, itís going to have a significant effect on J2EE, primarily,
as a replacement for EJB. As Iíve said, I think that EJB is a transitional
solution to AOP middleware. I think AOP generalizes a lot of the ideas
that we successfully applied in EJB, and makes them both more powerful,
but eliminates a lot of the downsides of EJB. For example, declarative
transaction management is one of the nicest features of EJB. But, in fact,
we can implement this in a simple way using an AOP framework. So I think
weíll be hearing a lot more about AOP, both in the next one or two years
as it becomes a popular replacement to EJB and in the next 5 to 10 years when
it really changes the way we design applications."