I've found this explanation within the FUSE-Doc's: https://access.redhat.com/site/documentation/en-US/JBoss_Fuse/6.0/html/Getting_Started/files/Concepts-Injection.html
When I look at the web page of Spring-DM (http://www.springsource.org/osgi), then it seems that Spring-DM is dead.
This implied I should take blueprint xml, does it?
Yes, please use blueprint if you start a new project.
What are the limitations we may face if we use blueprint over spring DM. Since spring DM is completely Spring based i assume i can use all features of Spring with DM approach,
Also as per my understanding though spring DM is now dead, it was merged into Gemini project and which is still active.
According to me advantages of Blueprint over Spring XML quoted in links above are not really significant, Based on what criterias shall we decide whether to use Spring or Blueprint ?
Thanks for your answer in advance
this surely helps and is inline with my understanding. Apart from couple of advantages inside blueprint, spring has many features which are not available in the blueprint.
ffang - is there any specific reason why you proposed blueprint ?
Spring-dm 2.0 is named blueprint, there are a few blueprint implementations like Apache Aries blueprint, and Eclipse Gemini.
The Aries one is that we used in JBoss FUSE.