Chetan Mehrotra wrote > On Mon, Oct 3, 2016 at 3:30 PM, Carsten Ziegeler <[email protected]> wrote: >> And then all scripts or code dealing with nt:resource fails as the node >> or resource type is now oak:resource ? > > Yes if the code checks if nodetype of jcr:content node under nt:file > is of type nt:resource. So far my reading of code is that code does > not rely on specific nodetype but just that node name is 'jcr:content' > as that is defined in nt:file nodetype definition itself >
Hmm, ok - in general this is nothing Sling should deal with. I think if oak:Resource is the better option, why can't do Oak the right thing? Why do we have to add workarounds on top in Sling? And if someone is not using the post servlet then it's again nt:Resource. Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
