Return-Path: 
 <cocoon-dev-return-28261-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 42696 invoked by uid 500); 14 Jun 2002 12:17:03 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 42685 invoked from network); 14 Jun 2002 12:17:03 -0000
Message-ID: <3D09DD87.50708@apache.org>
Date: Fri, 14 Jun 2002 07:11:51 -0500
From: Ivelin Ivanov <ivelin@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: Actions and XMLForm
References: <3D08A5E6.2070508@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N



Andrew,

You may want to try to combine XMLForm with the flowmap.
Daniel can be your guide, because he seems to understand how to balance 
both things.

I am looking forward to an implementation of the Feedback Wizard, which
delegates the flow control to the flowmap.


Ivelin


Andrew C. Oliver wrote:
> Hi,
> 
> I've been working on XMLForm stuff and overall it's nice.  just.....
> 
> Actions....I don't really like them.  They smell.  Okay, actually I 
> think they might have their place if say
> your form handling was really really really complex, but thats not the 
> 90% case.  (yes I realize they are
> part of cocoon and not xmlform)
> 
> Is there some way of handling this in the sitemap?  Say
> 
> <actionmap name="SampleAction">
>   <form name="myform">
>        <command name="next">
>         ...do stuff (like redirecting to the mapping for a page of the 
> form or something)
>         </command>
>         <command name="cancel">
>               ....
>         </command>
>    </form>
> </actionmap>
> 
> Furthermore, most beans that I'll be creating are *STUPID*..  Meaning, 
> they're something that a C struct would
> perfectly satisfy.  In such an event is there a way to just define the 
> set of fields:
> 
> <formbean name="Customer">
>  <field name="firstname" type="string"/>
>  <field name="lastname" type="string"/>
>  <field name="irateflag" type="boolean"/>
> </formbean>
> 
> While I'm not sure this should be in say the sitemap, it seems like I 
> should be able to define my datatypes in XML
> somewhere. 
> Advantages:
> 
> 1. Shortens the change/compile/test cycle and increases developer 
> productivity
> 2. Saves typing getters and setters
> 3. Don't Repeat Yourself, if I'm going to create 100 practically 
> identical classes, then one must ask, why am I
>    creating them at all.
> 4. Smells like cocoon.  (where Actions and the beans smell like struts)
> 
> Disadvantages
> 
> 1. Might require serialization before passing to java code.
> 
> Mitigations
> 
> 1. Pass a DOM tree or something.
> 
> While I'm just betting someone already thought of this, in the event 
> they didn't I am happy to contribute, though I lack
> the in-depth knowledge of cocoon innards to provide it by my lonesome.
> 
> -Andy
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 
> 



-- 

-= Ivelin =-


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org