You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Aman Arora <AA...@manh.com> on 2014/10/15 14:19:17 UTC
Versioning of [nt:file]
Hi,
I need to version the jcr:data property of nt:resource. For that, Do I need to add mixinNode (mix:versionable) to [nt:file] or [nt:resource]?
Thanks & Regards,
Aman Arora
RE: Versioning of [nt:file]
Posted by Aman Arora <AA...@manh.com>.
Thanks Angela.
You were right. On adding a mixinNode to [nt:file], all the sub-nodes are also versioned.
Regards,
Aman Arora
-----Original Message-----
From: Angela Schreiber [mailto:anchela@adobe.com]
Sent: Wednesday, October 15, 2014 8:27 PM
To: oak-dev@jackrabbit.apache.org
Subject: Re: Versioning of [nt:file]
i think it should... if i am not mistaken neither nt:file nor nt:resource specifies another OPV... but you may want to check again in order to be sure...
regards
angela
On 15/10/14 15:02, "Aman Arora" <AA...@manh.com> wrote:
>Thanks for the response,
>Actually I have a file node. To that file node, I have added two
>mixinNodes, one is mix:versionable and the other is some custom node type.
>Now I want all the properties of nt:file as well as nt:resource to be
>versioned, including jcr:data, and the properties from the custom node
>type Will it work if I add mixin node to the nt:file node?
>
>Thanks,
>Aman Arora
>
>
>-----Original Message-----
>From: Angela Schreiber [mailto:anchela@adobe.com]
>Sent: Wednesday, October 15, 2014 6:25 PM
>To: oak-dev@jackrabbit.apache.org
>Subject: Re: Versioning of [nt:file]
>
>hi aman
>
>it depends a bit on how you want your version content to look like and
>what you want to restore... the file or the content node?
>
>second you have to look at the OnParentVersion flag defined with the
>node type definition which - as you can see in JSR 283 - defines what
>happens to the child items if the parent gets versioned.
>
>if i am not totally mistaken the default is COPY.
>
>for the details i would suggest you take a look at the specification.
>
>hope that helps
>angela
>
>
>
>
>On 15/10/14 14:19, "Aman Arora" <AA...@manh.com> wrote:
>
>>Hi,
>>
>>I need to version the jcr:data property of nt:resource. For that, Do I
>>need to add mixinNode (mix:versionable) to [nt:file] or [nt:resource]?
>>
>>
>>Thanks & Regards,
>>Aman Arora
>>
>>
>
Re: Versioning of [nt:file]
Posted by Angela Schreiber <an...@adobe.com>.
i think it should... if i am not mistaken neither nt:file
nor nt:resource specifies another OPV... but you may want
to check again in order to be sure...
regards
angela
On 15/10/14 15:02, "Aman Arora" <AA...@manh.com> wrote:
>Thanks for the response,
>Actually I have a file node. To that file node, I have added two
>mixinNodes, one is mix:versionable and the other is some custom node type.
>Now I want all the properties of nt:file as well as nt:resource to be
>versioned, including jcr:data, and the properties from the custom node
>type
>Will it work if I add mixin node to the nt:file node?
>
>Thanks,
>Aman Arora
>
>
>-----Original Message-----
>From: Angela Schreiber [mailto:anchela@adobe.com]
>Sent: Wednesday, October 15, 2014 6:25 PM
>To: oak-dev@jackrabbit.apache.org
>Subject: Re: Versioning of [nt:file]
>
>hi aman
>
>it depends a bit on how you want your version content to look like and
>what you want to restore... the file or the content node?
>
>second you have to look at the OnParentVersion flag defined with the node
>type definition which - as you can see in JSR 283 - defines what happens
>to the child items if the parent gets versioned.
>
>if i am not totally mistaken the default is COPY.
>
>for the details i would suggest you take a look at the specification.
>
>hope that helps
>angela
>
>
>
>
>On 15/10/14 14:19, "Aman Arora" <AA...@manh.com> wrote:
>
>>Hi,
>>
>>I need to version the jcr:data property of nt:resource. For that, Do I
>>need to add mixinNode (mix:versionable) to [nt:file] or [nt:resource]?
>>
>>
>>Thanks & Regards,
>>Aman Arora
>>
>>
>
RE: Versioning of [nt:file]
Posted by Aman Arora <AA...@manh.com>.
Thanks for the response,
Actually I have a file node. To that file node, I have added two mixinNodes, one is mix:versionable and the other is some custom node type.
Now I want all the properties of nt:file as well as nt:resource to be versioned, including jcr:data, and the properties from the custom node type
Will it work if I add mixin node to the nt:file node?
Thanks,
Aman Arora
-----Original Message-----
From: Angela Schreiber [mailto:anchela@adobe.com]
Sent: Wednesday, October 15, 2014 6:25 PM
To: oak-dev@jackrabbit.apache.org
Subject: Re: Versioning of [nt:file]
hi aman
it depends a bit on how you want your version content to look like and what you want to restore... the file or the content node?
second you have to look at the OnParentVersion flag defined with the node type definition which - as you can see in JSR 283 - defines what happens to the child items if the parent gets versioned.
if i am not totally mistaken the default is COPY.
for the details i would suggest you take a look at the specification.
hope that helps
angela
On 15/10/14 14:19, "Aman Arora" <AA...@manh.com> wrote:
>Hi,
>
>I need to version the jcr:data property of nt:resource. For that, Do I
>need to add mixinNode (mix:versionable) to [nt:file] or [nt:resource]?
>
>
>Thanks & Regards,
>Aman Arora
>
>
Re: Versioning of [nt:file]
Posted by Angela Schreiber <an...@adobe.com>.
hi aman
it depends a bit on how you want your version content to look like and what
you want to restore... the file or the content node?
second you have to look at the OnParentVersion flag defined with the
node type definition which - as you can see in JSR 283 - defines what
happens to the child items if the parent gets versioned.
if i am not totally mistaken the default is COPY.
for the details i would suggest you take a look at the specification.
hope that helps
angela
On 15/10/14 14:19, "Aman Arora" <AA...@manh.com> wrote:
>Hi,
>
>I need to version the jcr:data property of nt:resource. For that, Do I
>need to add mixinNode (mix:versionable) to [nt:file] or [nt:resource]?
>
>
>Thanks & Regards,
>Aman Arora
>
>