On Wed, 05 Sep 2012 22:35:17 -0300, Leonardo Uribe <[email protected]>
wrote:
The code comes from that blog, but my objective is do the comparison
in the right way.
I haven't checked the other framework implementations, but the Tapestry
one wasn't right . . .
In theory, it is better to keep the business model
the same, even if is not optimal. In that way, the only thing that
changes is the one related to the framework. Anyway, it sounds better
to fix that part, to reflect the way people using Tapestry use to do
it.
I'm not suggesting to change the business model nor rules, but the very
wrong way the session is used in the Tapestry implementation.
It is necessary the validation for only two fields (BookPage.tml
"Credit Card #:" and "Credit Card Name:". This is how is done with JSF
2:
In few words the idea is just do server side validation over one field
and update the result using ajax. It does not matter if the update is
for all the field including the message (preferred), or just for the
message box, the effect should be the same. The idea is see how the
framework is able to deal with ajax.
Many AJAX scenarios can be done in Tapestry out-of-the-box with Zones and
other AJAX-supporting components.
So just wrap the Form in a Zone and add zone="^" to the Form. In addition,
the AJAX validation in the example, if I got it right, is superfluous.
What exactly this validation is? Does it really needs Tapestry is able to
handle most validation scenarios both client- and server-side without any
additional code.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
