Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (herse.apache.org: domain of mwaschkowski@gmail.com
 designates 64.233.166.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=NWh5SlMgPtvxZOXVoO1trl1Q8crCxVIvXvQjI03nVys/hQ7uUewnorexL9QOu6Z7Xr8GhFNhaykYSw7suIvDTk+AFaBDoRgNwyMiOlVqn201u06NA/0Pdas7VA4WFl3fJoiWFme8FIxZ26zo6mzYP4OY381emSEQnynXp0So1kg=
Message-ID: <76a6ebd00707161237r6482ca8dhbef0fbd051f57662@mail.gmail.com>
Date: Mon, 16 Jul 2007 15:37:35 -0400
From: "Mark Waschkowski" <mwaschkowski@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: JSR 283 - Public Review - Content Repository for JavaTM
 Technology API Version 2.0
In-Reply-To: <eb7e2190707160743r2179e2a2kf0abedb1ba0cbf67@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_45879_14805611.1184614655414"
References: <eb7e2190707160106l89ca860ld1fbc325d07b037f@mail.gmail.com>
	 <1184580413.3177.20.camel@tveimo-laptop>
	 <eb7e2190707160743r2179e2a2kf0abedb1ba0cbf67@mail.gmail.com>

------=_Part_45879_14805611.1184614655414
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi David,

I just glanced through the spec and looks like it has some interesting new
features. One thing I noticed (as pointed out at theserverside.com) is that
sql and xpath is deprecated and replaced with a new AQM. A natural evolution
of xpath support would have, of course, been XQuery since JCR is a
hierarchical storage mechanism, for which xpath and xquery are well suited.
There is no mention of the reasoning behind this, would you provide some
please?

I do, however, like the idea of a Java query object model since doing
criteria queries with sql is a pain (having to append where criteria
together using a string is no fun) so I'm assuming that the JQOM would be
something akin to 'example' queries (create an example object and ask system
to get data that 'looks like' the example object), right?

Best,

Mark

------=_Part_45879_14805611.1184614655414--