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/10/25 16:21:55 UTC
svn commit: r588238 - in /jackrabbit/sandbox/spi: FAQ.txt LIMITATIONS.txt
README.txt TODO.txt
Author: angela
Date: Thu Oct 25 07:21:54 2007
New Revision: 588238
URL: http://svn.apache.org/viewvc?rev=588238&view=rev
Log:
update sandbox to reflect current status of the project
Removed:
jackrabbit/sandbox/spi/FAQ.txt
jackrabbit/sandbox/spi/TODO.txt
Modified:
jackrabbit/sandbox/spi/LIMITATIONS.txt
jackrabbit/sandbox/spi/README.txt
Modified: jackrabbit/sandbox/spi/LIMITATIONS.txt
URL: http://svn.apache.org/viewvc/jackrabbit/sandbox/spi/LIMITATIONS.txt?rev=588238&r1=588237&r2=588238&view=diff
==============================================================================
--- jackrabbit/sandbox/spi/LIMITATIONS.txt (original)
+++ jackrabbit/sandbox/spi/LIMITATIONS.txt Thu Oct 25 07:21:54 2007
@@ -3,31 +3,6 @@
===============================================================================
--------------------------------------------------------------------------------
- spi
---------------------------------------------------------------------------------
-
-
---------------------------------------------------------------------------------
- jcr2spi
---------------------------------------------------------------------------------
-
-- Reregistering an existing namespace to a new prefix will not be visible to
- 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.
-
-
---------------------------------------------------------------------------------
- spi2jcr
---------------------------------------------------------------------------------
-
-
-
---------------------------------------------------------------------------------
spi2dav
--------------------------------------------------------------------------------
Modified: jackrabbit/sandbox/spi/README.txt
URL: http://svn.apache.org/viewvc/jackrabbit/sandbox/spi/README.txt?rev=588238&r1=588237&r2=588238&view=diff
==============================================================================
--- jackrabbit/sandbox/spi/README.txt (original)
+++ jackrabbit/sandbox/spi/README.txt Thu Oct 25 07:21:54 2007
@@ -30,30 +30,17 @@
This contribution within the Jackrabbit project contains example
implementations for Jackrabbit SPI:
-- SPI2JCR : implements the SPI on top of JCR (e.g. Jackrabbit)
-- SPI2DAV : SPI implementation on top of WebDAV connecting to a Jackrabbit Jcr-Server.
-
-- SPI-RMI : rmi layer
-
-In addition the contrib contains
-
-- JCR2SPI : implementation of the JSR170 API covering the transient layer.
-
-
-This means that the current environment contains the following layers
-
- JCR -> SPI -> JCR
- JCR -> SPI -> WebDAV -> JCR
+- spi2dav : SPI implementation on top of WebDAV connecting to a Jackrabbit Jcr-Server.
+- spi-rmi : rmi layer
+- spi-logger : logging facility
Requirements
===============================================================================
This project assumes that you have already successfully compiled and
-installed the Jackrabbit SPI, SPI commons and JCR commons module as well
-as the Jackrabbit Jcr-Server into your maven repository. If this is not the case,
-go back to your jackrabbit directory and build it.
-NOTE: Jackrabbit is built using Maven2.
+installed the Jackrabbit project into your maven repository. If this is not
+the case, go back to your jackrabbit directory and build it.
> cd ../../
> mvn install