A small update with some irony here. At the job I just finished today, we reached the conclusion that we weren't getting much value out of Karaf and pax-web; no criticism intended, we just don't dynamically provision, and we don't need any HTTP except for CXF services. So, over the last few weeks, we refactored the thing to use cxf-rt-transport-http-jetty in the Felix container, with our own rather tiny class responsible for launching. We lost a bit of flexibility in that we can't create an endpoint 'inside' of the namespace of another endpoint, but otherwise it works just fine. The code that that I showed James is hardly changed at all. The endpoint addresses now look like "http://0.0.0.0:nnnnn/base/whatever"; instead "/whatever". Maybe some day there will be an ultramicrobule that anticipates this mode of operation.
On Mon, Nov 21, 2016 at 7:13 PM, James Carman <[email protected]> wrote: > Small update. Microbule 0.1.0 release has been cut and will soon be > available in Maven Central (awaiting sync from Nexus OSS). Enjoy, folks! > > On Mon, Nov 21, 2016 at 1:03 PM James Carman <[email protected]> > wrote: > >> We've been working on a Microservices framework called "Microbule" which >> leverages CXF and Karaf (hence the cross-post): >> >> https://github.com/jwcarman/microbule >> >> The idea is to make writing Microservices easy and fun, by providing many >> of the oft-requested features for you out-of-the-box (CORS, Caching, JSON >> transformation, validation, etc.). There's a README page that explains how >> to install/run Microbule in Karaf and how to write your own services. If >> you're interested, take it for a spin and let us know what you think. >> >> Thanks, >> >> James >>
