Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
2.1.5
-
None
-
None
-
Operating System: other
Platform: Other
-
32208
-
Patch available
Description
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
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