Java Reference
In-Depth Information
Using JSF, one will get automatic binding of data to visual
components, mapping, and validation of input data and saving
of state between requests. Using JSP - you have to implement
it manually. JSF also supports Ajax interaction with the
server.
If you are developing an application that requires a standard
behavior, such as data entry, editing and display - JSF is the
best bet. If you need an online application with fast response,
navigation within a page on the client side, such as Gmail or
twitter - you can spend a lot of time translating the client-side
logic components in the JSF. In this case, you better use the
JSP, as a source of data and JavaScript library to display data.
Therefore JSF is not suitable for all types of projects so those
who use JSP will not be moving to JSF.
JSF Pros
:
•
MVC
framework.
Offers
a
clean
separation
between
behavior and presentation.
•
UI
component
model
(binding,
events,
state
saving,
validation).
• Multiples front-ends (desktop and mobiles browsers).
• Hides the HTTP infrastructure.
• Use IDE RAD environments.
• Automatic event handling (map http requests to component
specific).
