The nice thing is, most of the Spring-DM samples can be used for blueprint, too.
regards, Achim 2012/3/15 PAC Kieffer Guillaume <[email protected]>: > Hi Chris, > > I went through so many examples with Spring.. that's why I was wondering. > > Thanks for your quick reply and the clarification. > > Regards, > Guillaume. > > -----Original Message----- > From: Chris Geer [mailto:[email protected]] > Sent: Thursday, March 15, 2012 17:27 > To: [email protected] > Subject: Re: ServiceMix 4/Camel: Blueprint or Spring DM ? > > 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. >> -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
