Nodes are normally in a "checked out" state, you can write as many
times as you like to a node in checked out state, and no versions will
be created. To create a new version you need to check the node in.
This will make a read only copy of the node and its subtree in the
version tree (assuming the node is versionable). Leaving the original
node read only.
To write to the node once more, you need to check it out again.
AFACT, Sling by default does not perform check in's except in the
content loader.
For a better description of how this part of JCR works have a look at
the JSR-170 spec document.
HTH
Ian
On 19 May 2009, at 17:26, Daniel, de la Cuesta Navarrete wrote:
Hi,
How works the versioning using the SlingPostServlet?
I an creating new resources using the SlingPostServlet, I have an
observator
that adds the mixins referenceable and versionable to the new
created node.
Is Sling saving all vesions of the node automatically?
Thank you.
