On Mon, Dec 29, 2008 at 9:12 PM, Clement Escoffier <[email protected]> wrote: > Le 29 déc. 08 à 06:35, Trejkaz a écrit : >> (Immediate thoughts here... why is it forcing me to install the web >> console when I really only wanted/needed the shell commands mentioned >> in the tutorial? And why is it listing v1.0.0 of the web console as >> optional when v1.2.0 is already required? And why is it installing >> v1.0.0 despite having called it optional?) > > I agree, there is an issue. The configuration admin bundle is described as > follows: >[cut] > > So despite that some requirements are optinal, OBR tries to revolve them. I > will try to understand from where comes the trouble. > > I have something close to you. But there is a not clean solution for the > time beeing: > obr deploy "Apache Felix Configuration Admin Service" > And then start the config admin bundle.
This is clean enough for me. Along these lines I took a copy of the bundle for the admin service itself, and installed (started) that by itself. That seems to be enough to make it work... or at least to make the parts I'm using so *far* work. It looks like its dependencies are satisfied entirely internally (which would make all those other dependencies obr suggested... optional? Even though it claimed some were required. Very interesting.) > No, there is no OSGi-code, except for pushing configuration in the > configuration admin. But this service is quiet easy to use and with an iPOJO > dependency, you can avoid tracking the configuration admin service. It's proving to be quite useful in cutting down on a lot of cases which would normally require the tracker, yes. Anyway, following that tutorial (the code was very helpful) I've managed to make a command to manage my custom configuration now and all seems to be working happily. The first of many shell commands for me, I imagine... :-D The only truly awful part of OSGi left in any of this is yes, interfacing with ConfigurationAdmin and mostly its love of Dictionary over Map... I don't suppose Felix happens to have convenience API hidden in some bundle to make that easier... TX
