Guillaume, We recently went through the same thought process and standardized on Blueprint. The major reason why is blueprint is supposed to the the standard way of doing it in OSGI (per the spec). Also, Spring-DM is actually no longer a supported standalone project, it's been transitioned to Eclipse Gemini Blueprint which won't officially be supported until Karaf 3.0 (ServiceMix ??).
Chris On Thu, Mar 15, 2012 at 9:22 AM, PAC Kieffer Guillaume < [email protected]> wrote: > Hi, > > I would like to have your opinion on what could be the best container to > choose for OSGi bundles deployed on Servicemix 4 ? > Starting from scratch - Shall we start with Spring DM or blueprint ? > > It seems they are both pretty the same, but nearly all readings I get, > describes Camel Spring projects... > It seems that Spring DM is more prowerful in terms of bean management, > autowiring capabilities.. transaction management, and comes out with a > tremendous number of extensions.. > I do not find any clear info (beside the spec) on blueprint but it appears > to be the standard in the OSGi world and may be wider used and adopted > within the new versions.. > > Thanks for the clarification, > > Guillaume. >
