I think the misunderstanding comes from the two different use cases. In the pure AOP case you don't have all the dependencies and you are doing lazy xml parsing. i.e. this is the case where you are running inside somebody else's container and expect all the dependencies to be satisfied. This is a pure IOC play.
In the microcontainer (MC) we are going further. We don't make any assumption about dependencies. We let the user specify everything upfront and then through it at MC to sort out the correct order (including creating classloaders binding/lookup to jndi, etc.) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861445#3861445 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861445 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development