Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Java view technologies and frameworks
open-in-new
<h2 id="at-a-glance">At a glance</h2> <table><tbody><tr><th>Action-based frameworks:</th><td><a href="/facts/Apache_Struts/n6IaPbD7">Apache Struts</a>, <a href="/facts/Spring_Framework/ajIwLM73">Spring MVC</a></td></tr><tr><th>Component-based frameworks:</th><td><a href="/facts/Apache_Click/VDErsYzD">Apache Click</a>, <a href="/facts/Apache_Tapestry/cohzQdmh">Apache Tapestry</a>, <a href="/facts/Apache_Wicket/CMYwKWwh">Apache Wicket</a>, <a href="/facts/Jakarta_Faces/1QhmoE1A">Jakarta Faces</a></td></tr><tr><th>Web template systems:</th><td><a href="/facts/Apache_Tiles/vBxdNbca">Apache Tiles</a>, SiteMesh, <a href="/facts/Thymeleaf/yuuyLXSz">Thymeleaf</a></td></tr></tbody></table> <ul><li><a href="/facts/Jakarta_Faces/1QhmoE1A">Jakarta Faces</a> (JSF), <a href="/facts/Apache_Tapestry/cohzQdmh">Apache Tapestry</a> and <a href="/facts/Apache_Wicket/CMYwKWwh">Apache Wicket</a> are competing component-based technologies, abstracting the <a href="/facts/Stateless_protocol/TgJncyPa">stateless</a> HTTP request-response cycle and the <a href="/facts/Jakarta_Servlet/hf5LQVq1">Jakarta Servlet</a> <a href="/facts/API/GMlN4vUr">API</a> behind an <a href="/facts/Object-oriented_programming/TxNMEcao">object-oriented</a>, event-driven component model.</li> <li>In contrast, Struts and the <a href="/facts/Spring_Framework/ajIwLM73">Spring MVC Framework</a> are action-oriented frameworks that provide a thinner <a href="/facts/Abstraction_layer/EV8c84SY">abstraction layer</a> over the servlet <a href="/facts/API/GMlN4vUr">API</a>.</li> <li>Apache Tiles is a templating framework designed to work with Struts.</li> <li><a href="/facts/Facelets/GSPHKLHM">Facelets</a> is a view definition and templating technology designed to work with JSF.</li> <li>SiteMesh can be used with any <a href="/facts/Jakarta_Server_Pages/LAr4ALkb">Jakarta Pages</a> (JSP).</li> <li>Facelets, Tapestry and Wicket have their own templating approaches based on <a href="/facts/HTML/sSc3fT78">HTML</a>/<a href="/facts/XHTML/6qHnmJSg">XHTML</a>.</li> <li><a href="/facts/Apache_Click/VDErsYzD">Apache Click</a> uses HTML based <a href="/facts/Apache_Velocity/Ed0ENs6Q">Apache Velocity</a> templates and <a href="/facts/Plain_old_Java_object/sTUnd6MN">plain old Java objects</a> (POJOs), with JSP optional.</li></ul> <h2 id="servlet-api">Servlet API</h2> <p class="note">Main article: <a href="/facts/Jakarta_Servlet/hf5LQVq1">Jakarta Servlet</a></p> <p>The Servlet API is the foundation of almost all Java Web View technologies. Servlet provides the basic mechanism for writing Java <a href="/facts/Class_(computer_programming)/zvzkSAtE">classes</a> for web applications. Servlets can respond to HTTP requests, create cookies and maintain sessions. </p> <h2 id="jakarta-pages-jsp">Jakarta Pages (JSP)</h2> <p class="note">Main article: <a href="/facts/Jakarta_Server_Pages/LAr4ALkb">Jakarta Server Pages</a></p> <ul><li>Built on top of the Servlet API, JSP provides a document-centric, tag-based templates, server programming model which can generate many forms of textual content.</li> <li>Java code may be embedded in JSP files and is compiled and executed when a request is received.</li></ul> <h2 id="apache-struts">Apache Struts</h2> <p class="note">Main article: <a href="/facts/Apache_Struts/n6IaPbD7">Apache Struts</a></p> <ul><li>Struts provides for a <a href="/facts/Coupling_(computer_programming)/QEeSaXF3">decoupling</a> of the Controller and the View.</li> <li>Requests are received by a Java Class (Controller) which can decide which View to display.</li> <li>The actual View can be written in different view technologies, like JSP, free marker template, velocity template etc.</li> <li>An XML <a href="/facts/Configuration_file/DDzU0FLJ">configuration file</a> 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.</li> <li>Competitor: Spring MVC, Grails</li></ul> <h2 id="apache-tapestry">Apache Tapestry</h2> <p class="note">Main article: <a href="/facts/Apache_Tapestry/cohzQdmh">Apache Tapestry</a></p> <ul><li>A component-based view framework.</li> <li>Classes are written as POJOs and byte-code transformed at runtime</li> <li>Configured with annotations and naming conventions rather than XML</li> <li>Compared to JSPs, enforces a clear separation of <a href="/facts/HTML_element/s4TKzjUP">HTML markup</a> and Java code.</li> <li>HTML templates can be directly previewed by web designers</li> <li>Changed component classes are live-reloaded into running application for faster development.</li> <li>Uses the <a href="/facts/Post%2fRedirect%2fGet/aSEDfnXo">Post/Redirect/Get</a> navigation pattern for form submission.</li> <li>Competitor: Wicket, JSF</li></ul> <h2 id="apache-tiles">Apache Tiles</h2> <ul><li>This is an HTML templating framework based on the <a href="/facts/Composite_pattern/Q2GvqrD0">composite pattern</a>.</li> <li>It allows for the HTML page to be broken up into multiple "pagelets", called Templates, Definitions and Composing pages.</li> <li>At <a href="/facts/Runtime_(program_lifecycle_phase)/lCxKsrzB">runtime</a> the pagelets are stitched together to generate the final HTML. Pages are written in JSP.</li> <li>Competitor: SiteMesh</li></ul> <h2 id="apache-wicket">Apache Wicket</h2> <p class="note">Main article: <a href="/facts/Apache_Wicket/CMYwKWwh">Apache Wicket</a></p> <ul><li>A component-based view framework.</li> <li>Pages directly interact with stateful Java components on the server.</li> <li>Components and their state are managed by the Wicket framework, freeing the application developer from having to use HttpSession directly to manage state.</li> <li>Does not require XML for configuration.</li> <li>Compared to JSPs, enforces a clear separation of <a href="/facts/HTML_element/s4TKzjUP">HTML markup</a> and Java code.</li> <li>Web page components are 'pushed' into the HTML markup from the code.</li> <li>Competitor: Tapestry, JSF</li></ul> <h2 id="jakarta-faces-and-facelets">Jakarta Faces and Facelets</h2> <p class="note">Main article: <a href="/facts/Jakarta_Faces/1QhmoE1A">Jakarta Faces</a></p> <ul><li>A specification for component-based view frameworks.</li> <li><a href="/facts/Eclipse_Mojarra/1QhmoE1A">Eclipse Mojarra</a> and <a href="/facts/Apache_MyFaces/x4jz55I6">Apache MyFaces</a> implementations are available</li> <li>Typically uses Facelets for XML/XHTML-based templating.</li> <li>Classes are written as POJOs, with Annotations or XML configuration files used to associate them with page and component templates.</li> <li>The <a href="/facts/Unified_Expression_Language/8QfUs9GN">Unified Expression Language</a> allows binding component fields and events to POJO bean properties and methods.</li> <li>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.</li> <li>Navigation can be via configuration file rules or directly specified in the page.</li> <li>Can transparently support <a href="/facts/Ajax_(programming)/cS0P0whT">Ajax</a>.</li> <li>Competitor: Wicket, Tapestry</li></ul> <h2 id="sitemesh">SiteMesh</h2> <p class="note">Main article: SiteMesh</p> <ul><li>SiteMesh is an HTML templating framework based on the "Decoration" model.</li> <li>It allows for the creation of a 'decoration' template which is then applied to any other HTML to generate a new HTML.</li> <li>The newly generated HTML contains elements from the original HTML blended into the template.</li> <li>This allows for the original HTML to be very simple and devoid of any formatting or layout specification. The template, in turn, is devoid of any actual information.</li> <li>Blending the two allows for a consistent <a href="/facts/Look_and_feel/Uo3RcETT">look and feel</a> for all <a href="/facts/Web_page/5JK7xQLe">web pages</a>.</li> <li>Competitor: Tiles</li></ul> <h2 id="spark">Spark</h2> <p class="note">Main article: Spark (software)</p> <ul><li>Spark a micro web framework built around a simple routing system</li> <li>It runs on an embedded <a href="/facts/Jetty_(web_server)/QI8x2ooX">Jetty</a> web server by default, but can be configured to run on other webservers.</li> <li>It supports three different templates engines: <a href="/facts/Apache_Velocity/Ed0ENs6Q">Velocity</a>, <a href="/facts/FreeMarker/FvP4jVza">FreeMarker</a> and <a href="/facts/Mustache_(template_system)/m3EAsoqt">Mustache</a></li> <li>It aims to facilitate rapid development, and does not make use of annotations or proprietary solutions.</li></ul> <h2 id="see-also">See also</h2> <ul> <li>Computer programming portal</li></ul> <ul><li><a href="/facts/List_of_web_service_frameworks/gMVJUs2c">List of web service frameworks</a></li> <li><a href="/facts/List_of_Java_frameworks/0g8X4GEo">List of Java frameworks</a></li></ul>