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/03/01 11:59:49 UTC
svn commit: r513273 - in /jackrabbit/trunk/contrib/spi: FAQ.txt README.txt
TODO.txt
Author: angela
Date: Thu Mar 1 02:59:48 2007
New Revision: 513273
URL: http://svn.apache.org/viewvc?view=rev&rev=513273
Log:
adjust todos, readme, faq
Modified:
jackrabbit/trunk/contrib/spi/FAQ.txt
jackrabbit/trunk/contrib/spi/README.txt
jackrabbit/trunk/contrib/spi/TODO.txt
Modified: jackrabbit/trunk/contrib/spi/FAQ.txt
URL: http://svn.apache.org/viewvc/jackrabbit/trunk/contrib/spi/FAQ.txt?view=diff&rev=513273&r1=513272&r2=513273
==============================================================================
--- jackrabbit/trunk/contrib/spi/FAQ.txt (original)
+++ jackrabbit/trunk/contrib/spi/FAQ.txt Thu Mar 1 02:59:48 2007
@@ -44,6 +44,8 @@
JSR 170. Introducing an SPI is a recent approach that hopefully allows to
provide a JCR client covering the transient layer only. See also the
README.txt for some rationals regarding defining a SPI.
+ For discussions regarding merging the SPI efforts and jackrabbit-core
+ see the devs@jackrabbit.apache.org mailing list.
Q: why does the SPI subproject have a dependency to jackrabbit commons?
@@ -59,30 +61,19 @@
and added the implementation to our own 'commons' project.
While preparing the existing efforts for a checkin into jackrabbit, we
decided, that there should be only one commons project within Jackrabbit.
- therefore we removed the interfaces again from the SPI project, since it would
+ therefore removed the interfaces again from the SPI project, since it would
not be possible to have jackrabbit code depend on a contribution.
-> we will probably address this issue again.
-Q: jcr2spi looks like jackrabbit/core code. why are all the classes copied?
-A: originally we planned to use jackrabbit/core for the jcr2spi implementation.
- however, we realized that its not feasible to plug different implementations
- of the crucial interfaces in the core. Therefore we decided to copy over
- the code and modify it according to the needs of the SPI.
-
-
Some questions arising from issues still being discussed:
Q: Why does the RepositoryService does not provide methods batch reads?
Q: Is there need for special handling of very large values in SPI?
Q: Should the SPI define a XASessionInfo or should the transaction handling
be left out from the interfaces?
-Q: Should credentials, workspaceName and all kind of tokens be passed to every
- RepositoryService call instead of having a SessionInfo?
- (currently we don't thinks so. we had that in the beginning).
Q: RepositoryService.executeQuery(): should it take an offset?
-Q: QueryInfo: should it take a flag rating the results?
-Q: QueryInfo: should it rather return NodeInfos instead of Ids?
+Q: QueryInfo: should it take a flag rating the results?
Modified: jackrabbit/trunk/contrib/spi/README.txt
URL: http://svn.apache.org/viewvc/jackrabbit/trunk/contrib/spi/README.txt?view=diff&rev=513273&r1=513272&r2=513273
==============================================================================
--- jackrabbit/trunk/contrib/spi/README.txt (original)
+++ jackrabbit/trunk/contrib/spi/README.txt Thu Mar 1 02:59:48 2007
@@ -43,7 +43,7 @@
by another SPI implementation, avoiding the extra costs caused by
having JCR (including transient space and Session management) again:
- JCR -> SPI -> WebDAV -> SPI (WebDAV only being an example).
+ JCR -> SPI -> SPI-Implementation
@@ -85,13 +85,14 @@
This project assumes that you have already successfully compiled and
installed the Jackrabbit commons module as well as the Jackrabbit
-Jcr-Server into your maven repository. If this is not the case:
+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.
-> cd ../../jackrabbit/modules/commons
-> maven jar:install
+> cd ../../
+> mvn install
-> cd ../../../jcr-server
-> maven
+-> installs all required jar files.
> cd ../contrib/spi
> maven
Modified: jackrabbit/trunk/contrib/spi/TODO.txt
URL: http://svn.apache.org/viewvc/jackrabbit/trunk/contrib/spi/TODO.txt?view=diff&rev=513273&r1=513272&r2=513273
==============================================================================
--- jackrabbit/trunk/contrib/spi/TODO.txt (original)
+++ jackrabbit/trunk/contrib/spi/TODO.txt Thu Mar 1 02:59:48 2007
@@ -63,24 +63,12 @@
call may not identify the new Node in case of same-name-siblings.
-7) Merge >> done
-
-
8) Transactions (work in progress)
Definition of XASessionInfo must be reviewed.
-9) Extract interface for ItemState and derived classes
-
-
10) AccessManager.canRead() seems useless, since the jcr2spi client is only
- able to access Items it can read anyway. Remove method and calls to it?
-
-
-11) Nodetypes, Namespaces (improve)
-
- Should the SPI define means for observation of nodetype/namespace
- changes?
+ able to access Items it can read anyway. Remove method and calls to it