OCPSoft.com - Simple SolutionsCommunity Documentation
PrettyFaces follows a set order of events when processing each request. If a request is not mapped, or does not match a rewrite-rule, then the request will not be processed by PrettyFaces, and will continue normally.
URL-matching, path-parameter parsing, query-parameter handling, and value injection into managed beans.
DynaView calculation (if a view Id is dynamic, the EL method will be called.)
PrettyFaces relinquishes control of the current request via RequestDispatcher.forward(“/context/faces/viewId.jsf”).
If the view-ID is a JSF view, page-action methods are called after RESTORE_VIEW phase, unless the optional phaseId attribute is specified.
The server continues to process the request as normal.
Search for classpath resources named META-INF/pretty-config.xml in the ServletContext resource paths for this web application, and load each as a configuration resource.
Check for the existence of a context initialization parameter named com.ocpsoft.pretty.CONFIG_FILES. If it exists, treat it as a comma-delimited list of context relative resource paths (starting with a /), and load each of the specfied resources.
Check for the existence of a web application configuration resource named /WEB-INF/pretty-config.xml, and load it if the resource exists.