----- Original Message -----
From: "Thiago H. de Paula Figueiredo" <thiag...@gmail.com>
To: "Tapestry users" <users@tapestry.apache.org>
Sent: Tuesday, November 02, 2010 8:28 PM
Subject: Re: [Tapestry Central] Tapestry 5.2.2
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.
That's right, but it isn't the case here. My utility class is contained in
the same package where my filter is. 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? As I said, maybe I'm talking nonsense here cause classloaders
aren't my area of knowledge..
-Vjeran
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
