On Mon, 02 Dec 2013 09:35:03 -0200, John <j...@quivinco.com> wrote:
I hear that, but again my point is what do you do with the parameter to
persist it into the page? Must you have 2 members for the same value?
My point is that you're basing this thread in a wrong assumption, which is
persisting parameters. That's wrong. You don't persist parameters, neither
directly or indirectly as you're doing. Period. And, in pages or through
@SessionState/ApplicationStateManager, you persist just what you really
need to. You haven't described your scenario, so I don't know what to
suggest you.
You're probably passing some value from page to component. If you really
need to persist the value, and you should avoid it, you persist the value
in the page, not in the component.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
Help me spend a whole month working on Tapestry bug fixes and
improvements: http://igg.me/at/t5month
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
