Thank you Mzemeck, I am using Spring and I tried implementing @Async but for some reason when I fired up my wicket app it complained that it couldn't find the beans. I think it must have been because I'm declaring all of my spring managed beans (including my wicketApplication class) on my applicationContext file.
Looking at the http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/htmlsingle/spring-framework-reference.html#scheduling Task Execution and Scheduling section of the spring reference manual, I decided to use a http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/htmlsingle/spring-framework-reference.html#scheduling-task-executor-usage TaskExecutor instead of using @Async annotations and it works perfectly with my current spring settings. I am autowiring spring beans on my WicketAppliation class. And I noticed that calling WicketApplication.get() from the taskExecutor kept throwing a "WicketRuntimeException: There is no application attached to current thread taskExecutor-1" exception. I realised that I didn't need to call my db services from the taskExecutor since none of those tasks are time consuming, the sending emails is what is time consuming and that's what I limited the functionality of taskExecutor to. Thanks, once more for your help. Lucas -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Continue-navigating-while-on-submit-button-process-stuff-on-the-background-tp3473026p3480723.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
