You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Torsten Curdt <tc...@apache.org> on 2005/01/12 22:29:01 UTC
searching
Looking into the searching part of the API
I came accross a level 1 and 2 repository.
Is there any more documentation what there
is the difference? ...versioning?
cheers
--
Torsten
Re: searching
Posted by Peeter Piegaze <pe...@gmail.com>.
The compliance levels have been reworked since verion 0.12 of the spec
document (the one available publically on the JCP's JSR-170 site).
The "Proposed Final Draft" of the spec is still winding its way
through the JCP but it should be published soon. In this latest
version the compliance level breakdown is as follows:
The JCR specification is divided into two compliance levels with a set
of additional optional features which repositories of either level may
support. Level 1 provides for read functions and level 2 adds
additional write functions. The functional division is as follows:
Level 1 includes:
-Retrieval and traversal of nodes and properties
-Reading the values of properties
-Transient namespace remapping
-Export to XML/SAX
-Query facility with XPath syntax
-Discovery of available node types
Level 2 adds:
-Adding and removing nodes and properties
-Writing the values of properties
-Persistent namespace changes
-Import from XML/SAX
-Assigning node types to nodes
-Discovery of access control permissions
Optional:
Any combination of the following features may be added to an
implementation of either level.
-Transactions
-Versioning
-Observation (Events)
-Access Control
-Locking
-SQL syntax for query
The javadoc on the jackrabbit site reflects the upcoming proposed
final draft of the spec.
On Thu, 13 Jan 2005 10:12:34 +0100, Marcel Reutegger
<ma...@gmx.net> wrote:
> Hi Torsten,
>
> > Looking into the searching part of the API
> > I came accross a level 1 and 2 repository.
>
> Level 1 primarily defines read operations on a repository. In addition a
> level 1 repository must support XPath queries.
>
> The specification also defines a SQL query syntax which is optional and
> not tied to any compliancy level.
>
> -marcel
>
Re: searching
Posted by Marcel Reutegger <ma...@gmx.net>.
Hi Torsten,
> Looking into the searching part of the API
> I came accross a level 1 and 2 repository.
Level 1 primarily defines read operations on a repository. In addition a
level 1 repository must support XPath queries.
The specification also defines a SQL query syntax which is optional and
not tied to any compliancy level.
-marcel