From richfaces-svn-commits at lists.jboss.org Tue Jul 8 06:43:53 2008 Content-Type: multipart/mixed; boundary="===============5379305849841143164==" MIME-Version: 1.0 From: richfaces-svn-commits at lists.jboss.org To: richfaces-svn-commits at lists.jboss.org Subject: [richfaces-svn-commits] JBoss Rich Faces SVN: r9443 - trunk/docs/cdkguide/en/src/main/docbook/modules. Date: Tue, 08 Jul 2008 06:43:49 -0400 Message-ID: --===============5379305849841143164== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: artdaw Date: 2008-07-08 06:43:49 -0400 (Tue, 08 Jul 2008) New Revision: 9443 Modified: trunk/docs/cdkguide/en/src/main/docbook/modules/intro.xml Log: http://jira.jboss.com/jira/browse/RF-3692 - Introduction was added Modified: trunk/docs/cdkguide/en/src/main/docbook/modules/intro.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/cdkguide/en/src/main/docbook/modules/intro.xml 2008-07-08 09= :41:08 UTC (rev 9442) +++ trunk/docs/cdkguide/en/src/main/docbook/modules/intro.xml 2008-07-08 10= :43:49 UTC (rev 9443) @@ -11,7 +11,101 @@ = Introduction - This document is aimed to provide guidelines for... + The major benefit of the JSF framework is a component based archit= ecture. = + The component in JSF is not just a set of HTML code rendered and i= nterpreted by a browser. = + The JSF component is a composition of a client-side widget coupled= with the server-side object = + that represents component behavior including data validation, even= ts handling, business layers bean binding, etc. = - + = + In contrast to a page-oriented development approach, = + JSF allows to use a component-oriented paradigm to build a well-de= signed, = + highly customizable UI interface based on reusable components. + + + However, there is not yet enough sets of rich components on the ma= rket that might enable the rapid application developments. = + One of important problems is a long and very complicated process o= f the component creation. = + Even the very primitive JSF component requires to write the UIComponent class, = + Renderer class, Tag class + and a faces configuration file (faces-config.xml). = + + + In order to use the component library in a Facelets environment, = + you should add the *.taglib.xml file to this = checklist. + + = + Creation of the rich component takes even more time. = + You have to provide the ListenerTagHandler class, a class for creating a listener interface, + an event processing method name in a listener interface, = + an event class, render specific classes for each possible render k= it used with the component. + + + Therefore, the process of JSF component creation is pretty complic= ated but repeatable. = + Jonas Jacobi and John R. Fallows in their "Pro JSF and Ajax B= ulling Rich Internet Components" book describe = + the process in details. = + This description and used approaches are very similar to our own e= xperience and have been used as a methodology = + for Component Development Kit (CDK) - a sub-p= roject of RichFaces + that allows you to easily create rich components with built-in Aja= x support. = + = + + + + The significant features of the Component Development Ki= t (CDK) are: + + + + + Quick development start. = + A new component development starts from a pre-generated co= mponent project template. = + It contains the whole required infrastructure and necessar= y files generated. + It's necessary only to have a Maven installed. = + All other required stuff will be loaded and configured aut= omatically. + + + + + Declarative approach for a component development. = + It's necessary only to specify meta-data and a code s= pecific for your component. = + All other required artifacts are generated for you. + + + + + Independent development life-cycle. Component De= velopment Kit (CDK) presumes = + development of each component isolated from each other wit= h further assembling them into the component library. = + Hence, this allows to organize a continuous process when o= ne component is already in production condition, = + but another is just started. + + + + + Add Ajax capability to the existing JSF applications and c= reate a first-class rich components = + with built-in Ajax functionality. + + + + + Facility for automatic testing. = + At the moment of generating the initial project structure, = + the Unit Test classes are also genera= ted. = + The RichFaces also provides the Mock-= test facility that allows to emulate = + a run-time environment and automatically test the componen= ts before their are gathered into the result library. + + + + + Optimization for different JSF implementations. = + As soon as the most part of a result code is generated, th= e Component Development Kit (CDK) = + becomes able to generate an implementation specific code a= long with a universal code. = + It makes sense if it"s necessary to optimize a result= code using features specific for = + the particular implementation. For example, for using with= JSF 1.2 only. + + + + + Create a modern rich user interface look-and-feel with JSP= -like templates and skins-based technology. + RichFaces comes with a number of predefined skins to get y= ou started, = + but you can also easily create your own custom skins. = + + + \ No newline at end of file --===============5379305849841143164==--