Jens, This sounds similar to what I proposed (although not as lengthy and detailed as what you posted). My only suggestion would be to not use HttpSession directly, instead using the ValueStack. Doing so can decouple your actions from the web in case you want to write a rich gui client in the future.
> > Here is how I have implemented an automatic reloading progress page, > during credit-card payment and other long running tasks. > > 1) action: PaymentSubmit > 2) action: PaymentProgress > 3) interface: reloadInfo > 4) view: progress.jsp > 5) cfg: xwork.xml > > PaymentSubmit receives the form data and launches a thread. > The thread runs the payment operation, but the action return "progress". > When the payment thread is done, it updates the payment object > in the HttpSession. > > PaymentProgress checks the payment object in the HttpSession. > As long as the payment is not complete, it returns "progress". > After payment completion it returns "success". > This action exports a reloadInfo object with url and interval > for the progress jsp to use. > Wayland Chan email: wchanATtrekspaceDOTcom ---------------------------------------------------------- Get your free email account from http://www.trekspace.com Your Internet Virtual Desktop! ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
