Java view technologies and frameworks: Difference between revisions

Revision as of 06:19, 15 December 2012

Latest revision as of 20:14, 17 July 2024

(72 intermediate revisions by 47 users not shown)

Line 1:

{{Short description|Programming language and libraries}}

Various '''Java [[Web application frameworks]]''' have appeared in recent years. Some of them are in direct competition, while others are complementary technologies. It is therefore necessary to understand where exactly each technology/framework fits into the [[Java EE|JEE]] scheme of things. This page lists the [[Model–view–controller|View]] technologies. These are the frameworks which are used for defining the web pages and the server-side programs which handle the requests (clicks) generated by the web pages.

'''Java view technologies and frameworks''' are [[web-based]] [[software libraries]] that provide the [[user interface]], or "[[Model–view–controller|view-layer]]", of [[Java (programming language)|Java]] [[web application]]s. Such [[application framework]]s are used for defining [[web page]]s and handling the [[HTTP]] [[List of HTTP header fields#Requests|requests]] (clicks) generated by those web pages. As a sub-category of [[web framework]]s, view-layer frameworks often overlap to varying degrees with web frameworks that provide other functionality for Java web applications.

Java view-layer frameworks often claim to support some or all of the [[model–view–controller]] design pattern.

==At a glance==

{| class="wikitable" border="1"

|-

! Action-based frameworks:

! [[HTTP]] Paradigm

| [[Apache Struts]], [[Spring Framework|Spring MVC]]

! [[Component-based software engineering|Component Paradigm]]

! [[Web template system|Templating]]

|-

! Component-based frameworks:

| [[Apache Struts|Struts]]

| [[Apache Click]], [[Apache Tapestry]], [[Apache Wicket]], [[Jakarta Faces]]

| [[Wicket]]

| [[Tiles]]

|-

! Web template systems:

|

| [[Apache Tapestry|TapestryTiles]], SiteMesh, [[Thymeleaf]]

| [[SiteMesh]]

|-

|

| [[JavaServer Faces|JSF]]

| [[Facelets]]

|-

|

| Jt Design Patterns

| [[Apache Click]]

|}

* Struts is relatively easier to use for beginners because it contains the familiar HTTP paradigm of [[HTTP request|Request]]/Response. However, the Component based frameworks are architecturally superior, and usually recommended for creating more complex [[web application]]s.

* [[Jakarta Faces]] (JSF), [[Apache Tapestry]] and [[Apache Wicket]] are competing component-based technologies, abstracting the [[Stateless protocol|stateless]] HTTP request-response cycle and the [[Jakarta Servlet]] [[API]] behind an [[Object-oriented programming|object-oriented]], event-driven component model.

* Wicket, Tapestry and JSF are competing technologies.

* In contrast, Struts and the [[Spring Framework|Spring MVC Framework]] are action-oriented frameworks that provide a thinner [[abstraction layer]] over the servlet [[API]].

* Tiles is a templating framework which is designed to work with Struts.

* Apache Tiles is a templating framework designed to work with Struts.

* SiteMesh can be used with any [[JavaServer Pages|JSP]].

* [[Facelets]] is a view definition and templating technology designed to work with JSF.

* SiteMesh can be used with any [[Jakarta Server Pages|Jakarta Pages]] (JSP).

* 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.

* WicketFacelets, Tapestry and FaceletsWicket have their own native templating approaches based on [[HTML]]/[[XHTML]].

* [[Apache Click]] uses HTML based velocity[[Apache Velocity]] templates and [[plain old Java objects.object]]s JSP(POJOs), iswith JSP optional.

==Servlet API==

{{main |Jakarta Servlet}}

* This is the foundation of almost all Java View technologies.

* It provides the basic framework for writing Java classes, called '[[Servlet]]s' that can respond to HTTP requests, create cookies and maintain sessions.

* Rahul

The Servlet API is the foundation of almost all Java Web View technologies. Servlet provides the basic mechanism for writing Java [[class (computer programming)|class]]es for web applications. Servlets can respond to HTTP requests, create cookies and maintain sessions.

==JSP==

* Built on top of the Servlet API, JSP provides for a HTML centric Server [[Parallel programming model|programming model]].

* Java code is embedded in the JSP files and is executed when a request is received.

==Jakarta Pages (JSP) ==

==Struts==

{{main |Jakarta Server Pages}}

* Built on top of the Servlet API, Struts provides for [[decoupling]] between the Controller and the View.

* 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.

* Java code may be embedded in JSP files and is compiled and executed when a request is received.

==Apache Struts==

{{main |Apache Struts}}

* Struts provides for a [[coupling (computer programming)|decoupling]] of the Controller and the View.

* Requests are received by a Java Class (Controller) which can decide which View to display.

* The actual View iscan be written asin adifferent view technologies, like JSP, free marker template, velocity template pageetc.

* 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''': Spring MVC, Grails

* '''Competitor''': Though Struts does not have any direct competitor in its league, Component View Technologies (like Wicket, Tapestry, JSF) are generally accepted as superior.

==TilesApache Tapestry==

{{main |Apache Tapestry}}

* This is a HTML templating framework based on the "Composite" model.

* It allows for the HTML page to be broken up into multiple [[pagelet]]s, called Templates, Definitions and Composing pages.

* A component-based view framework.

* At [[run time (program lifecycle phase)|run time]] the pagelets are stitched together to generate the final HTML. Pages are written in JSP.

* Classes are written as POJOs and byte-code transformed at runtime

* Configured with annotations and naming conventions rather than XML

* Compared to JSPs, enforces a clear separation of [[HTML element|HTML markup]] and Java code.

* HTML templates can be directly previewed by web designers

* Changed component classes are live-reloaded into running application for faster development.

* Uses the [[Post/Redirect/Get]] navigation pattern for form submission.

* '''Competitor''': Wicket, JSF

==Apache Tiles==

{{see also |d:Special:EntityPage/Q28912908|l1=Apache Tiles}}

* This is an HTML templating framework based on the [[composite pattern]].

* It allows for the HTML page to be broken up into multiple "pagelets", called Templates, Definitions and Composing pages.

* At [[runtime (program lifecycle phase)|runtime]] the pagelets are stitched together to generate the final HTML. Pages are written in JSP.

* '''Competitor''': SiteMesh

==SiteMeshApache Wicket==

{{main |Apache Wicket}}

* [[SiteMesh]] is a HTML templating framework based on the "Decoration" model.

* It allows for the creation of a 'decoration' template which is then applied to any other HTML to generate a new HTML.

* The newly generated HTML contains elements from the original HTML blended into the template.

* 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.

* Blending the two allows for a consistent [[look and feel]] for all [[web page]]s.

* '''Competitor''': Tiles...

* A component-based view framework.

==Wicket==

* Pages directly interact with stateful Java components on the server.

* [[Apache Wicket|Wicket]] provides a 'Component' view technology - meaning the Request-Response Stateless paradigm of HTTP is abstracted away to give rise to an [[Object-oriented programming|Object Oriented]] Stateful paradigm.

* Components and their state are managed by the Wicket framework, freeing the application developer from having to use HttpSession directly to manage state.

* Pages now directly interact with Stateful Java Components on the server.

* Does not require XML for configuration.

* Components and their State are managed by the [[Wicket framework]], freeing the application developer from having to use HttpSession directly to manage state themselves.

* Further,Compared Wicketto providesJSPs, forenforces a clear separation of [[HTML element|HTML markup]] from code, and thereJava are no XML configuration files to managecode.

* Web page components are 'pushed' into the HTML markup from the code.

* '''Competitor''': Tapestry, JSF

==Jakarta Faces and Facelets==

==Tapestry==

{{main |Jakarta Faces}}

* [[Tapestry_(programming)|Tapestry]] provides a 'Component' view technology.

* Classes are written as POJOs and Annotations are used to configure them as Tapestry components.

* HTML components can directly refer to the component methods and attributes.

* '''Competitor''': Wicket, JSF

* A specification for component-based view frameworks.

==JSF/Facelets==

* [[Eclipse Mojarra]] and [[Apache MyFaces]] implementations are available

* [[JavaServer Faces|Java Server Faces]] provides a 'Component' view technology while [[Facelets]] (optionally) provides xml/xhtml based view definition and templating.

* Typically uses Facelets for XML/XHTML-based templating.

* Classes are written as POJOs and Annotations or configuration files are used to associate them with Faces.

* Classes are written as POJOs, with Annotations or XML configuration files used to associate them with page and component templates.

* 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.

Line 86 ⟶ 90:

* '''Competitor''': Wicket, Tapestry

==SiteMesh==

{{Portal|Java}}

{{main |SiteMesh}}

<!-- formatting; please do not remove until some more text lines are added to compensate spacing -->

* SiteMesh is an HTML templating framework based on the "Decoration" model.

==See also==

* It allows for the creation of a 'decoration' template which is then applied to any other HTML to generate a new HTML.

*[[List of web service frameworks]]

* The newly generated HTML contains elements from the original HTML blended into the template.

* 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.

* Blending the two allows for a consistent [[look and feel]] for all [[web page]]s.

* '''Competitor''': Tiles

==ReferencesSpark==

{{main |Spark (software)}}

* [[Java Servlet]] Technology (http://java.sun.com/products/servlet/)

* [[JavaServer Pages]] Technology (http://java.sun.com/products/jsp/)

* Spark a micro web framework built around a simple routing system

* [[Apache Struts]] 2 Documentation (http://struts.apache.org/2.1.6/docs/home.html)

* It runs on an embedded [[Jetty (web server)|Jetty]] web server by default, but can be configured to run on other webservers.

* Apache Tiles (http://tiles.apache.org/)

* It supports three different templates engines: [[Apache Velocity|Velocity]], [[FreeMarker]] and [[Mustache (template system)|Mustache]]

* [[Click Framework]] Project Documentation (http://incubator.apache.org/click/)

* It aims to facilitate rapid development, and does not make use of annotations or proprietary solutions.

* Apache Wicket (http://wicket.apache.org/)

* [http://tapestry.apache.org/ Tapestry Home Page]

==See also==

{{Portal|Computer programming}}

* [[List of web service frameworks]]

* [[List of Java frameworks]]

[[Category:Java (programming language)]]

[[Category:Java APIs]]