1.1 --- a/visualweb.ravehelp.rave_nbpack/javahelp/org/netbeans/modules/visualweb/ravehelp/rave_nbpack/docs/web/create/tag/framework/framework_jsf_aboutcrud.html	Sat Aug 02 02:29:29 2008 -0700
     1.2 +++ b/visualweb.ravehelp.rave_nbpack/javahelp/org/netbeans/modules/visualweb/ravehelp/rave_nbpack/docs/web/create/tag/framework/framework_jsf_aboutcrud.html	Sun Aug 03 13:50:16 2008 +0200
     1.3 @@ -19,21 +19,33 @@
     1.4  The IDE provides support for this common programming task by letting you quickly generate code for CRUD 
     1.5  functionality based on entity classes in your project.</p>
     1.6  
     1.7 -<p>An application that implements CRUD functionality typically contains the following artefacts.</p> 
     1.8 +<p>A JSF application that implements CRUD functionality typically contains the following artefacts.</p> 
     1.9  
    1.10  <ul>
    1.11 -    <li><b>Controller classes.</b> A controller class is a wrapper for an entity class that provides clients with access to the database through the methods in the entity class. For example, the controller class has methods for creating and deleting an entry in the data source, getting all of the entries in the data source, or getting a specific entry in the data source. </li>
    1.12 -    <li><b>Converter classes.</b> A converter class takes input from the form and converts it into the type that matches the data in the data source.</li>
    1.13 -    <li><b>JSP pages.</b> The JSP pages are the web user interface for accessing and modifying the data in the data source. </li>
    1.14 +    <li><b>JPA Controller classes.</b>
    1.15 +    A typical JSF application may have JPA and JSF controller classes.
    1.16 +    A JPA controller class is a wrapper for an entity class that provides clients with access to the database 
    1.17 +    through the methods in the entity class.
    1.18 +    A JPA controller class contains the logic for creating, editing and destorying an entry in the data source, 
    1.19 +    getting all of the entries in the data source, and getting a specific entry in the data source.
    1.20 +    Generally you would not need to modify the JPA controller classes unless the database schema changed, in which case
    1.21 +    you could regenerate the classes for the new schema.</li>
    1.22 +    <li><b>JSF Controller classes.</b>
    1.23 +    A JSF controller class generally contains code that invokes methods in the JPA controller classes and 
    1.24 +    demonstrates which exceptions to catch.
    1.25 +    To modify your application you would generally modify the JSF controller classes.</li>
    1.26 +    <li><b>JSF Converter classes.</b> A JSF converter class takes input from the form and converts it into the type that matches the data 
    1.27 +    in the data source.</li>
    1.28 +    <li><b>JSP pages.</b> The JSP pages are the web user interface for accessing and modifying the data in the data source.</li>
    1.29  </ul>
    1.30  
    1.31  <p>The following wizards generate code for implementing CRUD functionality in the application.</p>
    1.32      <ul>
    1.33          <li><b>JPA Controller Classes from Entity Classes.</b> This wizard generates the CRUD controller classes based on the entity classes in the project. 
    1.34          The wizard creates one controller for each entity class and places the controller in the same package as the entity class.</li>
    1.35 -        <li><b>JSF Pages from Entity Classes.</b> This wizard generates the CRUD controller classes, converters and JSP pages based on the entity classes in the project.
    1.36 +        <li><b>JSF Pages from Entity Classes.</b> This wizard generates the JSF controller classes, converters and JSP pages based on the entity classes in the project.
    1.37          For each entity class, the wizard creates four JSP pages that let you view, edit, create, and destroy entries in the data source.
    1.38 -        The JSP pages use the JSF framework. </li>
    1.39 +        The JSP pages use the JSF framework and access the JSF converter and controller classes. </li>
    1.40      </ul>
    1.41      
    1.42  <dl> 

     2.1 --- a/visualweb.ravehelp.rave_nbpack/javahelp/org/netbeans/modules/visualweb/ravehelp/rave_nbpack/docs/web/create/tag/framework/framework_jsf_fromentity.html	Sat Aug 02 02:29:29 2008 -0700
     2.2 +++ b/visualweb.ravehelp.rave_nbpack/javahelp/org/netbeans/modules/visualweb/ravehelp/rave_nbpack/docs/web/create/tag/framework/framework_jsf_fromentity.html	Sun Aug 03 13:50:16 2008 +0200
     2.3 @@ -35,20 +35,10 @@
     2.4  <p>When you click Finish the IDE generates the following artifacts for each entity class.</p>
     2.5  <ul>
     2.6      <li><b>JPA controller classes.</b> 
     2.7 -    For each entity class the IDE creates one JPA controller class and places the controller in the specified location.
     2.8 -    A JPA controller class is a wrapper for an entity class that provides clients with access to 
     2.9 -    the database through the methods in the entity class. 
    2.10 -    The JPA controller class contains the logic for creating, editing and destorying an entry in the data source, 
    2.11 -    getting all of the entries in the data source, and getting a specific entry in the data source. 
    2.12 -    </li>
    2.13 -    <li><b>JSF classes.</b> For each entity class the IDE creates one JSF controller class and one JSF converter class and places the classes in the specified location. 
    2.14 -    The JSF controller class generally contains code that invokes methods in the JPA controller classes and 
    2.15 -    demonstrates which exceptions to catch.
    2.16 -    The JSF converter class takes input from the form and converts it into the type that matches the data in the data source.</li>
    2.17 +    For each entity class the IDE creates one JPA controller class in the specified location.</li>
    2.18 +    <li><b>JSF classes.</b> For each entity class the IDE creates one JSF controller class and one JSF converter class and places the classes in the specified location. </li>
    2.19      <li><b>JSP pages.</b> 
    2.20 -    For each entity class, the IDE creates four JSP pages that let you view, edit, create, and destroy entries in the data source.
    2.21 -    The JSP pages are the web user interface for accessing the data in the data source. 
    2.22 -    </li>
    2.23 +    For each entity class, the IDE creates four JSP pages that are used to view, edit, create, and destroy entries in the data source.</li>
    2.24  </ul>
    2.25  
    2.26  <p>The IDE also creates the following:</p>
    2.27 @@ -57,7 +47,7 @@
    2.28      (<tt>IllegalOrphanException.java</tt>, <tt>NonexistentEntityException.java</tt>, <tt>PreexistingEntityException.java</tt>, 
    2.29      <tt>RollbackFailureException.java</tt>)</li>
    2.30      <li>Three JSF utility classes 
    2.31 -    (<tt>JsfUtil.java</tt>, <tt>PagingInfo.java</tt>, and <tt>JsfCrudELResolver.java</tt>).</li>
    2.32 +    (<tt>JsfUtil.java</tt>, <tt>PagingInfo.java</tt>, and <tt>JsfCrudELResolver.java</tt>)</li>
    2.33      <li>Default stylesheet and JavaScript files</li>
    2.34  </ul>
    2.35