Hi, > >>Is it possible to split the logic (2 classes ?) which : > >>a) handles highlighting > >>b) grabs Query terms (method getTerms and its dependencies) > > The TextHighlighter class is already a class that purely handles highlighting (independent of > query terms). > The getTerms() function is made public in QueryHighlighter as I thought it might be of > use to some people.
It is :-) > I guess I could move it into a static function on a utility class somewhere That what my question... Well : up to you. Of course, I will use your package for highlighting, but I also have some practical applications for, say, grabbing synonyms from the Query object : Imagine the TermQuery "OS" ; it would be nice for me to get the terms as they are processed by the QueyParser's analyzer, i.e. "Windows", "Unix", "MacOS"... However, the QueryParser isn't fit yet to fulfill this goal (see bug #23307). I'm just working on this point... Cheers, p.b. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
