I've made a start on this, but doubt I'll finish it before I finish for Christmas.
I am deprecating the @DisableAOP annotation. By default aop proxies will be disabled, but
can be enabled with @EnableAopProxy. Lifecycle callbacks will be enabled by default (and
I'll come up with a quicker way of determining if they should apply), but can be
disabled using the @DisableAopLifecycle annotation.
One issue that I need to look into is that there are a bunch of tests that run with
weaving enabled, so I need to see how they fare with this new setup. Since if they are
woven, aspects will apply, and if those aspects have dependencies we need those in
On 24 Dec 2009, at 10:47, Ales Justin wrote:
> +1, disable AOP wherever possible.
I guess we can go the other way now, disabled by default + make
lifecycle completely OO.
We should then definitely see good improvement.
> And I'd even dare say if you want @JMX, why not just
> implement it the old fashion with MBean interfaces? It's simple and fast :-)
You got that right, it's simple, probably too simple. ;-)
I think one would still like to use the real power of POJO and IoC and
just register it to MBeanServer for some simple admin/config.
I dare to say I think you need to re-read this article :-)
jboss-development mailing list