On 7/28/08, Paco Avila <[EMAIL PROTECTED]> wrote: > In my application, a document node is uploaded to the repository and > cheked-in. Then it is versions as 1.0 and any other user can edit it > performing a previous check-out. The document node also is locked to > preserve it from modifications by other users. and what is the problem right now? regards, toby
> > On Mon, Jul 28, 2008 at 9:25 PM, Tobias Bocanegra > <[EMAIL PROTECTED]>wrote: > > > > hi, > > the initial state of a versionable node is checked-out with a base > > version to the root version. the point is, that you cannot edit the > > node, unless it's checked out. so in your world, the node would be > > transiently checkedout until you save it, and the automagically become > > checked-in? i don't think so. > > > > regards, toby > > > > On 7/28/08, Paco Avila <[EMAIL PROTECTED]> wrote: > > > This is an old issue, but now I wonder why when I add a node, its > > checkedOut > > > property is set to true. Does it make sense? I think it should be in > > > checked-in state. > > > > > >
