You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Boni Gopalan (BioImagene)" <Bo...@bioimagene.com> on 2008/10/17 08:01:29 UTC
OCM:Supporting nested properties for the FilterImpl
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)
Re: OCM:Supporting nested properties for the FilterImpl
Posted by Christophe Lombart <ch...@gmail.com>.
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)
> >
> >
> >
> >
>
RE: OCM:Supporting nested properties for the FilterImpl
Posted by "Boni Gopalan (BioImagene)" <Bo...@bioimagene.com>.
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)
>
>
>
>
Re: OCM:Supporting nested properties for the FilterImpl
Posted by Christophe Lombart <ch...@gmail.com>.
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)
>
>
>
>