jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paco Avila" <monk...@gmail.com>
Subject Re: why an added node is checkedOut = true?
Date Wed, 30 Jul 2008 12:22:31 GMT
Yes, I have modified the webdav servlet to perform an automatic "checkin" .
I've implemented my own IOHandler.

But I was I was also talking about Jackrabbit checkhot behaviour. From my
point of view, a versioned node added to the repository should be in checkin
state.

On Wed, Jul 30, 2008 at 11:02 AM, Angela Schreiber <anchela@day.com> wrote:

>
>  ah, your talking about uploading a document via webdav? in this case
>> you could alter the webdav servlet to do an automatic checkin after
>> creating the nodes.
>>
>
> the proper way would be to have the DAV:auto-version
> property handled by the server.
>
> that property would then determine whether checkout/checkin
> is performed automatically and whether lock is involved
> or not... see the link to RFC 3253 and the DAV:auto-version
> property i sent in an previous mail:
> http://www.webdav.org/specs/rfc3253.html#PROPERTY_auto-version
>
> that mail also links to an existing issue:
> http://issues.apache.org/jira/browse/JCR-1348
>
> alternative: create your own handler that does the checkout/checkin
> for you. but that's not the DeltaV way of doing it... then
> you can omit the DeltaV-support from the server.
>
> angela
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message