Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Message-ID: <3D0DD791.2060803@apache.org>
Date: Mon, 17 Jun 2002 07:35:29 -0500
From: Ivelin Ivanov <ivelin@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: XMLForms and Flowmap
References: <KBEKLGJIPBEEJDBCDDJHCEICCHAA.reinhard_poetz@gmx.net>
 <3D06C666.9080102@apache.org> <3D0B62A7.5E56AB55@apache.org>
 <3D0CC618.9050809@apache.org> <3D0CCFC4.885163D4@apache.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Stefano Mazzocchi wrote:
> Ivelin Ivanov wrote:
> 
> 
>>How about binding http request parameters to objects?
>>myobject.setName( cocoon.request.getParameter( "name" ) );
>>for each parameter for each form is not pretty code.
> 
> 
> Please, just keep one thing in mind: we have the ability to extend the
> FOM (flowmap object model) with *anything* we want.
> 
> Want to perform automatic binding between your bean and the user
> request? we might simply do
> 
>  flowmap.populate(myobject,cocoon.request);

Something like that.

Although there are a few more things which are specific about input 
handling.
1) Handling checkbox widgets. They can't be automatically populated when 
no checked.
2) Branching the flow in accordance with the user selection.
3) Branching based on validation result

I've posted another email with 5 requirements a flow map demo should 
satisfy, before it can be considered for real web apps, not just cool 
personal sites with 10 visitors.

> 
> and that is it.
> 
> And I'm just scratching the surface of this concept!
> 
> Food for thought.
> 


-- 

-= Ivelin =-


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