ADF supports event-driven development, where an event is raised to mark a status of the process, and the component will subscribe for the event to proceed with the process. For example, consider a page in which a component in a page fragment inside a task flow is to be refreshed whenever the command button in that page is clicked. In this case, we cannot use
partialSubmit because the ID of the component will not be available in the page fragment inside the task flow that holds the component to be refreshed. In this case, the
commandButton option in the outside page will raise an event named
REFRESH and publish it. The component inside the page fragments will subscribe for the
REFRESH event, refresh the component, ...