Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Message-ID: <20001219141910.21802.qmail@web6202.mail.yahoo.com>
Date: Tue, 19 Dec 2000 06:19:10 -0800 (PST)
From: Giacomo Pati <pati_giacomo@yahoo.com>
Reply-To: giacomo@apache.org
Subject: RE: XSPGenerator
To: cocoon-dev@xml.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- Torsten Curdt <tcurdt@dff.st> wrote:
> > > > >Hm.. ok then I just want make sure that we _really_ want to
> maintain
> > > > >3(?) include systems
> > > > >
> > > > > - <util:include-...>
> > > > > - <xinclude:...>
> > > > > - sitemap aggregation
> > > > >
> > > > >If you all think this is necessary (and convince me about that
> ;)
> > > > >I'm volunteer number one for porting the <util:> taglib
> > > >
> > > > Yes, the different systems allow you to work in different ways.
> > > >
> > > > XSP include mechanisms allow programatic control of included
> content.
> > > 
> > > Ok. I want to work on this one. If you guys say this should be
> done
> > > with <util:include-..>  I will try to port the util taglib and
> add
> > > some functionallity for including XSP pages. But I guess this
> will
> > > need some modifications on the XSP logicsheet as well (as I
> proposed)
> > > a modification on the XSPGenerator class (this is where the
> thread
> > > started ;) ... It will not break anything at all!! It will just
> > > be easier to get the plain SAX events without the start/stop
> document
> > > events!
> > > 
> > > I wanna get this on :)
> > 
> > Cool :)
> 
> So what about the XSPGenerator class modification? ;) Will this be
> ok?

Go for it. Send us a 'cvs diff -u' and maybe some doc (either in the
logicsheet itself or a an xml doc.

Giacomo

=====


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/