You could create a new Dispatcher that takes a namespace and Action name and will kick off a separate thread to execute them... You could use the Session to save status information for asynch Action execution.
> -----Original Message----- > From: Aaron Held [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 03, 2004 12:08 PM > To: [EMAIL PROTECTED] > Subject: Re: [OS-webwork] Long running tasks > > > Jason Carreira wrote: > > >Nope, no support out of the box... If you wanted, it would be easy > >enough to create an asynch ActionProxy using threads or JMS, > and/or to > >create a JMSDispatcher to consume JMS messages and translate them to > >Action executions... > > > >Jason > > > > > > > Thanks, > Threads will do. I'll look into ActionProxy, but it seems easier to > understand if I have three > seperate pages. > startLongAction Page -> Refresh And Wait Page -> Show user > results Page. > > -Aaron > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438> &op=click > > _______________________________________________ > > Opensymphony-webwork mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork > ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id56&alloc_id438&op=click _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
