On Mon, Aug 3, 2015 at 8:14 AM, Clay Ferguson <wcl...@gmail.com> wrote: > I looked at that readme page (oak-pojosr). I like the idea of simplifying > use of osgi, or embedding it. It reminds me a bit of how SpringBoot actually > embeds an instance of Tomcat, so deployment is simple and easy for web apps. > > Having a totally prepackaged way of doing stuff is what most developers want > these days. There are just too many moving parts in most large systems, so > people need "prepackaged" configurations that just work right out of the > box, at least for some minimal set of the most common usage patterns. I'm > not sure if there's any plans to integrate into SpringBoot, but IMO that > would be a hugely important thing for the industry if Oak was part of > SpringBoot stack.
I'm not an Oak developer, so don't take this as any sort of official statement, but the way I understand it the Jackrabbit project only provides the Oak code / binaries ; packaging it in suitable formats for development / deployment is left to packagers / other projects. One such example is Apache Sling ( https://sling.apache.org ), a framework built on top of JCR, REST and OSGi. But if you're well-versed in Spring and convinced that you should switch to OSGi it won't help you much. In that case "someone" ( it's always someone else :-) ) should provide that integration. Cheers, Robert -- Sent from my (old) compute
