In the case of a form, the quick answer is: probably. Tapestry
doesn't really maintain a copy of the form on the server and then cross
reference when you submit. What it does is *rebuild* the form on the server
on submission and make sure that rebuilt form has the same number of widgets
as the form that went out originally.
So if you tweak your form on the client and change the widget count,
you need to somehow tell the server about the change so that the rewind
process matches up. Conversely if your change doesn't alter the number of
submitted widgets, it's quite safe e.g. you can hide/unhide things or add
labels to your heart's content. Just don't add or subtract, say, edit boxes.
--- Pat
> -----Original Message-----
> From: Kertis, Dennis [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 13, 2005 8:56 AM
> To: [email protected]
> Subject: Ajax in tapestry
>
> My understanding of Tapestry is that it maintains the state of the
> component model on the server. I am wondering what would happen if I
> change the DOM using Javascript on the client. Does this alter
> Tapestry's ability to handle things.
>
> -Dennis
>
>
> CONFIDENTIAL, PRIVILEGED COMMUNICATION
> This e-mail transmission is private and intended for the addressee(s)
> only. It may contain information that is privileged and/or confidential.
> If you have received this transmission in error, you are not authorized
> to read, copy, disclose or disseminate it in any manner. If you have
> received it in error, please delete it and all copies (including backup
> copies) that have been made, and transmit a reply message informing the
> sender that it was misdirected.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
