You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by lyifan <yi...@gmail.com> on 2012/01/17 20:02:49 UTC
Re: use WeakReference in a SelectModel
up!
please help me!
--
View this message in context: http://tapestry.1045711.n5.nabble.com/use-WeakReference-in-a-SelectModel-tp5140106p5152570.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: use WeakReference in a SelectModel
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Tue, 17 Jan 2012 17:02:49 -0200, lyifan <yi...@gmail.com> wrote:
> up!
> please help me!
You said: "the Select component keeps the MyObject instance until the web
application restarts, which is a sort of memory leaking"
Why do you think that? Due to the way Tapestry works, parameters of
components, page and mixins won't hold a reference to any parameter value,
so basically you're trying to solve a problem that doesn't exist.
By the way, subscribe to the mailing list instead of posting through
Nabble, as is has some problems (I've never seen your message before and
Nabble ends up eating anything that looks like HTML).
--
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-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org