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:
--David
David Kerber wrote:
Thanks, David - that should give me enough to get me going on this.
I'll post back if I run into any other issues.
Dave
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
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:
--David
David Kerber wrote:
> David Smith wrote:
>
>> You won't be able to re-compose t
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,
Oooops. Minor point in code, but one that could trip someone up if they
copy paste my code:
Your request for ${SessProp} follows:
should read:
Your request for ${mySessProp} follows:
--David
David Smith wrote:
>You won't be able to re-compose the request object as if it was just
>submitted.
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:
Your request for ${SessProp} follows:
.
--David
David Kerber wrot
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
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
> 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 wi
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
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 informati
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]
--
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 servle
13 matches
Mail list logo
