Revision as of 16:49, 4 September 2007 by Cameron.bateman.oracle.com
Overview of requirements for Facelet support. Note: this document is provisional and subject to change.
- Mechanism for Accumulating design-time meta-data for facelet tags when not using JSP wrapper (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=192393#c14). Primarily this arises from the fact that there is no mandatory TLD-like descriptor for facelets. This means that we need to find alternative ways to know, for example, what tag and attributes are available.
- Support for JSP-editor-like behaviour for tag lookup and EL region partitioniing in the HTML source configuration. To support non-JSP JSF tags, we need to enhance and extend what the HTML SSE configuration provides for situations where we know an XHTML document will be consumed by the facelet view handler.
- WPE support for templating. This is a broad issue that affects both JSP views (jsp:include) and Facelet views (ui:composition). We need to determine the common visual editing tasks involving page fragments and facelet templates and how to implement them. As the ADF page flow concept shows, such fragments are important parts of common usages of JSF even without facelets.
- Identifying that facelets are in use. There are many facet-like activities here such as deciding how to update the web.xml file for servlet-mappings as well as whether an XHTML should be tooled for facelets or simply as a flat HTML file using the xml format. We may need to create a Facelet facet or perhaps decorate the JSF one.