Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
From: "Per Kreipke" <per@onclave.com>
To: <cocoon-users@xml.apache.org>
Subject: RE: Aha! got it! 64k limit(was: new version of the sql
  logicsheetunderdevelopment)
Date: Fri, 1 Sep 2000 12:29:20 -0400
Message-ID: <NDBBIKLOLMEELKELLPFIEEPDCMAA.per@onclave.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <39AF9A48.E87FDD8E@denic.de>
Importance: Normal

Uli, et al,

This might be a naiive observation (having only just realized that I can
parse/style taglibs to make them documentable) it occurs to me that it might
be possible to convert (or at least help) Cocoon1 XSP files to Cocoon2 by
using Cocoon itself. E.g. extracting the <?cocoon-process?> processing
instructions using XSLT (and possibly converting them to sitemap
instructions?).

Per.

> > From: Stefano Mazzocchi <stefano@apache.org>
> >
> > Only XSP that used DOM directly (AND WE TOLD YOU NOT TO DO IT!) will be
> > hard to port, anything else will be piece of cake.
>
> Well, piece of cake or not, I have thousands of files, so I will need
> some time to port. Plus, the "hacks" I had to implement for processing
> chains should be put into the sitemap, this will also take some time.
> And I suspect the clean-page model will not work anymore in cocoon2, so
> everything needs to be converted over to the taglib-model. We are not
> talking about simple pages here, but about sophisticated workflows. When
> I think of some of the hacks that have been reported on this list to
> make large sites work...
>
> Ulrich
>
> --
> Ulrich Mayring
> DENIC eG, Systementwicklung
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
> For additional commands, e-mail: cocoon-users-help@xml.apache.org
>
>