Kabir Khan wrote:
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.
I think you should be testing your changes to see if they actually
You can test it by emptying deploy/ and removing weld and
jbossweb.deployers from deployers directory. You should be able to see
significant improvement as you disable AOP bookkeeping and matching.
IMO, we should just remove AOP entirely as our customers probably are
not going to use it. For @JMX just write another deployer and do it
regularly. Similarly with lifecycle and other features.
Again, if you want to take this route, I'd be happy to do the work. I
am willing to spend the next month on boot performance and AS.
JBoss, a division of Red Hat