Re: Defining new content types and associated import actions

On Saturday 06 December 2014 08:00:41 Felix Meschberger wrote: Hi Bruce hi, I think you are on the right track. ContentReader would probably help solving your problem. Yet, for now the content loader is not extensible — by intent because we didn’t have a need for making it extensible so

Re: Defining new content types and associated import actions

Felix, that sounds damn near perfect. I can work on a folio import service now, given those assumptions. I can build it into the internal API now and migrate it over later, and if no one objects, contribute it as an optional extension. -Bruce From: Felix Meschberger

Re: Defining new content types and associated import actions

Hi Oliver, Was there a reference intended from the [1] in your message? I’m interested in what you may have planned. -Bruce From: Oliver Lietz apa...@oliverlietz.demailto:apa...@oliverlietz.de Reply-To: users@sling.apache.orgmailto:users@sling.apache.org

Difference between jackrabbit-oak distro vs sling embedded oak?

What is the difference between the version of oak that's embedded in sling bundles/jcr/* and the github https://github.com/apache/jackrabbit-oak.git oak distribution? I understand the benefits of sling, but I'd like to know what I may be missing compared to using oak directly. -Bruce