Thanks for all the details Marcel and Angela. That helps ... so look
like oak:Resource is the way to go
On Wed, Jul 20, 2016 at 6:17 PM, Angela Schreiber wrote:
> I am pretty sure that there was good
> intention behind the change in nt-definition between JCR 1.0 and
> JCR 2.0... but maybe not fu
Hi Chetan
That would be really troublesome for multiple reasons.
First of all nt:resource doesn't allow for residual properties as
it comes with defined set of property definitions. So, any attempt
to write a jcr:uuid property to such a node will fail.
Second, for other nodes that allow for resi
Hi,
On 20/07/16 12:53, Chetan Mehrotra wrote:
What if we do not add any mixin and just have jcr:uuid property
present. The node would anyway be indexed so search would still work.
that only works to some degree. there would be no property definition
for the jcr:uuid property and should be cons
On Wed, Jul 20, 2016 at 4:04 PM, Marcel Reutegger wrote:
> Maybe we would keep the jcr:uuid property on the referenceable node and add
> the mixin?
What if we do not add any mixin and just have jcr:uuid property
present. The node would anyway be indexed so search would still work.
Not sure if API
Hi,
On 20/07/16 11:41, Chetan Mehrotra wrote:
@Marcel - I did not understood JCR-2170 properly. But any chance we
can switch to newer version of nt:resource and do not modify existing
nodes and let the new definition effect/enforced only on new node.
node types are not versioned, which means a
Hi Chetan
I would not do that even if it was possible as it will break
every single application that relies on nt:resource to extend
from mix:referenceable... these applications would need to change
their code adding the mixin manually which may lead to follow
up issues, because adding a mixin by
On Wed, Jul 20, 2016 at 2:49 PM, Bertrand Delacretaz
wrote:
> but the JCR spec (JSR 283 10 August 2009) only has
>
> [nt:resource] > mix:mimeType, mix:lastModified
> primaryitem jcr:data
> - jcr:data (BINARY) mandatory
Thats interesting. Did not knew its not mandated in JCR 2.0. However
Hi Bertrand
It used to be mix:referenceable in JSR170 (i.e. JCR 1.0) and we
kept it for backwards compatibility:
https://docs.adobe.com/content/docs/en/spec/jcr/1.0/6.7.22.9_nt_resource.ht
ml
So, adding oak:Resource sounds the right thing to do here.
Kind regards
Angela
On 20/07/16 11:19, "Ber
Hi,
OAK-4567 introduces a new oak:Resource nodetype as an alternative to
nt:resource which has mix:referenceable.
I understand the idea of making that node non-referencable for
performance reasons, but why is nt:resource referenceable in the first
place?
builtin_nodetypes.cnd [1] has this defini