Re: [Springframework-developer] TSS Symposium: Warning British/Australian humour

[Rod J. <rod...@in...>]

>I really like our AOP strategy: Just intercept methods of specific
instances, not everything of any class loaded in the current classloader. Of
course, this isn't as powerful as "full" AOP on fields etc - but the latter
is power that I don't want anyway. We can achieve EJB-style functionality
like declarative transactions and security easily, that seems more than
enough to me for now.

Anyone say "Pareto Principle"? It's also nicely isolated, in that each
business object can have different advice if necessary. I've just expressed
that view to Gregor Kiczales on the AOP Alliance list. (Btw, if you're
interested in our AOP, please subscribe.)

I feel that when I've finished it, our souce-level metadata option will
simplify AOP usage and drive all our competitors to complete despair. Spring
developers will not only walk through walls : they'll levitate far beyond
the leaden chains of EJB. We'll define the new paradigm. In fact we'll be so
far ahead our competitors won't be smart enough to understand our paradigm.
All your AOP _and_ J2EE  Belong to Us. (Did I mention that we'll cure third
world debt?)

Rod