Re: Holding on to request data

[Ted Husted <hu...@apache.org>]

There's not an easy way, since we're confined to what HTTP/HTML can do. 

The only way to pass information from a web page is through a GET or
POST request, which means you have to write it out in the page, either
in an URI or as an element in a form.

The Java Servlet framework provides the session context to keep
information on the server instead, and cookies can be used to keep the
same sort of informatoin in the client's browser. But that's the end of
the road.

-- Ted Husted, Husted dot Com, Fairport NY US
-- Developing Java Web Applications with Struts
-- Tel: +1 585 737-3463
-- Web: http://husted.com/about/services


"Bryan P. Glennon" wrote:
> 
> Hi -
> 
> I need to keep a request around during a page display. What I am doing
> goes like this:
> 
>         - User clicks on a button
>         - Request gets passed to various struts Action classes where
> various things happen
>         - Request then gets passed to a jsp page. This jsp page is a
> frameset containing two frames. The
> second frame needs to refresh itself (I do this with a meta tag). This
> is basically an "action in progress"
> stage, where a status message is displayed in the lower frame. Once the
> action is done, the message
> gets replaced with actual data, and the auto refreshes stop.
> 
> Problem is, once control goes back to the browser to display the jsp,
> the request is lost. Unfortunately,
> it contains data that needs to be passed  back for the refresh action.
> Right now I am pulling out the
> individual parameters and attributes and building the URL for the
> refresh with them. This is ugly,
> since every time info is added to the request, it has to be manually
> added to the refresh URL. Is
> there an easy way to have the jsp page just pass the original request on
> to the refresh URL?
> 
> I don't want to put the request info in session scope, since it is not
> really session information.
> 
> One limitation - I can't use JavaScript here. One of the project
> requirements is no client-side code.
> 
> Thanks,
> Bryan
> 
> --
> Bryan Glennon (mailto:bryan@bpgc.com)
> BPG Consulting, Inc. (http://www.bpgc.com)
> Tech Question? (mailto:techQuestion@bpgc.com)
> 
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>