On Wed, 03 Nov 2010 03:45:21 -0200, Vjeran Marcinko
<vjeran.marci...@email.t-com.hr> wrote:
The thing that I worry about is that utility class and its static field
is used as a way for filter and pages to communicate. I thought if
filter and pages are in different classloaders, will they see different
instances of static field and thus ruin communication?
I strongly suggest you to make your utility class a Tapestry-IoC service
instead. This will guarantee that everybody uses the same class instance
even when the service class is reloaded. It's so easy to provide a class
as a Tapestry-IoC service that it's quite hard to argue otherwise.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
