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.176 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=fjXvc5Zs5hcUGKXthgMRAucRzlDQwvRR249nfgZT6QyWvXM4tuBBAQJ+aEia5ocjcada9E0FRaIsHx1EKt4ykd6TT5Rkok3adVFM/O1aZe+s1YYakvth9fYzUHM4RqLKVW7nzi3GnZ56FDAeRapgLRb5bnqXKrSmRoS4iLI/A1c=
Message-ID: <76a6ebd00706271414k28665f17ia5ea83b10039eed8@mail.gmail.com>
Date: Wed, 27 Jun 2007 17:14:36 -0400
From: "Mark Waschkowski" <mwaschkowski@gmail.com>
To: users@jackrabbit.apache.org
Subject: Re: difference between xpath searches
In-Reply-To: <ae03024e0706270749v50311aa6p3bdee969365a235f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_29988_23165024.1182978876074"
References: <76a6ebd00706261121i90b040fiec371af4294b1112@mail.gmail.com>
	 <ae03024e0706262230t7688be0cm34f1b30219598200@mail.gmail.com>
	 <76a6ebd00706270540o2ceccd81p901f2a2972a605e9@mail.gmail.com>
	 <ae03024e0706270749v50311aa6p3bdee969365a235f@mail.gmail.com>

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

Hi,

Thanks Jukka and Felix for the clarifications. I understand now that the
call to getNode cannot be a query. Please allow me to restate:

Node retrieval is not handled consistently when retrieving nodes using an
xpath that refers to a particular location within the repository.

For example do the following:
0) define xpath == '/documents/contacts'
1) create a session
2) add a node in documents/contacts
3) retrieve your nodes by using 3a or 3b
3a)
  session.getRootNode().getNode(xpath).getNodes()
3b)
    Workspace ws = session.getWorkspace();
    QueryManager qm = ws.getQueryManager();
    Query q = qm.createQuery(xpath, Query.XPATH);
    NodeIterator iter = q.execute().getNodes();

You will, as mandated by the spec, get different results! I believe that the
nodes returned should be consistent regardless of Node retrieval access,
either both with the added node, or both without.

Best,

Mark

On 6/27/07, Felix Meschberger <Felix.Meschberger@day.com> wrote:
>
> Hi Mark,
>
> On 6/27/07, Mark Waschkowski <mwaschkowski@gmail.com> wrote:
> >
> > Hi Felix,
> >
> > Thanks for the response. Please allow me to clarify the first point, I'm
> > actually referring to exactly what is stated, the getNode(xPath) method.
> I
> > see an xpath statement as a type of search because any given xpath may
> be
> > a
> > simple path, but often includes some kind of criteria for the result
> set.
>
>
> Thanks for the clarification. Now, there is another misconception,
> unfortunately. The path argument to the Node.getNode(String) method is not
> an XPath querry but a relative path with no pattern characters allowed.
> This
> is for direct addressing of a single child (or descendent) node. This
> method
> just walks down the node hierarchy without applyiing any pattern matching.
>
> Regards
> Felix
>


-- 
Best,

Mark Waschkowski

------=_Part_29988_23165024.1182978876074--