Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 83153 invoked from network); 2 Jan 2009 13:01:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jan 2009 13:01:53 -0000 Received: (qmail 38153 invoked by uid 500); 2 Jan 2009 13:01:53 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 38078 invoked by uid 500); 2 Jan 2009 13:01:52 -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 List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 38069 invoked by uid 99); 2 Jan 2009 13:01:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jan 2009 05:01:52 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.9] (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 02 Jan 2009 13:01:51 +0000 Received: (qmail 82750 invoked from network); 2 Jan 2009 13:01:28 -0000 Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; 2 Jan 2009 13:01:28 -0000 Message-ID: <495E1027.2090506@apache.org> Date: Fri, 02 Jan 2009 14:01:27 +0100 From: Carsten Ziegeler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; de; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [C3] Extract SAX from the Pipeline module References: <495E08F5.9010907@indoqa.com> In-Reply-To: <495E08F5.9010907@indoqa.com> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Steven Dolg wrote: > Hello, > > as indicated some time ago, I would like to remove all the SAX related > pipeline components from the Pipeline module and put them into their own > module. > > Now I have done this locally just to see how easy or difficult this > would be. > I found that some modules (e.g. cocoon-servlet) actually rely on those > SAX components. > This means the dependencies amongst the modules will change a little bit > and the SAX module will actually be a dependency for some other > higher-level modules. (But I find nothing wrong with that). > But this also means the patch will be rather huge and affect a lot of > the existing modules. > > I intend to finish this and provide a patch in the next 1-2 weeks. > If someone is currently working on some components or modules this might > lead to a merge-mess. > So let me know if this might be a problem for you. > > > As second step I'd like to rename some of those components to clearly > indicate that they're handling XML using SAX - as opposed to our new > components using StAX. > But I guess that can (and should) wait until the new module is there. > > > Any opinions or objections on that? Sounds great! The only comment I have atm is about the naming of the sax classes, I think for consistency we should use upper case characters (SAX) as this is the way the classes are named in the jdk (same with DOM). Carsten -- Carsten Ziegeler cziegeler@apache.org