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 christophe.lombart@gmail.com
 designates 209.85.198.229 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=mhjovpEzCGVcf28/WGZMZxWmxwrZQQ9FIitOrjGpSgY2VTYfJ6I3Sv3pMwvAZu8Wid
         Zebo6kTEEsZ48Bgp3ujbBXvpju9DrdQoTkR6PNjOuthgjnoJeGfHOGEFxwqgzZWnFYzw
         7B3V0K3jreUS/2goLvKftye/IcTARiuOx4Ym4=
Message-ID: <3b728ee90810170032r7f6adbaatddcab9f5c555818f@mail.gmail.com>
Date: Fri, 17 Oct 2008 09:32:32 +0200
From: "Christophe Lombart" <christophe.lombart@gmail.com>
To: dev@jackrabbit.apache.org
Subject: Re: OCM:Supporting nested properties for the FilterImpl
In-Reply-To: <E599B819E62E8C4F85F610411F0E38A0734E09@PUNEXCH.bioimagene.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_46090_14223137.1224228752125"
References: <E599B819E62E8C4F85F610411F0E38A0734DE3@PUNEXCH.bioimagene.com>
	 <3b728ee90810162356j2f9aa41ocd48f8c449cfb9b0@mail.gmail.com>
	 <E599B819E62E8C4F85F610411F0E38A0734E09@PUNEXCH.bioimagene.com>

------=_Part_46090_14223137.1224228752125
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

ok.  Thanks for your help.

Christophe


On Fri, Oct 17, 2008 at 09:27, Boni Gopalan (BioImagene) <
Boni.G@bioimagene.com> wrote:

> The Mapping file gives a good handle on guessing what the equivalent
> node or property name is.  I think the current mapping file has all the
> information needed to do an OGNL like traversing of the Nodes.  Will try
> out a testcase to understand the challenges.
>
> -----Original Message-----
> From: Christophe Lombart [mailto:christophe.lombart@gmail.com]
> Sent: 17 October 2008 12:26
> To: dev@jackrabbit.apache.org
> Subject: Re: OCM:Supporting nested properties for the FilterImpl
>
> At present,  this not possible but I think it should be nice to
> implement
> it.
>
> See the issue http://issues.apache.org/jira/browse/JCR-878 (see the
> latest
> point in this issue).  We can split this issue into smaller ones .
>
> On Fri, Oct 17, 2008 at 08:01, Boni Gopalan (BioImagene) <
> Boni.G@bioimagene.com> wrote:
>
> > The Filter is a nifty interface that allows hassle free construction
> of
> > JCR query strings through a Criterion() like methods.  The default
> > implementation does a remarkably accurate job of building queries that
> > are one level deep.  It would be great if the queries can be any level
> > deep so that one can fetch back any specific 'Object' representation
> of
> > a node or a property.
> >
> >
> >
> > Eg.
> >
> >
> >
> > Foo{
> >
> > String id;
> >
> > List<Bar> myBar;
> >
> > }
> >
> >
> >
> > Bar{
> >
> >            String id;
> >
> >            String name;
> >
> > }
> >
> >
> >
> > Filter(Foo.class); [Not exactly but you get the idea!]
> >
> > Filter.addEqualsTo("myBar[].name"," C&A's Pub Pub");
> >
> >
> >
> > Ocm.getObjects(Filter) , fetches all the Foos with a nested property
> > name="C&A's Pub"
> >
> >
> >
> > Any thoughts?  Is it possible with the current API?,
> >
> >
> >
> > Thanks
> >
> > Boni
> >
> >
> >
> >
> >
> >
> >
> > Boni Gopalan
> > Manager Engineering
> > BioImagene, Pune
> >
> > +91-206-609-6579(O)
> > +91-992-369-9356(C)
> >
> >
> >
> >
>

------=_Part_46090_14223137.1224228752125--