Hi David,
in fact, Blueprint is the specification and Spring DM is the reference
implementation of blueprint.
So you can use Aries Blueprint exactly as you use Spring DM.
Especially, Aries Blueprint is more flexible with namespace than Spring DM.
Aries implements all Blueprint specification and is a "mature" project
(even if the versioning is still 0.3-incubating :)).
It's used in Apache Karaf and Apache ServiceMix in stable release.
Regards
JB
On 12/28/2010 03:18 AM, David Erickson wrote:
Hi there-
I am currently using Spring and Spring DM in my application. We
export Spring beans using DM as services, and consume them from other
bundles. I haven't used the Blueprint portion of Spring DM yet, but I
am curious if I can use Aries' Blueprint implementation and interop
with Spring in the same way I am currently using Spring DM? IE can I
use both namespaces from the same XML file, share beans back and
forth, etc? Can Aries create the Spring contexts for each bundle, or
is that out of scope? And if so do you have a suggestion on how to
maintain that functionality?
Also how mature is Aries, does it fully implement Blueprint? I saw it
recently was graduated to a top level project (grats)..
Thanks,
David
