Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of
 gcaj-jackrabbit-dev@m.gmane.org designates 80.91.229.2 as permitted sender)
To: dev@jackrabbit.apache.org
From: Christoph Kiehl <christoph@sulu3000.de>
Subject: Re: master plan for jsr 283 query implementation
Date: Mon, 10 Sep 2007 19:00:39 +0200
Lines: 44
Message-ID: <fc3t52$9hf$1@sea.gmane.org>
References: <46DFB804.4040809@gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
In-Reply-To: <46DFB804.4040809@gmx.net>
Sender: news <news@sea.gmane.org>

Marcel Reutegger wrote:

> well, those are actually just my thoughts how I think we should 
> implement the query enhancements specified in JSR 283.
> 
> there are basically three major blocks that we need to implement:
> 
> - JQOM, allows you to programmatically create a query
> - JCR-SQL2, the new SQL query syntax
> - additional query features (joins, etc.)
> 
> In a first step I already introduced temporary interfaces for the JQOM 
> and implementing classes.
> 
> I'd like to keep the current design of the query sub system for a while 
> until we are ready to switch to the new JQOM as the basis for syntax 
> independent query representation.
> 
> That is, in a first phase my suggestion is the following:
> 
> XPath---+
>         +--->AQT----+
> SQL-----+           +---->LuceneQuery
>                     |
> SQL2------->JQOM----+
> 
> 
> AQT: abstract query tree
> 
> And once the path SQL2->JQOM->LuceneQuery is stable:
> 
> XPath---+     AQT (deprecated)
>         |
> SQL-----+---->JQOM----->LuceneQuery
>         |
> SQL2----+
> 
> 
> Comments and suggestions are welcome.

+1. Sounds reasonable. Do you want to use javacc for SQL2 parsing?

Cheers,
Christoph