Btw, feel free to experiment deploying both aries blueprint and spring-dm 2.x in karaf and see what happens. I haven't really tried, but i envision a lot of problems, that's what I didn't even bothered trying until there is a real need for that. I guess the ideal solution would be to have custom namespaces for both implementations using the same schema, but the startup ordering problems will always happen with spring-dm, whereas they should not with aries blueprint. That's a problem which Dan Kulp is investigating in ServiceMix and we're about to switch from spring-dm to aries in the very short term.
On Tue, Jun 29, 2010 at 17:26, Guillaume Nodet <[email protected]> wrote: > Well, that would be nice, but I don't think it's that easy. > The problem is that spring-dm 2.x implements blueprint, so we'd end up > with 2 blueprint extenders. > That would not be a problem if we had no custom namespaces, but we > actually use some and those are not necesseraly implemented for both > aries blueprint and spring-dm. > Not sure really how to do that for now ... > > On Tue, Jun 29, 2010 at 17:22, Charles Moulliard <[email protected]> wrote: >> Is it planned to migrate SpringDM from 1.2.x release to 2.x ? >> >> Charles Moulliard >> >> Senior Enterprise Architect (J2EE, .NET, SOA) >> Apache Camel - ServiceMix Committer >> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> Blog : http://cmoulliard.blogspot.com | Twitter : >> http://twitter.com/cmoulliard >> Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard >> > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
