jcr2spi currently uses the JSR 170 way to determine whether a given Session owns the lock by checking of the lock token is null.
with JSR 283 a new Lock method has been defined for this, while on the other hand the lock token is always null for session-scoped
In addition 283-locking allows to specify a timeout hint and hint about the owner info that should be displayed
for information purpose.
Proposed changes to SPI:
- extend org.apache.jackrabbit.spi.LockInfo to cover the new functionality added with JSR 283
- add an variant of RepositoryService.lock that allows to specify timeout and owner hint.
Proposed changes to JCR2SPI:
- change jcr2spi to make use of the new functionality and modify the test for session being lock holder.
this mainly affects
> LockManager impl
> Lock impl
- is depended upon by
JCR-2097 Broke lock tests in jcr2spi after the JCR 2.0 upgrade