On Tue, 30 Aug 2011 10:08:18 -0300, Wechsung, Wulf <wulf.wechs...@sap.com>
wrote:
Hi Thiago,
Hi!
maybe it was wrong to send it to the users list, I should've tried the
dev list.
You've posted in the correct list. The dev one is for the development of
Tapestry itself, not development with Tapestry, which is the case of this
thread.
I mean, from the code it was clear to me that formsupport.store could be
used in that capacity.
But it isn't meant to store values in general, just what is needed to
process a form submission.
So the reason for my mail was to find out if that my perception was true
(as you confirmed) and also to encourage a discussion on if those
specific cases might deserve their own persistence scope to enable the
(component) developer to say "I need this value for the lifecycle of
this form" instead of writing a component action that does this.
I don't think persistence scopes make any sense for form submission
processing. The lifecycle of a form is just rendering and processing.
Component actions are only executed in form submissions, so data used in
these component actions have no better place to be stored than in the
commands themselves. I would agree if you didn't need a component action
for your scenario, but you do. ;)
--
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
