Are you exporting the results directly as XML? Filtering down to properties is not possible with queries in JCR, because they are more tied to the JCR model than to XML views. In JCR queries, you will always get nodes as result (albeit you can access the properties directly with QueryResult.getRows(). For XML export, you will have to do any additional output filtering yourself.
Regards, Alex On Wed, Jul 16, 2008 at 1:14 AM, MARTINEZ Antonio <[EMAIL PROTECTED]> wrote: > Hello Alex, > > Thanks for the reply. > > Query //root/obj_level_1/[EMAIL PROTECTED] and not(@attr2) and > not(@attr3)] performs filtering. > In my case I do not want to filter. > Let me put an example. I have 100 obj_level_2, each one of them > containing attr1, attr2 and attr3. > I want to formulate a query to get all 100 obj_level_2, but I only want > to get property attr1 for each one of them. > Otherwise, I need to do the query //root/obj_level_1/obj_level_2 and > remove attr2 and attr3 from the result myself. > Maybe it is not possible. > > Thanks, > Antonio > > > -----Original Message----- > From: Alexander Klimetschek [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 15, 2008 3:48 PM > To: [email protected] > Subject: Re: Query for objects with reduced set of attributes > > You need predicates defined in square brackets. Simply stating the > property checks for its existence: > > //root/obj_level_1/[EMAIL PROTECTED] and not(@attr2) and not(@attr3)] > > This query would find all nodes with a property "attr1", but without a > property "attr2" and "attr3". > > Regards, > Alex > > On Wed, Jul 16, 2008 at 12:06 AM, MARTINEZ Antonio > <[EMAIL PROTECTED]> wrote: >> Hello, >> >> If I do query >> >> //root/obj_level_1/obj_level_2 >> >> I get all obj_level_2 objects, these containing all its attributes >> (say attr1, attr2, attr3, ...) >> >> Is it possible to formulate a query to get all obj_level_2 objects >> with a reduced # of attributes per object? I tried >> >> //root/obj_level_1/obj_level_2/@attr1 , trying to get all >> obj_level_2 objects with only attr1, but I get the same result as with > >> the previous string >> >> Thanks, >> Antonio >> > > > > -- > Alexander Klimetschek > [EMAIL PROTECTED] > -- Alexander Klimetschek [EMAIL PROTECTED]
