Skip to main content

JSF pros and Cons

JSF was developed using MVC design pattern and is driven by Java Community Process (JCP). The advantage of JSF is that it provides a clean separation between presentation and behaviour. UI can be created by page author using reusable UI components and business logic part can be implemented using managed beans.

It’s a fact that JSF libraries like RichFaces and ICEfaces greatly add lot of components to develop thin-client rich Internet applications (RIA) in pure Java. Component libraries like RichFaces for JSF has easy integration capabilities to AJAX and speeds business application development. They also includes strong support for the skinnability of JSF applications. But after using JSF in two projects I realized that JSF has complex life cycle and takes a lot of effort to develop custom components. Apart from JDeveloper there is no other IDE which supports a rich interface for component drag and drop. Eclipse is till trying and I have not even seen one stable version. Many JSF component frameworks lack maturity, documentation, or both. JSF is fast maturing and become stable and is a step in the right direction.

Comments

Post a Comment

Popular posts from this blog

SAAS Simple Maturity Model

There are two architectural models – commonly referred as SAAS Maturity models- that describe the transition of a service to what is called Multi-tenant efficient, highly scalable application. The SAAS Maturity model described by Microsoft has four distinct stages and is illustrated below. Another similar well-known model for SaaS-maturity is known as Forrester-model but adds another stage known as "Dynamic Business Apps-as-a-service". The three key Attributes of a SAAS Architecture: Configurability: Metadata used to configure the way the application behaves for customers Multi-tenant Efficiency : Maximizing the sharing of resources across tenants Scalability: Maximizing concurrency, resource efficiency SAAS Simple Maturity Model (Microsoft, 2006) SaaS Maturity Model (Forres
Post a Comment
Read more

What is an ESB?

ESB is another of these amorphous terms that means different things to different people. An ESB can be thought of as the next generation of Service Oriented Architecture. Everybody knows web services today, and they have been used extensively to allow companies to break the tyranny of proprietary architectures. Now you can wire applications to service providers without having to know or worry about the provider's underlying operating system or programming language. It is an architectural concept/construct - not a technology, despite some vendors (and even gartner) telling you otherwise. You'll find many different types of technology can fulfil the conceptual role of an ESB, hence be careful not to associate it with a particular technology. Therefore designing the architecture is more important than choosing a 'product'. An Enterprise Service Bus (ESB) is the "backbone" of the service-oriented architectural model which allows different protocols to be communica
Post a Comment
Read more

Web Service Framework comparison

Web Services is one of those concepts made all the more difficult to understand because of the myriad acronyms and abbreviations that are superfluous in any discussion. Covering all the concepts and standards associated with Web Services is a vast topic in itself. There are a large number of standards around Web Services. These standards define the norms of a Web Services implementation and ensure that a Web Services is accessed independently of the client platform. There are numerous frameworks available to select to build web service today. Below is the most widely used ones. Product Does it fit my need? Axis2.0 Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis SOAP stack to build on the lessons learnt from Apache Axis. An advantage of Axis 2 is its support for the binding frameworks XMLBeans. Axis 2 with XMLBeans is widely
Post a Comment
Read more