On Fri, May 28, 2010 at 4:25 PM, Alex Objelean <alex.objel...@gmail.com> wrote: > > 2) Let the client code to create the Future. Though it is a good approach, I > don't like the fact that the client is responsible for implementing such > details each time it overrides the execute() method. It would be cleaner to > move this logic inside the component.. >
Are you talking about my approach here? If so, it's not a future, it's a Runnable I'm talking about. And, to run something with an executor, you have to create a Runnable anyway, so it's not hard to just let something "wrap" it to provide the functionality. Also, I guess you could use aspects for this, too. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
