The deployers are aspect orientated in that each deployer deals with its own core responsbility.
Whether it uses an jboss-aop style container or an interface is an implementation details. PRO People could plugin aspects that are not deployers, but they could do the same thing using aspects on the MainDeployer? CON It places a dependency on the MC deployer on jboss-aop. A better dependency would be the container abstraction. On backwards compatibility, the MainDeployer needs to show the interface externally as now. Nobody should be directly referencing an individual deployer. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861464#3861464 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861464 ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
