On 7/25/07, Nick Allmaker <[EMAIL PROTECTED]> wrote:
All right, here's what I'm seeing:
I've set up a simple test workspace with effectively one node in it,
which fits the same parameters as below (@test = "Test"). When I set up
a similarly simple Java class to run these queries, it returned all the
results as expected. However, my main program runs through .net,
through IKVM.net, and continues to produce the results as listed below.
Both the simple Java class and the IKVM-powered C# program used the same
.jar files as references. So, I suppose does anyone have experience
trying to use jcr:like through IKVM?
I've never used IKVM, but as long as your query is intact by the time
it reaches Jackrabbit I really cannot see how IKVM would change
things.
./alex
--
.w( the_mindstorm )p.
Thank you for the help, Marcel.
--Nick Allmaker
-----Original Message-----
From: Marcel Reutegger
Sent: Wednesday, July 25, 2007 3:41 AM
To: [email protected]
Subject: Re: Issue using jcr:like with Jackrabbit 1.3
I ran a quick test on my jackrabbit svn checkout and all your queries
returned the correct result. are you able to reproduce the behaviour in
a simple test case?
you can also re-index the workspace and see if the problem persists.
regards
marcel
> I'm trying to do wildcard searches against my repository, but I'm
> getting odd results from the system.
>
> In my repository, I have one node with an attribute @test which has
the
> value 'Test', and all my searches are with XPath.
>
> //[EMAIL PROTECTED]'Test'] returns 1 result.
> //*[jcr:contains(.,'Test') returns several results (because other
things
> say 'Test' in other attributes), including my one node.
> //*[jcr:like(@test,'Test') returns 1 result.
> //*[jcr:like(@test,'Test%') returns 1 result.
> //*[jcr:like(@test,'%Test%') returns 0 results.
> //*[jcr:like(@test,'%Tes%') returns 0 results.
> //*[jcr:like(@test,'Tes%') returns 0 results.
> //*[jcr:like(@test,'%s%') returns 0 results.
> //*[jcr:like(@test,'%') returns every node in the repository.
>
> Anyone have any thoughts?
>
> Thanks,
>
> --Nick Allmaker
