"david.lloyd(a)jboss.com" wrote : | To me it makes more sense to restrict our usage of on-demand beans to deployments that are only activated if a user deployment consumes it declaratively (in other words, beans depend on beans; methods do not depend on beans). | | Also, and I only speak for myself here, I'm personally really hesitant to invest more into AOP, given that AOP appears to be at least one key source of the performance problems that we have right now. To do on-demand properly, we do need a first request activation mechanism. However, it seems like using an activation aspect is overkill. Why can't the API just be simplified, or better yet automated on first non-lifecycle MC method access. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228780#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...