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
