Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 88259 invoked from network); 12 Nov 2004 18:55:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 12 Nov 2004 18:55:53 -0000 Received: (qmail 44799 invoked by uid 500); 12 Nov 2004 18:55:51 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 44747 invoked by uid 500); 12 Nov 2004 18:55:50 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 44734 invoked by uid 99); 12 Nov 2004 18:55:50 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Fri, 12 Nov 2004 10:55:47 -0800 Received: (qmail 22134 invoked by uid 50); 12 Nov 2004 18:55:46 -0000 Date: 12 Nov 2004 18:55:45 -0000 Message-ID: <20041112185545.22133.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 32208] New: - [PATCH] lucene block contribution : a AnalyzerManager component X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . 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