Return-Path: 
 <cocoon-users-return-17922-apmail-xml-cocoon-users-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org
Received: (qmail 93465 invoked by uid 500); 9 Apr 2001 08:46:05 -0000
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-users-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-users-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-users@xml.apache.org>
Reply-To: cocoon-users@xml.apache.org
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 93012 invoked from network); 9 Apr 2001 08:45:59 -0000
Sender: ulim@denic.de
Message-ID: <3AD17686.71501400@denic.de>
Date: Mon, 09 Apr 2001 10:44:54 +0200
From: Ulrich Mayring <ulim@denic.de>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.16-22 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: cocoon-users@xml.apache.org
Subject: Re: 4 New Classes
References: <3AD08455.2751EADC@histio.org>
X-MIMETrack: Itemize by SMTP Server on notes/Denic(Release 5.0.4 |June 8,
 2000) at 09.04.2001
 10:45:02,
	Serialize by Router on notes/Denic(Release 5.0.4 |June 8, 2000) at 09.04.2001
 10:46:15,
	Serialize complete at 09.04.2001 10:46:15
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Claude Warren wrote:
> 
> I have written 2 new classes.
> 
> AggregatingProducer - used to aggregate static (or infrequently chaning)
> XML pages into a single page.  This is handy if you have documents that
> are combined with infrastructure elements to create standard pages which
> contain a mixture of static and active (current time for example)
> elements.  Conceptually it is like a "make" for xml pages.  I use this
> on a site that should be public soon to combine documents created by a
> content editor with elements to create a standard display.  The
> resulting XML document is stored on disk for quick retrieval later.
> This producer works correctly in front of the XSP classes.

Does it pick up changes to the source XML files automatically? What is
the advantage of using a producer instead of doing it all in XSP?

> HAUtilProcessor - a class that uses a plug in paradigm to provide an
> extensible processor. I have uses this to develop a system specific time
> class <hautil:time>, an include class <hautil:include> that works with
> the AggregatingProducer, a navigation class <hautil:navigation> to
> produce an active navigation panel, a backlinks class <hautil:backlinks>
> to create a series of links to directories up the document tree,
> parameter <hautil:parameter> and header <hautil:header> classes to
> retrieve parameters and headers from the servlet request.

Shouldn't this be an XSP taglib, too? Why a processor?

> HAFormProcessor - a class that processes <haform:> tags to create online
> forms.  The result of the post operation is a document that has a
> structure based on the structure and names of the <haform> elements in
> the original document.  The processor has the ability to hide data from
> the form (not on the form at all) but include those data on the document
> that results from the post operation.

Interesting, I'll look at it. However, IMHO it should also be an XSP
taglib, so XSP features can be used within it.

> I hope to have the code and documentation available on www.histio.org
> sometime soon.

Cool, tell us when the docs and samples are ready.

Ulrich

-- 
Ulrich Mayring
DENIC eG, Systementwicklung

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <cocoon-users-unsubscribe@xml.apache.org>
For additional commands, e-mail: <cocoon-users-help@xml.apache.org>