I have implemented this for ClassContainers and ClassAdvisors http://jira.jboss.com/jira/browse/JBAOP-575 See the linked JIRA issues for outstanding tasks related to this. For AS startup, I have only focused on ClassContainers for now, since they are used by the proxies used in AS 5, i.e. there is no weaving involved. For the "default" config on my machine, the startup time has gone from 34s to 28s. For "all" from 48s to 42s. Basically when adding bindings, we only add the new binding to the end of the chains for the existing advisors. This causes slightly different behaviour if we have an advisor with an instance domain in GeneratedAdvisor mode, since then bindings for the class-level domain are handled before the bindings for the instance domain. Now, the last added is added to the end of the chain regardless of what domain level it is added to. However, precedence rules are still calculated following an added binding, so that can be used to determine the order where critical. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4151827#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...