Java view technologies and frameworks: Difference between revisions

Revision as of 12:01, 29 January 2010

Revision as of 22:39, 11 April 2010

Line 1:

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

{{Article issues|refimprove =January 2009|cleanup =January 2009|copyedit =May 2009}}

A plethora of Java Web Frameworks have mushroomed in the recent years. Some of them are in [[Competition|direct competition]], while others are complementary technologies. It is therefore necessary to understand where exactly each technology/framework fits into the J2EE scheme of things. This page lists the "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.

==At a glance==

Line 16 ⟶ 14:

|

| Tapestry

| SiteMesh

| Sitemesh

|-

|

Line 29 ⟶ 27:

* Wicket, Tapestry and JSF are competing technologies.

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

* SitemeshSiteMesh can be used with any JSP.

* Facelets is designed to work with JSF.

* Wicket and Tapestry have their own native templating.

Line 53 ⟶ 51:

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

* At [[run time]] the pagelets are stitched together to generate the final HTML. Pages are written in JSP.

* '''Competitor''': SitemeshSiteMesh

==SitemeshSiteMesh==

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

Line 64 ⟶ 62:

==Wicket==

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

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

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

Line 72 ⟶ 70:

==Tapestry==

* Provides[[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

==See also==

{{Portal|Java|Wave.svg}}

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

==References==