Java view technologies and frameworks: Difference between revisions

Content deleted Content added
Matt5091 (talk | contribs)
No edit summary
Mlavannis (talk | contribs)
No edit summary
Line 3:
Following is list of various view technologies available for the Java platform, and the frameworks which support them.
 
==Servlet API==
* Servlet API: This is the foundation of almost all Java View technologies. It provides the basic framework for writing Java classes that 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 programming model. Java code is embedded in the JSP files and is executed when a request is received.
Line 12 ⟶ 13:
 
* Wicket: Provides a 'Component' view technology - meaning the Request-Response Stateless paradigm of HTTP is abstracted away to give rise to a 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. Further, Wicket provides for a clear separation of HTML markup from code, and there are no XML configuration files to manage.
<small>Small Text</small>