cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Sparkes <>
Subject Re: CForms, repeater and continuation
Date Tue, 19 Apr 2005 12:22:56 GMT
Thanks, I will do it that way


> Could you save the form into a session variable (i.e. use the session
>transformer in the success pipeline) at the point where the user exits
>the form, and then aggregate the old data from the session variable and
>the new data from the current context when initiating a new form?
>Otherwise you're stuck stretching a continuation across a bunch of
>non-form-related hits (as the user navigates to the new page). 
>Peter Binkley
>Digital Initiatives Technology Librarian
>Information Technology Services
>4-30 Cameron Library
>University of Alberta Libraries
>Edmonton, Alberta
>Canada T6G 2J8
>Phone: (780) 492-3743
>Fax: (780) 492-9243
>>-----Original Message-----
>>From: Peter Sparkes [] 
>>Sent: Sunday, April 17, 2005 09:35 AM
>>Subject: CForms, repeater and continuation
>>I have a Cform which is called from any one of a number of web pages. 
>>The CForm contains a repeater widget. Both the main form and 
>>the repeater use beans to hold their data. One of the 
>>repeater fields is populated with data from the initiating 
>>web page, the others being populated by the user. This all works OK.
>>What I want to do is to allow users to exit the CForm, select 
>>another web page and recall the original CForm instance, 
>>populating the repeater with a second set of repeater fields, 
>>one of them populated with data from the second initiating 
>>web page, etc. The end result is a Cform containing sets of 
>>data from a number of web pages and user inputs.  I don't 
>>know how to do this, help please.
>>I am using cocoon 2-1-7
>>To unsubscribe, e-mail:
>>For additional commands, e-mail:
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message