Why do I need a ajaxResponseRenderer within my backing class, when I want to
update a zone?
Eg: having a table with all users, and when clicking a user I want to update
another table which shows the address of the selected user. Now I have to:
-create a zone with the address table grid, and place it into a zone
-trigger that zone from an eventlink or pagelink within the main table
-make ajaxResponseRenderer for that eventlink in the backing class.
Question: Why do I need this ajax response in backing? Because I'm already
updating the user object by user.id that is given in context on eventLink
click. So why is it no sufficient to just update the zone from the tml
frontend?
<p:usernameCell><t:eventLink event="selectUsername" context="user.id"
zone="userprofile">${user.username}</t:eventLink></p:usernameCell>
<t:zone id="userprofile">
<t:if test="selectUsername">
<t:grid source="user.address">
</t:grid>
</t:if>
</t:zone>
class UserPage{
@Property
boolean isSelectUsername;
User user;
void onSelectUsername(Long id) {
isSelectUsername = true;
user = dao.find(id);
ajaxResponseRenderer.addRender("userprofile", userprofile);
}
}
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Why-is-ajaxRenderer-needed-for-zone-update-tp5717391.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
