I think you're missing the point of what people have already told you to do.
What they have suggested will work.
Here's the idea, I suppose your structure in general is that servlet A
forwards to A.jsp, or maybe it can forward to A,B and C.jsp, whatever.
In our example we'll suppose that is the servlet that is going to do the
time consuming process.
So here what you do is that from A you forward to A.jsp, which prints out
"loading" and has a meta refresh that reloads on servlet *B*.
A continues to process. A's job now is to process until the results come
back, and upon the completion of the results, will put bean Bar into the
session.
Servlet B's job now is to look for bean Bar in the session. If it's not
there, it just forwards back to A.jsp, which reissues the "loading" message,
and will, after some time, hit servlet B again.
When B finds bean Bar in the session (meaning that both A has completed it's
processing and that A.jsp has meta-refreshed back to B), then it forwards to
B.jsp, which contains the display logic for bean Bar.
Got it?
-tg
----- Original Message -----
From: Mike Engelhart <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, August 17, 1999 8:46 AM
Subject: Re: Long process (Rewrite)
> > In this way, you can have one JSP page that loads data into the
bean
> > and decides whether to show an error, or "please wait" screen. The
"please
> > wait" screen would refresh after so long to a new page which would be in
the
> > same session. Before the first page terminates however, it calls the
beans
> > start() method to set it running in the background.
>
> The only problem is that my JSP's don't do any loading of data. JSP's are
> strictly being used for display purposes and I'd really would like to keep
> it that way.
> >
> > I think this is possible, but I have never tried anything like
it. I
> > may have a bash sometime tonight.
>
> I think it's possible as well, but like server push, it's too much hassle
to
> do something so simple. Also, server push has the nasty problem of
keeping
> the connection alive. If there isn't an easy way to do this, then I'd
just
> rather skip it (i've been reading too much on useit.com anyway ;-))
>
> Thanks,
>
> Mike
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff JSP-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
> For JSP FAQ, http://www.esperanto.org.nz/jsp/jspfaq.html
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
For JSP FAQ, http://www.esperanto.org.nz/jsp/jspfaq.html