Hi,
On Mon, May 25, 2009 at 18:47, Dan Diephouse
dan.diepho...@mulesource.com wrote:
I've made good progress on JCR-977. I now have a working implementation,
although a bit rough around the edges.
One of the use cases I wanted to support was using jcr:contains and
jcr:deref in a predicate,
On Fri, Apr 24, 2009 at 9:27 AM, Marcel Reutegger
marcel.reuteg...@gmx.netwrote:
Hi,
On Wed, Apr 22, 2009 at 21:57, Dan Diephouse
Wondering if I
have some freedom here. Otherwise it's going to end up a big ugly it
looks
like...
as an alternative we could try to add a new class, which
On Fri, Apr 24, 2009 at 9:27 AM, Marcel Reutegger
marcel.reuteg...@gmx.netwrote:
Hi,
On Wed, Apr 22, 2009 at 21:57, Dan Diephouse
Wondering if I
have some freedom here. Otherwise it's going to end up a big ugly it
looks
like...
as an alternative we could try to add a new class, which
Hi,
On Wed, Apr 22, 2009 at 21:57, Dan Diephouse
dan.diepho...@mulesource.com wrote:
Does RelationQueryNode have to be API compatible with 1.5?
it is a public class in spi-commons, which means it should be
compatible with 1.5. I don't know how many projects out there depend
on that class...
Hi,
On Mon, Apr 20, 2009 at 22:01, Dan Diephouse
dan.diepho...@mulesource.com wrote:
I'm looking into this now and have a question. In a non predicate query I
see that Jackrabbit creates a DerefQueryNode and adds it to the
PathQueryNode via addPathSetp.
However, if one is working on a
Does RelationQueryNode have to be API compatible with 1.5? Wondering if I
have some freedom here. Otherwise it's going to end up a big ugly it looks
like...
On Wed, Apr 22, 2009 at 4:23 AM, Marcel Reutegger
marcel.reuteg...@gmx.netwrote:
Hi,
On Mon, Apr 20, 2009 at 22:01, Dan Diephouse
I'm looking into this now and have a question. In a non predicate query I
see that Jackrabbit creates a DerefQueryNode and adds it to the
PathQueryNode via addPathSetp.
However, if one is working on a RelationQueryNode there is only the ability
to add Path.Elements. Am I correct in understanding
Hi,
On Thu, Apr 16, 2009 at 21:40, Dan Diephouse
dan.diepho...@mulesource.com wrote:
I was contemplating implementing support for jcr:deref in xpath predicates a
la https://issues.apache.org/jira/browse/JCR-977.
There is a message from Mercel saying that the spec doesn't explicitly
support
Yeah, it basically allows you to do joins of certain sorts when searching
for items, which is *immensely* useful. I've got this coded up as two
separate queries right now, but it's pretty slow and I can see how for some
open queries it'd cause things to grind to a halt...
Anyway, thanks for the
Frédéric Esnault wrote:
Thanks for the answer, but my question was : is there another way only using
XPath? I should have been clearer, sorry.
no, there is not. jcr:deref() can only be used to dereference a property along
the path. e.g.
foo/bar/jcr:deref(@myRef, '*')/bla
regards
marcel
Frédéric Esnault wrote:
Is it forbidden to put a jcr:deref in a predicate, knowing that we can use
child nodes and properties?
jackrabbit does not support the jcr:deref function in a predicate.
please file a jira issue if you wish to see this enhancement in jackrabbit.
regards
marcel
: vendredi 22 juin 2007 11:25
À : dev@jackrabbit.apache.org
Objet : Re: jcr:deref() in predicate
Frédéric Esnault wrote:
Is it forbidden to put a jcr:deref in a predicate, knowing that we can use
child nodes and properties?
jackrabbit does not support the jcr:deref function in a predicate.
please
Frédéric Esnault wrote:
Thansk I will because if we don't have, how can we do this query.
I want all contracts having as an internal contractor the company Lycos.
Knowing that contractors are references in the contract type.
I did /jcr:root/lgw:root/lgw:contracts/element(*,
: jcr:deref() in predicate
Frédéric Esnault wrote:
Thansk I will because if we don't have, how can we do this query.
I want all contracts having as an internal contractor the company Lycos.
Knowing that contractors are references in the contract type.
I did /jcr:root/lgw:root/lgw:contracts
14 matches
Mail list logo
