DO NOT REPLY [Bug 32208] New: - [PATCH] lucene block contribution : a AnalyzerManager component

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32208>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32208

[PATCH] lucene block contribution : a AnalyzerManager component

           Summary: [PATCH] lucene block contribution : a AnalyzerManager
                    component
           Product: Cocoon 2
           Version: 2.1.5
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: blocks
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: nicoo_@hotmail.com


i was frusted with the LuceneIndexTransformer because i can use custom analyzer
because the constructor needed parameters.
So i developped a analyzerManager.
The goal of the analyzerManager is to

1 - register all the necessary analyzers. Two main methods: 
		public   void register(key,analyzer);
		public   analyzer get(key);
(in a hacked version of LuceneIndexTransformer, in the xml input format you can
replace analyzer="myclass" by analyzer="mykey" and access to all the analyzers
you want)

you can configure all the necessary analyzers in the cocoon.xconf

2 - allow to configure with a custom xml file a analyzer that need to be
configured to work (PerFieldAnalyzer for multilingue document or a custom
stopwordanalayzer).    => allow multiple analyzers of the same class but with
different configurations   
(see ConfigurableAnalyzer class)



with build.xml to deploy to a cocoon webapp
see analyzer_manager tag in the cocoon.xconf after the deployment

Nicolas Maisonneuve