Re: Regression: @Inject'ed objects cannot be passed to Threads

2010-06-04 Thread Douglas Ferguson
That makes sense. I was just surprised to see it stop working. It is something people should be aware of when upgrading. Any idea of what changed from 1.4.5 - 1.4.7 that was have exacerbated this? Also, what every happened to wrap idea that was proposed? D/ On Jun 3, 2010, at 10:22 AM, Igor

Re: Regression: @Inject'ed objects cannot be passed to Threads

2010-06-04 Thread Douglas Ferguson
Also, I'm starting to dig into these and fix them and most of them make sense to me. They are obviously asynchronous threads that we start. But this one has be a bit baffled. Does anybody recognize the classes in the stack? 2010-06-04 00:06:34,623 ERROR [main] session.ManagerBase - Exception

Regression: @Inject'ed objects cannot be passed to Threads

2010-06-03 Thread Douglas Ferguson
I've posted a similar message the other week, because I was having strange behavior when passing objects that have been injected into my page to child threads. So, we recently upgrade from 1.4.5 - 1.4.7 Prior to the upgrade we had some runnables that would do some asynchronous work for us and

Re: Regression: @Inject'ed objects cannot be passed to Threads

2010-06-03 Thread Igor Vaynberg
this is not a regression in the sense that it is a bug. we have always maintained that the objects that get injected should only be used within wicket components. you need to make sure the Application object is bound to the thread that is executing the runnable, so you will have to pass the