Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 97834 invoked by uid 500); 24 Mar 2003 19:23:13 -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 97820 invoked from network); 24 Mar 2003 19:23:13 -0000 Received: from out004pub.verizon.net (HELO out004.verizon.net) (206.46.170.142) by daedalus.apache.org with SMTP; 24 Mar 2003 19:23:13 -0000 Received: from verizon.net ([4.3.86.55]) by out004.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030324192317.HQLG10550.out004.verizon.net@verizon.net> for ; Mon, 24 Mar 2003 13:23:17 -0600 Message-ID: <3E7F5B27.10803@verizon.net> Date: Mon, 24 Mar 2003 11:23:19 -0800 From: Christopher Oliver Reply-To: coliver@apache.org User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: Scratchpad PetStore Sample and XMLForm References: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out004.verizon.net from [4.3.86.55] at Mon, 24 Mar 2003 13:23:16 -0600 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N No, XMLForm will still behave the same way. It's just a change to the implementation to make it more maintainable. leo leonid wrote: > Hi Christopher, > just read your last post "Flow views, scratchpad taglib, and writing > transformers" (hew..., your fast:) . > Does this mean you abandon your your current XMLForm-approach of the > petstore sample? > /Leo > > > On Sonntag, M�rz 23, 2003, at 12:00 Uhr, Christopher Oliver wrote: > >> I modified this sample to use XMLForm to implement the "Edit Account" >> page of this sample. To see this, first sign in and then click on "My >> Account". >> >> XMLForm is very nice to use in flow scripts, because it automatically >> populates the model (you never have to call cocoon.request.get("...")) >> and it has nice hooks for validation. >> >> However, I don't know how to integrate its view with the rest of the >> application. Could somebody take a look at this? >> >> Regards, >> >> Chris >> >> > >