Re: Restricting xpath query to document text

The class looks ok, except that you shouldn't lower-case the text retrieved from the resource, or is there a specific reason why this is done? Jackrabbit 1.2 will support the functions fn:lower-case() and fn:upper-case(), so there is no need to lower-case the text when it is indexed. The quer

Re: Restricting xpath query to document text

required to enable use of @jcr:data property with a jcr:like constraint? Any advice greatly appreciated. Thanks, Thomas -- View this message in context: http://www.nabble.com/Restricting-xpath-query-to-document-text-tf1512215.html#a7380944 Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.

Re: Restricting xpath query to document text

Hi, On 5/17/06, thomasg <[EMAIL PROTECTED]> wrote: One slight worry, have you visited www.textmining.org lately? Doesn't seem too healthy! The site has been hacked since December. :-( Would it make sense to consider alternatives? Some ideas that come to my mind: a) Contact the Jakarta POI com

Re: Restricting xpath query to document text

; }) then large sections of the text can go missing. You're right this must either be the way text mining or poi apis are used so I'll look at the forums. One slight worry, have you visited www.textmining.org lately? Doesn't seem too healthy! -- View this message in context: http://www.nabb

Re: Restricting xpath query to document text

thomasg wrote: When you said it got a bit nasty were you refering to the spooling from Reader to String (method readerToString)? yes, simply because text filters are built to provide a reader and not a string. It seems that you need to remove nasty parts of the returned string such as "\r\n

Re: Restricting xpath query to document text

am now getting results when searching with jcr:like: jcr:like(@jcr:data, '%are not intended to be%') Cheers, Thomas -- View this message in context: http://www.nabble.com/Restricting-xpath-query-to-document-text-t1512215.html#a4390389 Sent from the Jackrabbit - Dev forum at Nabble.com.

Re: Restricting xpath query to document text

thomasg wrote: node scoped fulltext index (the one you can use with jcr:contains(.,'whatever') ) and again in the field fulltext index, which allows you to use jcr:contains(@jcr:data,'whatever'). 1) Last time I checked searches such as jcr:contains(@jcr:data,'whatever') don't return expected h

Re: Restricting xpath query to document text

rty to enable jcr:like likely to be significantly less performant than your suggestion? Thanks again, Thomas -- View this message in context: http://www.nabble.com/Restricting-xpath-query-to-document-text-t1512215.html#a4355580 Sent from the Jackrabbit - Dev forum at Nabble.com.

Re: Restricting xpath query to document text

thomasg wrote: Yep I've just found the part in the jcr spec that says jcr:like only supported for string properties. Do you have any idea how easy / difficult it would be for us to change this behaviour for our application? It looks like we need to enable wildcard search in the document text. I g

Re: Restricting xpath query to document text

xt. I guess we could duplicate the doc text in a string property but would probably be better for us to modify the jcr:like behaviour. Thanks for your help, Thomas -- View this message in context: http://www.nabble.com/Restricting-xpath-query-to-document-text-t1512215.html#a4338607 Sent fro

Re: Restricting xpath query to document text

thomasg wrote: Hi Marcel, I've just been looking at a some more typical queries that our system will need to run and am finding a (related) but more serious problem using jcr:like. A query such as this works fine: String queryString = "//element(*, axxia:resource)[jcr:like(@axxia:title, '%inki

Re: Restricting xpath query to document text

ches the document text, even though you can't specify 'ONLY the document text and not other properties'. Any advice would be appreciated. Thanks, Thomas -- View this message in context: http://www.nabble.com/Restricting-xpath-query-to-document-text-t1512215.html#a4320864 Sent from the Jackrabbit - Dev forum at Nabble.com.

Re: Restricting xpath query to document text

thomasg wrote: Thanks for your reply. To clarify the situation at little. I was expecting to run a query such as: //element(*, axxia:resource)[jcr:contains(@jcr:data, 'classes')] to only search the contents of a document. This does not currently return an expected hit. that's because the node

Re: Restricting xpath query to document text

ork logically as won't return a hit if the word is in the document text and a property. I guess my only option is to use a different node structure with the content and properties seperated and run 2 queries rather than 1. Cheers, Thomas -- View this message in context: http://www.nabble

Re: Restricting xpath query to document text

thomasg wrote: How can I modify the query to return hits when the word is in the document body and not if it is just in one of the properties? with the current implementation the only way to achieve this is to prohibit the term in another clause for the excluded properties. currently the tex

Restricting xpath query to document text

... etc, all my properties I want to exclude...] Any suggestions would be cool, cheers Thomas -- View this message in context: http://www.nabble.com/Restricting-xpath-query-to-document-text-t1512215.html#a4102828 Sent from the Jackrabbit - Dev forum at Nabble.com.