component tree

The MyFaces tag allows you to store data (including entire backing beans) as part of the component tree rather than just the value bindings.

You can use a Facelets TagHandler to inject the logic to decide whether components in the body of a tag are added to the component tree.

Remember that the endgame of a Facelets template is to create a JSF component tree.

In this case, the JSF implementation cannot restore the component tree, which must be created in the Render Response phase.

Tags in Facelets because everything is treated as a component in a component tree.

JSF cannot build the component tree, and later cannot look up the component tree that was already created.

Facelets knows about the JSF component tree, and its sole purpose in life is to build that component tree.

Listing 15 just uses the type of the value binding to decide if the components defined in the tag's bodies get added to the component tree.

Please specify the root of your domain component tree.

Finally, the Render Response phase creates a response component tree and forwards the response.

When it is added to a component tree, but the tree is not visible yet, the peer will be still not created.

First, the framework needs to restore the component tree of the form page.

Traversing the JSF component tree recursively.

Using custom tag libraries to construct the component tree in the view root.

Many GUI toolkits often setup some innate mechanism to avoid this, for example, by a complex lock on a component tree.

Pages that represent MVC-style views; pages reference view roots via the JSF component tree

Listing 14 shows how the printed component tree looks