ORIGIN OF JSF

-


Before jsf was introduced there were many frameworks which gained popularity (Spring,Struts etc).All of them offered many benefits explicitly by following MVC2 approach.Despite of those benefits they  lacked something i.e a robust user-interface-oriented framework.We need  better way to handle the view tier.

To address this need,several leading software vendors including SUN,IBM,Oracle and BEA met through the Java Community Process in may 2001 and given  detailed specification for building J2EE thin client web applications whose primary goal is to provide a simple way to build user interfaces for java web applications.This result in Java Specification Request JSR #127.Here are the design goals of JSF taken from the java community process.

  1. Create a standard GUI component framework which can be leveraged by development tools to make it easier for tool users to both create high quality GUIs and manage the GUI's connections to application behavior.
  2. Define a set of simple lightweight Java base classes for GUI components, component state, and input events. These classes will address GUI lifecycle issues, notably managing a component's persistent state for the lifetime of its page.
  3. Provide a set of common GUI components, including the standard HTML form input elements. These components will be derived from the simple set of base classes (outlined in #1) that can be used to define new components.
  4. Provide a JavaBeans model for dispatching events from client-side GUI controls to server-side application behavior.
  5. Define APIs for input validation, including support for client-side validation.
  6. Specify a model for internationalization and localization of the GUI.
  7. Automatic generation of appropriate output for the target client, taking into account all available client configuration data, such as browser version, etc.
  8. Automatic Generation of output containing required hooks for supporting accessibility, as defined by WAI.


Comments

Post a Comment

Popular posts from this blog

What's New in JAVA 8

-
Finally Java 8 released under oracle leadership with many features and enhancements. Though some of the popular JSR's like JSR 294 (Jigsaw) are deferred again to next release, Java 8 still be the largest ever upgrade to java after it was introduced in 1996.  Lets see one of those improvements.  Performance improvement of java.util.HashMap under high hash-collision conditions : Just to give a little background : HashMap is used to store key-value pairs in no.of buckets technically 'Entry' objects . Entry is an inner class of HashMap. Please click  here to see the source code in java 7. Each bucket has a unique number called hash code. When you try to put a key-value pair into the map, the hashmap will look at the hash code of the key, and store the pair in the bucket of which the identifier is the hash code of the key. Let's say if hash code of two keys are same then hash-collision occurs. Till now (prior to Java 8), hash collision is addressed by creati
Read more

Singleton Design Pattern

-
We need to create a class which can have only one instance at any time. Solution 1: public class MySingleton { private static MySingleton singleton= new MySingleton(); private MySingleton(){ System.out.println( "Object Created" ); } public static MySingleton getMySingleton(){ return singleton; } } Let's create the object when we need it, not at the time of loading the class. Solution 2(with Lazy loading): public class MySingleton { // Line : 1 private static MySingleton singleton=null; // Line : 2 private MySingleton(){ System.out.println( "Object Created" ); } // Line : 3 public static MySingleton getMySingleton(){ // Line : 4 if(singleton == null) // Line : 5 { singleton = new MySingleton();
Read more

Internals of JSF

-
Once jsf project set up properly i.e entries in the web.xml,jsf related jars in lib folder of your web app( setting up jsf project ) we have to create a faces-config.xml to make our set up into a full fledged jsf application. Creating Faces-config.xml :: In the name itself telling us that it contains all the configurations needed for all jsf pages.In fact we don't need to create the file with the same name.We can create it with any name and we have to mention same as a context parameter in the WEB.xml ( setting up jsf project ).Now its the time to jump into the detailed view.   Fallowing are the two main components that we use frequently. 1)Managed Beans It represents a Java bean that will be instantiated dynamically at the run time by JSF container.We can achive inversion of control in JSF. Ex: Class User{ private String name; private String Address; //setters and getters for both properties } Declaration in faces-config.xml   <man
Read more