Hello! I'm a newcomer to Karaf, and would have a question regarding the integration with Spring DM 2. I have an existing Karaf/Blueprint project and would like to use spring DM as it offers advanced DI features as well as a nice way of performing integration testing.
So I spent a good part of the day fighting (and understanding) how Spring DM deals with custom namespaces, and was able to deploy a bundle with Spring-DM 2.0 on Karaf. For doing so I created a custom provision file and registered spring dm 2 as a feature. Karaf 2.1 seems to come by default without Aries installed so I didn't have any conflicts occurring there (or so I think at least). I mean I didn't see Aries running when performing a osgi:list. The issue I have now is that we use the Karaf shell extensions in order to talk to our bundles via the console. This worked nicely with a <command-bundle> declaration as long as I didn't inject dependencies with spring (but wired them via hand). Now, spring not being the one initializing the shell <action> classes, the dependencies are not initialized. My questions thus would be: - how does the shell console look for it's extension points? Will it only look in <command-bundle> definitions in a OSGI-INF/blueprint path, or would it in theory be fine if the definition were in a spring bundle-context definition file (with a custom namespace mapping). My aim would be to have spring initialize the instance (and wire its dependencies) but still have the shell know about it / how to talk to it. - it looks like http://karaf.apache.org/xmlns/shell/v1.0.0 isn't online, whilst that would be handy to have - does what I am trying to do make any sense at all? (I'm rather new to the latest OSGi spec, and am not sure what the usual practices are) Thanks! Manuel
