Re: Re-executing a servlet request

2006-12-22 Thread David Kerber
Caldarale, Charles R wrote: From: David Smith [mailto:[EMAIL PROTECTED] Subject: Re: Re-executing a servlet request 2. With sessions -- the original params are stored in the session and page 1 uses them in the absence of form params -- ie when completing the process. Have to be careful

Re: Re-executing a servlet request

2006-12-22 Thread David Kerber
David Smith wrote: So you want to effectively save the parameters from the original request to page 1 and then use them when you come back to page 1. I can see two options: 1. Sessionless -- each page propogates the original params as hidden fields until you return to page 1 where it makes

Re: Re-executing a servlet request

2006-12-22 Thread David Smith
You won't be able to re-compose the request object as if it was just submitted. The quickest, dirtiest way is to just stow the form params in the session upfront and then use them from the session later. Example: c:if test=${not empty param.mySubmitBtn} c:set var=mySessProp scope=session

Re: Re-executing a servlet request

2006-12-22 Thread David Smith
Oooops. Minor point in code, but one that could trip someone up if they copy paste my code: pYour request for ${SessProp} follows:/p should read: pYour request for ${mySessProp} follows:/p --David David Smith wrote: You won't be able to re-compose the request object as if it was just

Re: Re-executing a servlet request

2006-12-22 Thread David Kerber
David Smith wrote: You won't be able to re-compose the request object as if it was just submitted. The quickest, dirtiest way is to just stow the form params in the session upfront and then use them from the session later. Are you saying that I can't build a request and execute it directly,

Re: Re-executing a servlet request

2006-12-22 Thread David Smith
Yes. I'm saying the original request won't be available. One other alternative I can think of is for the last page submit to add all the saved params to the request for page 1. Last page example form tag: form action=page1.jsp?frmParam1=valuefrmParam2=value --David David Kerber wrote: David

Re: Re-executing a servlet request

2006-12-22 Thread David Kerber
Got this going; thanks for the help! David Smith wrote: Yes. I'm saying the original request won't be available. One other alternative I can think of is for the last page submit to add all the saved params to the request for page 1. Last page example form tag: form

Re: Re-executing a servlet request

2006-12-21 Thread David Kerber
Nobody has a suggestion about this? David Kerber wrote: I have a web app that starts with a .jsp, and then goes through a series of servlets to process some data. If possible, I'd like to set it up so that after the last processing page is done, it goes back and re-executes the first

Re: Re-executing a servlet request

2006-12-21 Thread Hassan Schroeder
On 12/21/06, David Kerber [EMAIL PROTECTED] wrote: Nobody has a suggestion about this? Sure. I suggest you rephrase what you're actually trying to accomplish, because the original made utterly no sense to me :-) FWIW, -- Hassan Schroeder [EMAIL PROTECTED]

Re: Re-executing a servlet request

2006-12-21 Thread David Kerber
Ok, I'll try: My app is started with a .jsp. On it the user enters a location ID. When they click the submit button, it sends the request to a servlet (call it page 1) which brings up information from a database about that location, and gives them the option to make changes to the

Re: Re-executing a servlet request

2006-12-21 Thread David Smith
So you want to effectively save the parameters from the original request to page 1 and then use them when you come back to page 1. I can see two options: 1. Sessionless -- each page propogates the original params as hidden fields until you return to page 1 where it makes use of them. 2. With

RE: Re-executing a servlet request

2006-12-21 Thread Caldarale, Charles R
From: David Smith [mailto:[EMAIL PROTECTED] Subject: Re: Re-executing a servlet request 2. With sessions -- the original params are stored in the session and page 1 uses them in the absence of form params -- ie when completing the process. Have to be careful with storing data in sessions