Re: Restricting xpath query to document text

2006-11-21 Thread Marcel Reutegger
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

Re: Restricting xpath query to document text

2006-05-17 Thread thomasg
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.nabble.com/Restricting-xpath-query

Re: Restricting xpath query to document text

2006-05-12 Thread thomasg
? 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

2006-04-27 Thread Marcel Reutegger
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

Re: Restricting xpath query to document text

2006-04-27 Thread thomasg
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.com/Restricting-xpath-query-to-document