In Oracle adf life cycle we have different phases are there
1) Restore View/Initialize Context: In case of post request view is restore view. In this request from a page is passed to bindingContext, which finds the page definition file that matches the URL.
If page is not loaded earlier view is initialized. bindingContainer object which is the run time representation of the page definition file. Life cycle context which stores the information about adf life cycle.
2) Prepare model: In this model prepares and initializes. In this bindingContainer prepares and evaluates any page or Taskflow parameters and executes them.
3) Apply input values: Whatever values we enter in the input text, those values can be mapped with bindings in the page definition file and those values gets stored in the temporary location/string.
4) Validate input values/Process validations: In this validations are takes place ie temporary string values is converted to the correct type.
5) Update model values: The component values are updated in the model and local values are discard.
6)Validate model values: Updated value is validated even in the entity level.
7) Invoke application: After bradcast root components, it executes action and actionListener methods
8) Metadata commit: This phase commits the runtime metadata changes to the model. It always executes before render response
9) Prepare render and Render response: This is the final phase is sent for rendering. Prepare render is sent for all the registered listeners. BindingContainer also refreshed.
This helps in updating any changes that happened during validation process. and finally page is build
1) Restore View/Initialize Context: In case of post request view is restore view. In this request from a page is passed to bindingContext, which finds the page definition file that matches the URL.
If page is not loaded earlier view is initialized. bindingContainer object which is the run time representation of the page definition file. Life cycle context which stores the information about adf life cycle.
2) Prepare model: In this model prepares and initializes. In this bindingContainer prepares and evaluates any page or Taskflow parameters and executes them.
3) Apply input values: Whatever values we enter in the input text, those values can be mapped with bindings in the page definition file and those values gets stored in the temporary location/string.
4) Validate input values/Process validations: In this validations are takes place ie temporary string values is converted to the correct type.
5) Update model values: The component values are updated in the model and local values are discard.
6)Validate model values: Updated value is validated even in the entity level.
7) Invoke application: After bradcast root components, it executes action and actionListener methods
8) Metadata commit: This phase commits the runtime metadata changes to the model. It always executes before render response
9) Prepare render and Render response: This is the final phase is sent for rendering. Prepare render is sent for all the registered listeners. BindingContainer also refreshed.
This helps in updating any changes that happened during validation process. and finally page is build
No comments:
Post a Comment