Hi, After playing a while with the features list of ServiceMix, NMR, Camel and Karaf, I have discovered that we have some discrepancies between the different files. This is really painful for users having to package solutions and wanting to use a modular solution based on OSGI specification.
Moreover, I'm convince that if we want that ServiceMix 4 (or Fuse) becomes an important player in the field of Enterprise Application Server (designed around OSGI) and including ESB, Web, EJB, JPA, ... containers, it is absolutely necessary that we improve what is already packaged in ServiceMix 4 but also the documentation. Without such approach, the future of Servicemix 4 will be dark compare to what GlassFish v3 / Websphere Application Server v7 + Aries / Glassfish v3 already propose. Action plan: - Refactor the features file of ServiceMix 4 to include more features (even if we have to copy/paste them from Karaf like HTTP feature, Spring, Spring-DM) - Add support for Blueprint, Aries application to deploy EBA archives - Add JPA, JTA, ... containers - Work on documentation to present ServiceMix 4, how to install it, start/stop it, debug, install examples, ... An alternative for J2EE features like EJB, Web Container could be that we work in collaboration with existing Web Application Servers to integrate ServiceMix 4 in. In this case, it really depends on the positioning of ServiceMix 4 / Fuse in the future : - standalone application server (we depend on people in charge of infrastructure and so could be seen as a competitor of existing application server for which resources to administrate them exist and have the knowledge, ...), - server embedded in Web Application Server (more visibility, can reduce project risk, project can be designed using J2EE or OSGI Enterprise specifications, ...) - standalone application server providing also J2EE features Remark : What I present here comes from discussion that we have had with Jean-Baptiste Onofré. Regards, Charles Moulliard Senior Enterprise Architect Apache Camel Committer ***************************** blog : http://cmoulliard.blogspot.com twitter : http://twitter.com/cmoulliard Linkedlin : http://www.linkedin.com/in/charlesmoulliard Apache Camel Group : http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
