On Tue, 02 Nov 2010 16:10:52 -0200, Vjeran Marcinko
<vjeran.marci...@email.t-com.hr> wrote:
Mentioned utility static method stores some value in one static field
(ThreadLocal static field), and this field is later accessed from pages.
I don't know if classloader for services is the same that loads pages,
so is there gonna be two different Utility class instances around making
communication via this field impossible? (maybe Im asking something
stupid, but I never worked much with classloaders so...)
I don't know much about classloaders, but I'm 100% sure that in Tapestry
putting anything that isn't a page (including utility classes) inside the
pages packages is a very bad idea due to class transformations and the
classloading issues that come with them. The same can be said about mixins
and components.
--
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
