You don't really need karaf-boot to generate static karaf instances. Just use the maven karaf plugin and configure it properly and you're done.
Karaf-Boot is more about helpers, recipes, examples, but if you already have your application that can be deployed, I don't think you need it. 2016-04-22 17:17 GMT+02:00 Brad Johnson <[email protected]>: > When is karaf-boot due out? Roughly. 2016? August? September? 2017? > > I'm pretty stoked about it because I think it is really going to open a > lot of vistas. I haven't had a lot of time to fiddle with my Raspberry Pi > but when i think about a self-deploying, thin karaf with all dependencies > and all the OSGi capabilities and libraries that's pretty astounding. > > The testing seems like it would be straight forward for things like black > box web testing. In that sample code I posted the other day you could see > a couple of simple fluent clients I use for create SOAP and REST clients > for testing. > > It would appear that without using Pax Exam or CamelBlueprintTestSupport > I'll be able to boot a karaf container and run tests against it if I expose > any web services. I'll commonly create delegate/adapters that can switch > based on configuration between using an internal set of Test stubs and > actual implementations and sometimes even remote implementations. The test > stubs I use always provide models that reflect what the bundle would be > receiving from any endpoint calls it makes so it permits me to exercise the > validators, transformers, business logic and web services without having > any integration in place. > > Being able to use plain ol' Junit (Poju?) and send and receive web service > calls that exercise self-container karaf/OSGi bundle sets is pretty damned > exciting. > > Brad > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: [email protected] Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
