Dear Support,
it seems I\'ve found an other strange behavior in OpenKM.
I created a multiple property called okp:test.abc=4,A,B,C,D,E,F,G. I attached A, B and C to a documents.
After that in the serch tab I was searching for A, but the document was not found. But this wasn\'t the case with B and C.
I\'ve made some code review, and found, that searching works in background with XPath queries.
So my queries look like the followings:
If I remove the contains keyword, I get my result for A too:
Can it be a Jackrabbit BUG? [file name=groups-89c17b1c702821306be3b45ecf64e78a.zip size=1047]http://www.openkm.com/images/fbfiles/fi ... 64e78a.zip[/file]
it seems I\'ve found an other strange behavior in OpenKM.
I created a multiple property called okp:test.abc=4,A,B,C,D,E,F,G. I attached A, B and C to a documents.
After that in the serch tab I was searching for A, but the document was not found. But this wasn\'t the case with B and C.
I\'ve made some code review, and found, that searching works in background with XPath queries.
So my queries look like the followings:
Code: Select all
The first one doesn\'t deliver any result./jcr:root/okm:root//element(*, okg:test)[jcr:contains(@okp:test.abc, \'A\')]
/jcr:root/okm:root//element(*, okg:test)[jcr:contains(@okp:test.abc, \'B\')]
/jcr:root/okm:root//element(*, okg:test)[jcr:contains(@okp:test.abc, \'C\')]
If I remove the contains keyword, I get my result for A too:
Code: Select all
I\'ve tried it with a clean downloaded instance./jcr:root/okm:root//element(*, okg:test)[@okp:test.abc=\'A\']
Can it be a Jackrabbit BUG? [file name=groups-89c17b1c702821306be3b45ecf64e78a.zip size=1047]http://www.openkm.com/images/fbfiles/fi ... 64e78a.zip[/file]