Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4324F917.1070002@apache.org>
Date: Mon, 12 Sep 2005 04:42:15 +0100
From: Ross Gardler <rgardler@apache.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Reloading a form after a time period
References: <4324B6F8.8010507@gardler.org>
 <4e890ccf96c28bb7554bc319da72d40c@wrinkledog.com>
 <4324C103.9000108@lojjic.net>
 <630d78b0bdacb2f9f33b323c8d225d17@wrinkledog.com>
 <4324D6AE.7080403@lojjic.net>
In-Reply-To: <4324D6AE.7080403@lojjic.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable

Jason Johnston wrote:
> Mark Lundquist wrote:
>=20
>>
>> On Sep 11, 2005, at 4:42 PM, Jason Johnston wrote:
>>
>>> You'll proabably also need to build the URL of the refresh to include=
=20
>>> the continuation id, and the name of the refresh button as a request =

>>> parameter.
>>
>>
>>
>> Not if it's the resource you're already serving :-)
>> =97ml=97
>=20
>=20
> Right, of course.  But from Ross's description of his flow it sounded=20
> like the form.showForm() loop was being exited during each refresh,=20
> which would mean that if form.showForm() was called again it would use =
a=20
> different continuation.  But without knowing for sure how the flow is=20
> structured it's a guess either way.  Just trying to give as much=20
> information as possible.

It's a multi-page form so a straight refresh won't do the trick (should=20
have said I'd tried that and it refreshes back to the first form in the=20
page).

However, adding the continuation to the refresh request did the trick,=20
thanks.

Ross


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