> I think you're missing the point of what people have already told you to do.
> What they have suggested will work.
Actually, I didn't miss the point. In my original message, I noted that my
beans have "request" lifetimes for all my servlets, not "session" lifetimes.
> 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.
Correct me if I'm wrong, but this sounds like a complete and utter hack. I
realize there are lots of different "methods" to do what I was asking, but I
really wanted something more defined (maybe in the JSP/Servlet specs) than
writing a separate JSP to sniff around a session waiting for some value that
may never get there due to any number of outside factors in the original
servlet.
Thanks anyway.
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
