Hi JB, Ah yes, that was how we did it I believe when we were still running the 3.x version of Karaf. The approach I described earlier worked for Karaf 4.0.x, but no longer in 4.1.0 or newer.
It's been a while, but believe we preferred this approach for several reasons, including that we had no dependency on Spring and that we could embed the broker info inside a blueprint xml inside one of our bundles. This way the lifecycle of the broker was aligned with that of the bundle. At least in 3.x I also vaguely recall having issues with multiple versions of Spring being loaded. You don't happen to know an easy way to get mqtt-over-websockets to work with a blueprint broker config embedded in a bundle? -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
