Ok, so form components using a root CompoundPropertyModel are never
versioned, because their data is in the root model. That makes sense.
But what does the form itself do? It doesn't seem to serialize its root
model, and without doing that, it can't live up to its versioning
"contract."
I'm n
that depends on the component and what it does. if you are using a pull model then there is no point of versioning it because the model is always recalculated even if the user presses the back button. this is also the case with some formcomponents, since their model is always current after request.
Yeah but most models do change, right? The thing is, nothing is calling
modelChanging(), neither the Form process() nor the form component's
updateModel().
So versioning, even if it's on, is not activated. Why is this?
Nathan
Igor Vaynberg wrote:
when a component is versioned and its model is
