Hi guys, I hope you're doing great.
I'm pretty new to Tapestry and I'm having some trouble with forms.
It turns out that when some field of a form (e.g. a textfield) references
some property that's accessed by a dot notation (I mean, it's not a simple
page property but a property that belongs
Hi, folks. I'm just learning Tapestry too but I want to participate in
the list. :-)
Juan, I don't know much about Tapestry (yet!) but if I'm not mistaken
that declaration of your service isn't adequate. You should use a method to
handle the activate event and there initialize your
On Thu, 25 Mar 2010 09:27:21 -0300, Matheus Eduardo Machado Moreira
matheus@gmail.com wrote:
Hi, folks. I'm just learning Tapestry too but I want to participate in
the list. :-)
Welcome to this list, Matheus!
Juan, I don't know much about Tapestry (yet!) but if I'm not mistaken
Thanks, Thiago. I'm glad to have helped Juan and that my answer was
absolutely correct. ;-)
Atenciosamente,
Matheus Eduardo Machado Moreira
matheus@gmail.com
Violence is the last refuge of the incompetent.
Salvor Hardin (The Foundation, Isaac Asimov)
2010/3/25 Thiago H. de
Actually, what's happening here is that the result of invoking new
Service() is being stored with the page instance and used to reset the
service field to its default value at the end of each request.
This isn't quite the same as storing it in the session, as the Service
instance will be carried
Thank you guys for your answers... now I can see it pretty clearer :)
I was blundering really bad!
Best, Juan
Howard Lewis Ship wrote:
Actually, what's happening here is that the result of invoking new
Service() is being stored with the page instance and used to reset the
service field
This is a leaky abstraction around the fact that pages are pooled.
They are just too expensive to reconstruct fresh each request, and
there's a lot of opportunities for optimizations that occur because
the pages are pooled and re-used.
On Thu, Mar 25, 2010 at 11:09 AM, Juan Isern
