Request Flow

The following illustrates the POM process flow for handling a request:

The following is the sequence of method calls during POM creation and content creation:

• doOnNodeReady(): Called on a component when the node representing the component is added to the POM tree. Called once for each component.

• doOnPOMReady(): Called on each node when no more nodes are to be added to the POM tree. The Portal Runtime traverses the tree from top to bottom, calling the method for each component.

  If a node is created in a doOnPOMReady() method, the new node's doOnNodeReady() method is called and then the doOnPOMReady() method finishes execution. The doOnPOMReady() method of the new node is then called.

• Request Event Handlers: Called if there are request events for special nodes.

• doBeforeContent(): Called just before content creation. The Portal Runtime traverses the tree from bottom to top, calling the method for each component.

• doContent(): Called to retrieve content from the top-most component in the POM tree. doContent() is called only in default mode. An alternative method is called for other modes. See Modes.

  It is up to this mode to invoke the doContent() (or alternative method) of any other nodes in the POM tree.

• doAfterContent(): Called on each node when that component's doContent() (or alternative method) is finished.

Calls to doOnNodeReady() , doOnPOMReady() and request event handlers are part of the POM creation phase. Calls to doBeforeContent() , doContent() (or an alternative method if the mode is not the default mode) and doAfterContent() are part of the content creation phase.

More information: Managing Nodes