RE: [PATCH] LuceneSearchService - configurable analyzer, specified by class-name

[Enrique Lara <en...@hotmail.com>]

Oops, I hit send before typing a msg body:

I wanted the ability to switch out which analyzer was being used in the 
Search  - I noticed that the LuceneSearchService was hard-coded to use the 
SimpleAnalyzer.
So, I changed that to be configurable via a property file, a la:

services.Search.analyzer=org.apache.lucene.analysis.standard.StandardAnalyzer
- or -
services.Search.analyzer=org.apache.lucene.analysis.SimpleAnalyzer
- or -
services.Search.analyzer=org.apache.lucene.analysis.ru.RussianAnalyzer

etc.

There may be other ways to go about this, but the submitted patch is the way 
that came to mind.

I ran the default maven goal and the related unit test looks to have 
returned successfully (org.apache.jetspeed.services.search.TestSearch).


HTH,
Enrique

_________________________________________________________________
¿Cuánto vale tu auto? Tips para mantener tu carro. ¡De todo en MSN Latino 
Autos! http://latino.msn.com/autos/


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org