Starting this short-lived thread within the context of the request
thread is the only place where using the ITL works correctly. All the
other usecases (which are both more probable and more advisable) don't
work reliably or at all.
On Thu, May 20, 2010 at 4:17 PM, Alex Objelean <alex.objel...@gmail.com> wrote:
>
> I do not agree...
> Maybe you didn't understand completely the use-case:
>
> public class MyPage extends Page {
> �...@springbean
> private MyService service;
> //perform a polling of long running process triggered by a button click
> onClickButton() {
> new Thread() {
> run() {
> service.executeLongRunningProcess();
> }
> }.start();
> }
> }
>
> The following example won't work well if the Application is not stored in
> InheritableThreadLocal. The reason why it doesn't work, as I understand
> that, is because @SpringBean lookup depends on Application instance which is
> not accessible from within the thread. Having it stored inside of ITL would
> solve the problem.
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/vote-Release-Wicket-1-4-9-tp2222388p2225232.html
> Sent from the Wicket - Dev mailing list archive at Nabble.com.
>
