Hi, On Wed, Aug 6, 2008 at 9:39 AM, KÖLL Claus <[EMAIL PROTECTED]> wrote: > sorry for my hardheadedness > but is there nobody out who can give some statement to that problem ? > i have created a jira issues JCR-1702 for that problem
I'm not sure what the right answer here would be. Ideally a session inside a transaction should behave as close as possible to a session outside one, but in this case it doesn't. One reason for this behaviour is that until the transaction is committed the created node is only visible within the transaction, so locking it doesn't really achieve much. I'm not sure how things end up looking internally in Jackrabbit for such a case, it seems like in JCR-1702 you've already dug deeper than what I can tell from the top of my head. More generally the effect of locking within a transaction is a tricky subject, e.g. should a lock within a transaction affect clients outside the transaction? In any case the behaviour you are seeing is confusing. If such locking is not supported, then already the lock() method should throw an exception instead of the failure being manifest as an ItemNotFoundException that causes commit() to fail. BR, Jukka Zitting
