Hi Chetan I think point #2 (cannot check for oak:Resource nodetype because Sling POST Servlet has no JCR dependency) indicates that we have an abstraction leak. I.e. the POST servlet needs to know the correct JCR node-structure despite the fact that it "officially" has no JCR dependency.
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. WDYT? Is that possible? Would it break backwards compatibility? Regards Julian On Mon, Oct 3, 2016 at 7:23 AM, Chetan Mehrotra <[email protected]> wrote: > Hi Team, > > Have a look at SLING-6090 where its suggested to avoid using > nt:resource. It also mentions few possible solutions. > > Kindly have a look and provide your feedback on which solution to implement > > Chetan Mehrotra
