I've done similarly to how Kristian described with one small addition - i had the background thread check a cancel flag every once in a while so that it's possible to cancel it manually from the UI.
On Fri, May 7, 2010 at 11:25, Massimo Lusetti <mluse...@gmail.com> wrote: > On Fri, May 7, 2010 at 3:58 AM, Alex Kotchnev <akoch...@gmail.com> wrote: > >> We've used Spring Batch quite a bit to handle situations like this. Lots of >> good infrastructure that we didn't have to reinvent > > I really don't want to put more deps on the app that are not actually needed. > > My question was more about how to orchestrate the batch processing > with the interactive GUI then how to do batch processing itself. > > Cheers > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- Andreas Andreou - andy...@apache.org - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
