On Monday 03 October 2016 13:43:44 Chetan Mehrotra wrote: > Hi Oliver, Hi Chetan,
> Defaults for nt:resource was changed in JCR 2.0 and it was made > unreferenceable. See [1] for some background. However JR2 and then Oak > continued to use the older definition for compatibility purpose and > hence the need for defining a custom nodetype I'm aware of that thread and therefore suggest to drive the spec towards version 3. Providing tools for upgrading from 2 to 3 would allow to break backwards compatibility and evolve. When using special Oak nodetypes (and moving further away from JCR) we should stop claiming to be a web framework using JCR but Oak. Regards, O. > Chetan Mehrotra > [1] http://markmail.org/thread/uj2ht4jwdrck7eja > > On Mon, Oct 3, 2016 at 1:20 PM, Oliver Lietz <apa...@oliverlietz.de> wrote: > > On Monday 03 October 2016 10:53:40 Chetan Mehrotra wrote: > >> Hi Team, > > > > Hi Chetan, > > > >> 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 > > > > rather than using implementation specific nodetypes I would like to stick > > to JCR spec and expect the Jackrabbit/Oak team (togehter with other > > implementers) to evolve the spec to version 3. > > > > See also "jcr 2.0 spec url" on users@jackrabbit – is JCR dead? > > > > Regards, > > O. > > > >> Chetan Mehrotra
