Public classes for the Java code API of Facelets. The vast majority of Facelets users have no need to access the Java API and can get all their work done using the tag-level API.

Sequence of events in the compilation and execution of a Facelets PDL Page

Startup Time

During the initialization of the impl's Application instance, an instance of SAXCompiler is created and the standard tag libraries are added to it. The instance is kept as an ivar of the Application. An instance of DefaultResourceResolver() is created and stuck into a new instance of DefaultFaceletFactory(), which is kept as an ivar of Application. DefaultFaceletFactory uses the resolver to get the baseUrl for all the pages in the app. Any taglibs that are declared in the faces-config are added here as well.

Compilation


PENDING(edburns): complete this.

RenderResponse.execute calls PDL.buildView().

This get the DefaultFaceletFactory from the application and calls
getFacelet() on it, passing the viewId.

This checks a cache of compiled views and determines if one needs to be
compiled.  In this case, a compiled view is not available, so the
compiler is invoked on the physical file corresponding to the viewId.

The SAXCompiler (extends Compiler) has a root CompilationManager, and a
SAX Handler called CompilationHandler (extends DefaultHandler).

A CompilationManager is created for each physical file in the tree of
physical files that can make up a Facelets PDL view.  The
CompilationManager keeps a stack of CompilationUnit instances.  This
handler is the bridge between the SAX XML engine and the Facelet
implementation.

The CompilationManager keeps a stack of Tags.  Each tag has a location,
localname, and a collection of attributes.  Each attribute has a
location, a name, and a value.

The compiler builds a tree of Tag instances.  Each Tag has an XML
namespace in which it belongs, the localName by which it is used in this
page, a qualified Name, and a collection of attributes.