On Wed, 01 Oct 2014 03:29:24 -0300, Lance Java <lance.j...@googlemail.com>
wrote:
As you've discovered, tapestry stores page properties as PerThreadValues
that are null on the non request thread. You should pass any contextual
information to your worker's constructor.
This happens since 5.2, when the page pool was abolished. Tapestry page
instances aren't meant to be passed around anyway.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
