This page (revision-1) was last changed on 24-Jul-2006 14:47 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version -1 and -1

At line 1 added 9 lines

A "Fixup" is a generalised action applied to a fully generated [component tree|ComponentTree] on a [render cycle|RenderCycle] that "fixes up" the component values by merging them with data taken from some source.

The main sort of fixup is the "EL value fixup". Any components of type UIBound (that includes all UIInput, UIOutput and nested instances in clusters such as UISelect) which do ''not'' have a value set, but which ''do'' have a value binding, will have the value filled in by querying the value binding.

A second sort of fixup is an "[RSVC fixup|RSVCFixup]", whereby the [RequestSubmittedValueCache|RSVC] for the current request will be queried for any "unapplied" values that are yet to be applied to the model. These values may be in the RSVC as a result of a previous erroneous submission that is being returned to the user, or as a result of an [RSVC replay|RSVCReplay] state preservation strategy (not yet fully implemented). These cached values will ''take priority'' over any values either in the model, or supplied to UIBound objects if they are found during a render cycle.

In terms of the [handler sequence|HandlerSequence] diagram, fixups execute as "step 8" of the rendering pipeline, after constructing the view tree by a producer and before rendering via IKAT.