When the transformer renders a form view, it lets the form wrapper know about each referenced model property. This allows a precise tracking and can be used for multiple reasons: 1) Verify that the client does not temper with the input fields as specified by the form view author 2) Allow default values to be used for properties which were expected to be send by the client, but for some reason were not. A typical example is a check box. When unchecked, the browser does not send any request parameter, leaving it to the server to handle the situation. This proves to be a very error prone problem when solved on a case by case basis. By having a list of expected property references, the model populator can detect a checkbox which was not send and set the property value to false. NOTE: This added functionality is ONLY useful for SESSION scope forms. Request scope forms are constructed anew for every request and therefore cannot benefit from this extra feature. With the high performance CPUs and cheap memory used in today's servers, session scope forms are a safe choice.
@param currentFormView
@param ref
@param inputType