versioning != locking if you need concurrect versioning, use seperate workspaces per user or locking.
regards, toby On 8/26/06, JavaJ <[EMAIL PROTECTED]> wrote:
So according to the javadoc, when you check out a node using Node.checkout(), the isCheckedOut property of that node changes to "true" and all of its non-versionable child nodes become writeable. These changes are persisted immediately. I assume this means that the changes are propagated across all sessions. So: - UserA retrieves NodeA and immediately checks it out, starts modifying it... - Before UserA checks in NodeA, UserB retrieves NodeA - Can UserB start changing NodeA even though he didn't check it out himself? If so, can he save or check in the changes? What happens if he saves the changes before UserA checks in his changes? -- View this message in context: http://www.nabble.com/Checking-out-a-node-tf2167382.html#a5992432 Sent from the Jackrabbit - Users forum at Nabble.com.
-- -----------------------------------------< [EMAIL PROTECTED] >--- Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel T +41 61 226 98 98, F +41 61 226 98 97 -----------------------------------------------< http://www.day.com >---
