Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 10805 invoked from network); 2 Jun 2000 15:37:57 -0000 Received: from pop.systemy.it (194.20.140.28) by locus.apache.org with SMTP; 2 Jun 2000 15:37:57 -0000 Received: from apache.org (pv9-pri.systemy.it [194.21.255.9]) by pop.systemy.it (8.8.8/8.8.3) with ESMTP id RAA28848 for ; Fri, 2 Jun 2000 17:37:45 +0200 Message-ID: <3937C5E0.BDE5E870@apache.org> Date: Fri, 02 Jun 2000 16:34:08 +0200 From: Stefano Mazzocchi Organization: Apache Software Foundation X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I) X-Accept-Language: en,it MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Cocoon2, War files, Xerces and beyond References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Scott Boag/CAM/Lotus wrote: > > > No, seriously, you are right, we should move to final SAX 2.0 ASAP but > > if Xalan doesn't support that we might miss one leg and walking could be > > difficult. > > For Cocoon 2, I'm hoping to have a Xalan 2.0.0d1 alpha posted in the next > couple of weeks. It uses the current incarnation of the TRaX APIs (there's > a stalled issue about whether the interfaces should be broken into DOM & > SAX layers), and fully supports and takes advantage of the SAX2 APIs. Wow, that's _awesome_ news! Hail to the Xalan team! This is were separation of concerns really shine doesn't it :) > The current 1.1.0d1 code in the CVS looks pretty stable with the current > code in Xerces. We will make a release as soon as Xerces does. Ok, Mike, call for you :) -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- Missed us in Orlando? Make it up with ApacheCON Europe in London! ------------------------- http://ApacheCon.Com ---------------------