Hi All, OK.. Based on your comments, here is a little summary:
- Spring (alone) may be used within an OSGi Container but it is not fully compliant for this environment (classloading issues.. namespace handling..) - Spring DM is (was ;) the OSGi compliant version of Spring. - Blueprint Standard was originally designed out of Spring DM. - Spring DM has moved to Gemini Blueprint. - Gemini Blueprint (Eclipse) as well as Apache Aries are different implementations of the OSGi blueprint Standard. - Aries is the implementation integrated within Servicemix. As it is fully my project is a Servicemix bundle, I will then go for blueprint ;) Thanks again, Regards, Guillaume. -----Original Message----- From: Jean-Baptiste Onofré [mailto:[email protected]] Sent: Thursday, March 15, 2012 18:23 To: [email protected] Subject: Re: ServiceMix 4/Camel: Blueprint or Spring DM ? Basically, another "guide line" is: - to use Blueprint, you have to be in an OSGi container with Blueprint support - if you choose Spring (and pure Spring, not Spring DM), even if it can work in ServiceMix, it can also work "outside" of OSGi (in Tomcat for instance). Regards JB On 03/15/2012 05:22 PM, PAC Kieffer Guillaume 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. > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
