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 3982 invoked from network); 19 Oct 2000 14:37:54 -0000 Received: from unknown (HELO ?195.115.98.1?) (195.115.98.1) by locus.apache.org with SMTP; 19 Oct 2000 14:37:54 -0000 Received: from maileu.imediation.com by [195.115.98.1] via smtpd (for locus.apache.org [63.211.145.10]) with SMTP; 19 Oct 2000 15:37:56 UT Received: (private information removed) Message-ID: <9B3E950CB293D411ADF4009027B0A4D2178CF0@maileu.imediation.com> From: Sebastien Sahuc To: cocoon-dev@xml.apache.org Subject: RE: [Xalan2J][Avalon3.0a3] First Cut of Patches Date: Thu, 19 Oct 2000 15:38:12 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C039DA.363B2B38" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C039DA.363B2B38 Content-Type: text/plain; charset="iso-8859-1" Berin Loritsch wrote : > The SVG serializer code needs to be refined a little to > find the propper serializer. The error page needs to > be set up to find propperly as well. I've just noticed that neither the status page nor the error page are working properly with the current code, so we will end up by fixing these anyway. Remain the SVG serializer... > The sitemap, xsp, and straight conversions work > flawlessly. > > The question is, should I commit what I have now and > refine those two things shortly? Or should I fix them > before committing my changes. I would say go ahead. Could you wait though that the last patch concerning the Xalan2j integration got commited ? Sebastien > The reason I went with the Avalon 3.0a4 (unreleased) > version is the inclusion of the correct ComponentSelector > pattern that was supposed to be in the last release. It > is better to limit the number of pervasive changes like > this. > > While my change affects a large number of classes, Avalon > has reached a point in it's API stability where we are > refining features. None of the future changes in API are > going to affect what we are using here in Cocoon. > ------_=_NextPart_001_01C039DA.363B2B38 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [Xalan2J][Avalon3.0a3] First Cut of Patches

Berin Loritsch wrote :
> The SVG serializer code needs to be refined a = little to
> find the propper serializer.  The error = page needs to
> be set up to find propperly as well.

I've just noticed that neither the status page nor = the error page are working properly with the current code, so we will = end up by fixing these anyway. Remain the SVG serializer...

> The sitemap, xsp, and straight conversions = work
> flawlessly.
>
> The question is, should I commit what I have = now and
> refine those two things shortly?  Or = should I fix them
> before committing my changes.

I would say go ahead. Could you wait though that the = last patch concerning the Xalan2j integration got commited ?

Sebastien

> The reason I went with the Avalon 3.0a4 = (unreleased)
> version is the inclusion of the correct = ComponentSelector
> pattern that was supposed to be in the last = release.  It
> is better to limit the number of pervasive = changes like
> this.
>
> While my change affects a large number of = classes, Avalon
> has reached a point in it's API stability where = we are
> refining features.  None of the future = changes in API are
> going to affect what we are using here in = Cocoon.
>

------_=_NextPart_001_01C039DA.363B2B38--