No ease of management that I'm aware of, it is just how the project was described to me originally.
It might be an idea to split out some of the integration points so they are available more a la carte e.g. At the moment they are mostly defined in the server module (along with some implementations like cmp or mdb). Obvious candidates in the server module are: invokers/proxy -> remoting invocation -> aop/microcontainer? container -> aop/microcontainer (if we really want to bother/risk migrating EJB2 to the new container) server/security -> security jmx -> management/jsr160 server/jndi -> naming etc. Although in general my preference is to have the integeration point in a separate module to the implementations. e.g. Both the connector and transaction modules define the interfaces, management, implementation and helper classes meaning the integration is ill defined and suspectible to being broken by people who don't understand the abstraction. This is abstraction is further complicated when a module has a client component. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860624#3860624 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860624 ------------------------------------------------------- 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
