Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 52086 invoked by uid 500); 16 Apr 2002 17:58:22 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 52075 invoked from network); 16 Apr 2002 17:58:18 -0000 Message-ID: <00f601c1e570$bffc37c0$fb1014ac@lmatnor> From: =?iso-8859-1?Q?Mats_Nor=E9n?= To: References: <200204151705.g3FH5V626210@orion.rgv.hp.com> Subject: Re: [RT] Forms and wizards (was: RE: HEADS UP - cocoon form handling (long!!)) Date: Tue, 16 Apr 2002 20:01:28 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Ovidiu, > I think actions should work fine if you put them right before > in a pipeline. Actions don't generate any > SAX events on the pipeline, so they should not interfere with the > later invocation of the sitemap via sendPage() or > sendPageAndContinue() functions. I was more thinking about a way to dynamically plug them into the flow-scripts.. :) Since they don�t interfere with the pipelines... DatabaseActions in perticular could prove useful. I remember that there were some discussions about actions and their whereabouts but I don�t remember the conclusions (if there were any) :) /Regards Mats --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org