On Sun, 19 Oct 2014 06:18:11 -0200, Lance Java <lance.j...@googlemail.com>
wrote:
And I just repeated what everyone has said here as an answer!
Yeah, this looks like a clear case not understanding the difference of
server-side versus client-side and when stuff in either side happens. When
you first render *the page*, you don't have the values needed to build
your message, which seem to be defined by form fields filled by the user,
so one solution is to change or build the message client-side. The
server-side doesn't know what the user typed until client-side informs it
through form submission or an AJAX. In other words, you just cannot define
your message while rendering the page because it doesn't have the
information it needs. This isn't related to Tapestry: actually, it's about
client-side and server-side. You'd have the exact same problem using
Wicket or JSF or Struts (or any other framework which doesn't mix up
client-side and server-side, using the same code for both, as GWT or Echo).
I've just told exactly what Lance said in his answer, but with different
words. :)
On 18 Oct 2014 23:42, "Name Surname" <wintertime0...@outlook.com> wrote:
> But why should I move from my solution while I am so close to it?
Because you're actually *not* close to it? ;)
Unrelated curiosity: your page surely looks like Spanish to me (my mother
language is Portuguese, which is similar), but your variables are written
in another language I couldn't figure out . . . What's it? :) Catalan?
Basque?
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
