Sorry for my poor explanation. I'm implementing a generic dialog box system that will use Javascript if it can to show dialog box components using DHTML layers/divs.
If Javascript is not enabled though I need to be able to accomplish exactly the same thing, so I'm essentially submitting the form the box is launched from, capturing the posted data and squeezing it into an encoded string, showing the dialog box component nested inside a generic page, and then, when the dialog is submitted, returning to the original form, in the state the user left it in. I've accomplished all of this now (I think), but the problem I was having was with returning to the form. I'm submitting the dialog page (which contains the original form data in an encoded hidden field), and then need to unpack the original form data and re-post (in the same request) to the direct service. I've accomplished this bit by faking the request cycle and giving it the unpacked form parameters before artificially rewinding the original form and then activating it's page. Bit contorted and not nice, but it's working. I was wondering whether there was a built in way (or a correct way) to re-trigger the whole request with the original forms data, as I'm not satisified with my 'hacked' way. Joe -----Original Message----- From: Mark White [mailto:[EMAIL PROTECTED] Sent: 13 September 2005 18:02 To: Tapestry users Subject: RE: Re: Internally forwarding from one request to another Try triggering a PageRedirectException. This takes a single variable which is the url you are forwarding to. If you forward to the current page with a new set of parameters you'll probably achieve what you're looking for. http://jakarta.apache.org/tapestry/tapestry/apidocs/org/apache/tapestry/ PageRedirectException.html Mark. -----Original Message----- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Kent Tong Sent: 13 September 2005 16:34 To: [email protected] Subject: Re: Internally forwarding from one request to another Joe Trewin <joe <at> canfactory.com> writes: > I've got an odd situation where I need to re-trigger the entire > request cycle from a listener, but with an artifical set of parameters. I think it will help a lot if you would specify exactly what you're trying to do. -- Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
