Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 83265 invoked from network); 11 Sep 2003 17:38:14 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 11 Sep 2003 17:38:14 -0000 Received: (qmail 14255 invoked by uid 500); 11 Sep 2003 17:38:01 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 14212 invoked by uid 500); 11 Sep 2003 17:38:01 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 14195 invoked from network); 11 Sep 2003 17:38:01 -0000 Received: from unknown (HELO out003.verizon.net) (206.46.170.103) by daedalus.apache.org with SMTP; 11 Sep 2003 17:38:01 -0000 Received: from verizon.net ([4.40.114.87]) by out003.verizon.net (InterMail vM.5.01.05.33 201-253-122-126-133-20030313) with ESMTP id <20030911173804.FWRB29617.out003.verizon.net@verizon.net> for ; Thu, 11 Sep 2003 12:38:04 -0500 Message-ID: <3F60B2FA.1060300@verizon.net> Date: Thu, 11 Sep 2003 10:38:02 -0700 From: Christopher Oliver User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [Woody multi page forms] was Re: cvs commit:cocoon-2.1/src/blocks/woody/java/org/apache/cocoon/woody/flow/javascriptwoody.js References: <3F5E390C.7060206@anyware-tech.com> <3F5E9C26.1050703@verizon.net> <3F5ED8D1.1020907@anyware-tech.com> <1063280347.1379.218.camel@yum.ot> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [4.40.114.87] at Thu, 11 Sep 2003 12:38:04 -0500 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Bruno Dumon wrote: >On Wed, 2003-09-10 at 09:54, Sylvain Wallez wrote: > > >>Christopher Oliver wrote: >> >> >> >>>BTW that flowscript code was written with the intention of supporting >>>multi-page Woody forms with automated back/forward navigation as in >>>JXForms. However, when I looked into implementing this I discovered >>>that Woody forms cannot be presented in multiple pages because >>>apparently the entire form is "submitted" with each request. As a >>>result the fields that are not presented in the first page fail >>>validation because they have no values. Or am I missing something? >>> >>> >>No, you got it right : Woody always validates the whole form. >> >> > >Yep, though it is possible to make a container widget that only >delegates request processing and validation to a subset of its widgets, >ie something like: > > > > > > > > > > > > >depending on the value of some request parameter, the wd:multipage >widget would only let a certain group of widgets process the request. > >Another approach to collecting data over multiple pages would simply be >to create multiple (different) forms, which is of course already >possible today. > >What's the best solution probably depends on the use case, I didn't felt >the need yet for the first one. > > Unfortunately that makes the current integration of Woody with Flowscript close to useless. How would you propose to handle multi-page forms? Chris