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 Vaynberg wrote:

> 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
> application along with the dependencies and call application.set/unset
> around the runnable.
> 
> -igor
> 
> On Thu, Jun 3, 2010 at 1:07 AM, Douglas Ferguson
> <doug...@douglasferguson.us> wrote:
>> 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 we would just @inject the DAO into the page and pass that 
>> into constructor of the runnable.
>> This worked fine until the upgrade to 1.4.7. Now when the thread calls 
>> methods on the object we get the "org.apache.wicket.WicketRuntimeException: 
>> There is no application attached to current thread pool-13-thread-16' error
>> 
>> D/
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
>> For additional commands, e-mail: users-h...@wicket.apache.org
>> 
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to