cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject Re: continuation woes
Date Fri, 01 Oct 2004 10:47:53 GMT
On Thu, 2004-09-30 at 10:06, Jorg Heymans wrote:
> Adam Walsh wrote:
> > Hi Jorg,
> > 
> > That scenario makes perfect sense. In step 1, you're actually updating 
> > the model of your form by removing the element. Step 2 you're jumping 
> > back and seeing an old view of your form model that is no longer valid. 
> > In step 4 you're effectively just refreshing your view on the model, so 
> > it won't show the element that you removed previously. It's not actually 
> > being removed again, it's presenting the updated repeater widget with 
> > the element missing that you removed in step 1.
> this makes sense .
> 
> But why can't I reproduce this behaviour in the CForms samples then? Try 
> playing with the contact repeater at the bottom, it does not have this 
> "feature".
> http://localhost:8888/samples/blocks/forms/form1

that sample doesn't use flowscript, nor does it store the form model
server side between requests, iow it is stateless. On each request, it
creates a fresh form instance and fills it up with the data from the
request.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


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


Mime
View raw message