: SlingPOSTServlet : Auto Checkin Nodes
On Dec 8, 2010, at 11:10 AM, Felix Meschberger fmesc...@gmail.com
wrote:
And: we must be very carefull to not create backwards compatibility
issues around this automatic checkin/checkout.
And that's what integration tests are for.
Clemens - take a look
Auto Checkin Nodes is activated (i.e. true). Hence I would expect that when
I modify (a property) of my mixin:versionable node, a new version is created.
Unfortunately this is not the case.
Looking at AbstractSlingPostOperation#run only CREATE, CHECKOUT or CHECKIN
trigger a potential checkin,
Hi,
Am Mittwoch, den 08.12.2010, 16:19 +0100 schrieb Clemens Wyss:
Auto Checkin Nodes is activated (i.e. true). Hence I would expect that
when I modify (a property) of my mixin:versionable node, a new version is
created. Unfortunately this is not the case.
Looking at
On 8 Dec 2010, at 16:10, Felix Meschberger wrote:
Hi,
Am Mittwoch, den 08.12.2010, 16:19 +0100 schrieb Clemens Wyss:
Auto Checkin Nodes is activated (i.e. true). Hence I would expect that
when I modify (a property) of my mixin:versionable node, a new version is
created. Unfortunately
An: dev@sling.apache.org
Betreff: Re: SlingPOSTServlet : Auto Checkin Nodes
Hi,
Am Mittwoch, den 08.12.2010, 16:19 +0100 schrieb Clemens Wyss:
Auto Checkin Nodes is activated (i.e. true). Hence I would expect that
when I modify (a property) of my mixin:versionable node, a new version
On Dec 8, 2010, at 11:10 AM, Felix Meschberger fmesc...@gmail.com wrote:
And: we must be very carefull to not create backwards compatibility
issues around this automatic checkin/checkout.
And that's what integration tests are for.
Clemens - take a look at the integration tests. They should
