On Mon, Oct 3, 2016 at 2:06 PM, Julian Sedding <[email protected]> wrote: > In an ideal world I would decouple the logic of what constitutes a > file, i.e. create an API/convention in Sling, that is JCR agnostic and > move the JCR-specific implementation to the JCR ResourceProvider > bundle.
In an ideal world probably yes. That would require decent amount of refactoring of existing code. Current code already uses JCR nodetypes, just that it inlines the constant names and does not have a direct dependency on the API In real world I am looking for least intrusive change here :) Chetan Mehrotra
