Content deleted Content added
rollback self-promotion. Sorry |
Added section about JSF/Facelets and added a few bits on JSF elsewhere |
||
Line 28:
* Tiles is a templating framework which is designed to work with Struts.
* SiteMesh can be used with any JSP.
* Facelets is a view definition and templating technology designed to work with JSF.
* Jt is a design pattern framework for the rapid implementation of web applications. It features a wizard application for automated generation. It supports JSP, struts and Ajax.
* Wicket, Tapestry and
* Click uses HTML based velocity templates and plain old Java objects. JSP is optional.
Line 46:
* The actual View is written as a JSP page.
* An XML [[configuration file]] is used to specify the "Page Navigation", i.e. the flow of the request to the appropriate Controller, and which View to display based on the outcome of the Controller.
* '''Competitor''': Though Struts does not have any direct competitor in its league, Component View Technologies (like Wicket, Tapestry, JSF) are generally accepted as superior.
==Tiles==
Line 75:
* HTML components can directly refer to the component methods and attributes.
* '''Competitor''': Wicket, JSF
==JSF/Facelets==
* [[JavaServer Faces|Java Server Faces]] provides a 'Component' view technology while [[Facelets]] (optionally) provides xml/xhtml based view definition and templating.
* Classes are written as POJOs and Annotations or configuration files are used to associate them with Faces.
* The [[Unified Expression Language]] allows binding component fields and events to POJO bean properties and methods.
* Conversion and validation constraints can be specified in Facelets and are automatically applied, normally resulting in reposting of the same page with error information in case of failure.
* Navigation can be via configuration file rules or directly specified in the page.
* Can transparently support [[Ajax]].
* '''Competitor''': Wicket, Tapestry
{{Portal|Java}}
| |||