Steve, can you please expand a bit on what you mean by "without really being "container aware"" and "leverage services or interact with the underlying container" as we use Spring DM but are not sure what we are missing out on by not switching to Blueprint. As far as I can see Spring DM can "leverage services" with a similar end result from the user's point of view i.e. mechanics maybe different but with Spring DM a service can be provided and referenced, can come and go etc.
-- View this message in context: http://karaf.922171.n3.nabble.com/Spring-vs-Blueprint-tp4035374p4035578.html Sent from the Karaf - User mailing list archive at Nabble.com.
