jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <jukka.zitt...@gmail.com>
Subject Re: JCR 2.0 implementation progress
Date Thu, 06 Aug 2009 11:31:35 GMT

On Thu, Aug 6, 2009 at 8:52 AM, Angela Schreiber<anchela@day.com> wrote:
>> Could we resolve the issue as fixed for the RI and open a new issue
>> for any further changes we need before the Jackrabbit 2.0 release?
> sure, i can do that. i simply don't want to have the final 2.0
> release to be pushed out before that.

OK, good. AFAIK there is no big rush towards the final 2.0 release
yet, but we should start wrapping up the RI and TCK so that JSR 283
can become final.

>>>>  [JCR-1590] JSR 283: Locking
>>> the timeout stuff is still not implemented (as stated in the issue).
>> Are you working on it, or should I take a look at it?
> unfortunately not... but i placed TODOs in the core code.
> what needs to be adjusted is
> - respect the timeout flag upon lock creation.
> - reset the expiration upon Lock.refresh based on the original hint
> - adjust isLocked (or similar) to make sure an expired
>  lock is properly detected.

Thanks, I'll look into it.


Jukka Zitting

View raw message