You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by an...@apache.org on 2007/07/11 11:08:58 UTC
svn commit: r555217 - /jackrabbit/trunk/contrib/spi/LIMITATIONS.txt
Author: angela
Date: Wed Jul 11 02:08:57 2007
New Revision: 555217
URL: http://svn.apache.org/viewvc?view=rev&rev=555217
Log:
add limitation regarding transfer of lock tokens
Modified:
jackrabbit/trunk/contrib/spi/LIMITATIONS.txt
Modified: jackrabbit/trunk/contrib/spi/LIMITATIONS.txt
URL: http://svn.apache.org/viewvc/jackrabbit/trunk/contrib/spi/LIMITATIONS.txt?view=diff&rev=555217&r1=555216&r2=555217
==============================================================================
--- jackrabbit/trunk/contrib/spi/LIMITATIONS.txt (original)
+++ jackrabbit/trunk/contrib/spi/LIMITATIONS.txt Wed Jul 11 02:08:57 2007
@@ -3,6 +3,11 @@
===============================================================================
--------------------------------------------------------------------------------
+ spi
+--------------------------------------------------------------------------------
+
+
+--------------------------------------------------------------------------------
jcr2spi
--------------------------------------------------------------------------------
@@ -10,7 +15,10 @@
another Session that had accessed the namespace before.
We decided that we will in first step not implement any cache-invalidation.
-
+- Session.addLockToken will always succeed.
+ JSR170 defines that a token can be present with one session only.
+ However, the SPI does not allow to find out about another session holding
+ the lock nor does the SPI impl. know, which Session instance holds the token.
--------------------------------------------------------------------------------