You would save yourself the pleasure of answering such posts, but also
the time involved in it, if you update the documentation.
ציטוט Mind Bridge:
The hidden fields guarantee that the 'rewind' will proceed exactly in
the same way as the 'render' that generated the form. That ensures that
the form will be rewinded in exactly the same way as it was rendered and
eliminates the possibility of StaleLink exceptions.
An example: during a 'render' the condition passed to Conditional may be
true, but when the form is submitted it could be 'false'. As a result
the form will be rewinded differently.
With 'If' that cannot happen as the value of the condition was stored in
a hidden field and is read from there during a rewind.
'volatile' turns this behaviour off and If starts behaving exactly as a
Conditional. I would not recommend using it, unless you know very well
what you are doing.
XYZ wrote:
When For and If are inside a Form, they generate many hidden fields.
What are they for?I notice that getVolatile is used inside
evaluateCondition() of IfBean. But I do not yet see the side effects
of setting volatile="true" when using the If and For inside a form
(except that much less html is generated). Can somebody explain what
are the side effects? Thank you.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
