NetBeans IDE Samples Catalog: commits@netbeans-samples.kenai.com: Archive

Mailing List
Downloads
» Downloads
Message Forum
» General Discussion
Source Code Repository
» Source Code Repository
Wiki
» NetBeans IDE Samples Catalo...
WikiHomePage
» WikiHomePage

NetBeans IDE Samples Catalog was started in May 2009, is owned by Irina Valerievna Filippova, and has 26 members.

» Join This Project

[netbeans-samples~samples:69] (Commit message missing)

» Back to List Archive

Chronological | Threaded

« Previous Message Next »

« Previous Thread Next »

From: ondrej58@kenai.com
To: commits@netbeans-samples.kenai.com
Subject: [netbeans-samples~samples:69] (Commit message missing)
Date: Wed, 16 Sep 2009 20:43:13 +0000

Project: netbeans-samples
Repository: samples
Revision: 69
Author: ondrej58
Date: 2009-09-16 20:43:08 UTC
Link:

Log Message:
------------

Revisions:
----------
69

Added Paths:
------------
NB68/catalog/web/resources/images/harmony.jpg
NB68/catalog/README_files/0-Connect-DB.png
NB68/catalog/web/resources/images/mario.jpg
NB68/catalog/web/resources/images/faith-s.jpg
NB68/catalog/web/resources/images/cat1.gif
NB68/catalog/src/java/web
NB68/catalog/web/WEB-INF/sun-web.xml
NB68/catalog/README_files/0-Execute-DB.png
NB68/catalog/web
NB68/catalog/web/WEB-INF/faces-config.xml
NB68/catalog/web/resources/images/paris-s.jpg
NB68/catalog/web/resources/images/bailey.jpg
NB68/catalog/src/conf
NB68/catalog/web/resources/images/monique.jpg
NB68/catalog/src/java/controller/ItemFacade.java
NB68/catalog/web/resources/images/olie-s.jpg
NB68/catalog/web/resources/js
NB68/catalog/nbproject/build-impl.xml
NB68/catalog/web/resources/images/thaicat-s.jpg
NB68/catalog/README_files/showdetail.jpg
NB68/catalog/web/resources/images/chantelle.jpg
NB68/catalog/src/java/controller/PagingInfo.java
NB68/catalog/src/java/web/messages.properties
NB68/catalog/web/resources/css
NB68/catalog/web/index.html
NB68/catalog/src/java
NB68/catalog/web/resources/images/katzen.jpg
NB68/catalog/web/resources/images/bailey-s.jpg
NB68/catalog/nbproject/ant-deploy.xml
NB68/catalog/src/java/controller/Catalog.java
NB68/catalog/web/resources/images/chantelle-s.jpg
NB68/catalog/web/resources/images/charlie-s.jpg
NB68/catalog/web/WEB-INF
NB68/catalog/nbproject/genfiles.properties
NB68/catalog/web/resources/images/mimi.jpg
NB68/catalog/web/resources/images/cat7.gif
NB68/catalog/web/resources/images/anthony.jpg
NB68/catalog/web/resources/images/cat11.gif
NB68/catalog/web/resources/images/monique-s.jpg
NB68/catalog/web/resources/images/cat4.gif
NB68/catalog/web/resources/images/katzen-s.jpg
NB68/catalog/web/resources/images/gaetano.jpg
NB68/catalog/web/resources/css/styles.css
NB68/catalog/web/resources/images/cat10.gif
NB68/catalog/src/java/model
NB68/catalog/README_files/ViewTabData.jpg
NB68/catalog/web/detail.xhtml
NB68/catalog/web/resources/images/bob-s.jpg
NB68/catalog/web/resources/images/elkie.jpg
NB68/catalog/README_files/0-Select-DB.png
NB68/catalog/web/resources/images/faith.jpg
NB68/catalog/web/resources/images/simba.jpg
NB68/catalog/web/resources/images/Thumbs.db
NB68/catalog/web/resources/images/cat3.gif
NB68/catalog/web/resources/images/princess.jpg
NB68/catalog/web/resources/images/cat9.gif
NB68/catalog/build.xml
NB68/catalog/src/java/controller
NB68/catalog
NB68/catalog/web/resources/images/princess-s.jpg
NB68/catalog/web/WEB-INF/web.xml
NB68/catalog/web/resources/images/anthony-s.jpg
NB68/catalog/web/resources/images/olie.jpg
NB68/catalog/web/resources/images/cat2.gif
NB68/catalog/web/resources/images
NB68/catalog/web/resources/images/paris.jpg
NB68/catalog/nbproject/project.xml
NB68/catalog/web/resources
NB68/catalog/catalog.sql
NB68/catalog/web/resources/images/mimi-s.jpg
NB68/catalog/web/resources/images/mario-s.jpg
NB68/catalog/web/resources/images/gaetano-s.jpg
NB68/catalog/web/resources/images/simba-s.jpg
NB68/catalog/README_files/Thumbs.db
NB68/catalog/nbproject/project.properties
NB68/catalog/README_files/0-Run-DB.png
NB68/catalog/src/java/model/Item.java
NB68/catalog/README_files
NB68/catalog/README.html
NB68/catalog/web/resources/images/charlie.jpg
NB68/catalog/web/resources/images/cat6.gif
NB68/catalog/web/resources/images/banner_logo.gif
NB68/catalog/web/resources/images/cat8.gif
NB68/catalog/extra
NB68/catalog/web/resources/images/cat5.gif
NB68/catalog/README_files/resources.jpg
NB68/catalog/web/resources/images/cat12.gif
NB68/catalog/web/list.xhtml
NB68/catalog/nbproject
NB68/catalog/src
NB68/catalog/web/resources/images/harmony-s.jpg
NB68/catalog/web/resources/images/elkie-s.jpg
NB68/catalog/web/resources/images/thaicat.jpg
NB68/catalog/src/conf/persistence.xml
NB68/catalog/test
NB68/catalog/README_files/petcatjsf2.jpg
NB68/catalog/web/resources/images/bob.jpg

Diffs:
------
Index: NB68/catalog/README_files/0-Select-DB.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/0-Select-DB.png
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README_files/showdetail.jpg
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/showdetail.jpg
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README_files/petcatjsf2.jpg
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/petcatjsf2.jpg
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README_files/0-Execute-DB.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/0-Execute-DB.png
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README_files/Thumbs.db
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/Thumbs.db
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README_files/0-Run-DB.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/0-Run-DB.png
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README_files/resources.jpg
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/resources.jpg
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README_files/ViewTabData.jpg
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/ViewTabData.jpg
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README_files/0-Connect-DB.png
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: NB68/catalog/README_files/0-Connect-DB.png
___________________________________________________________________
Added: svn:mime-type
 + application/octet-stream

Index: NB68/catalog/README.html
===================================================================
--- NB68/catalog/README.html (revision 0)
+++ NB68/catalog/README.html (revision 69)
@@ -0,0 +1,915 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html><head>
+
+
+ <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
+ <title>Java EE 6 Pet Catalog</title>
+
+
+</head><body>
+
+<h1> 
+</h1>
+<h2>Java EE 6 Pet Catalog with GlassFish v3
+</h2>
+ 
+This Pet Catalog app demonstrates a web application that
+uses JSF 2.0, Java EE 6, with GlassFish 
+<h2>Running the Pet Catalog Application</h2>
+<ol>
+ <li>Download and install <a
href="http://bits.netbeans.org/netbeans/6.8/m1/";>NetBeans IDE 6.8 with
+GlassFish v3 </a>(Glassfish v3 preview is Java EE 6
+Preview) 
+. 
+ </li>
+</ol>
+ 
+<h3>Create the Catalog Item database table 
+</h3>
+In order to run the sample code you first have to create and fill
+in  the Item database table. 
+ 
+Instructions are provided for Java DB. The Java DB database is
+installed with Sun GlassFish Enterprise Server. The SQL script works
+with MySQL also. 
+ 
+<ol>
+ <li>Start NetBeans IDE 
+ </li>
+ <li>Ensure that GlassFish is registered in the NetBeans IDE, as
+follows:
+ <ul>
+ <li>Click the Services tab in the NetBeans IDE.</li>
+ <li>Expand the Servers node. You should see GlassFish v2 in
+the list of servers. If not,
+register GlassFish v2 as follows:
+ <ul style="margin-left: 40px;" type="square">
+ <li>Right-click the Servers node and select Add Server.
+This opens an Add Server Instance wizard.</li>
+ <li>Select GlassFish v2 in the server list of the
+wizard
+and click the Next button.</li>
+ <li>Enter the location information for the server and
+click
+the Next button.</li>
+ <li>Enter the admin name and password and click the
+Finish
+button.</li>
+ </ul>
+ </li>
+ </ul>
+ </li>
+ <li>Start the Java DB database as follows:
+ <ul>
+ <li>Click the Services tab in the NetBeans IDE.</li>
+ <li>Expand the databases node. You should see the Java DB
+database in the list of databases.
+
+ <img src="README_files/0-Select-DB.png" alt="">
+</li>
+</ul>
+ </li>
+ <li>Right-click the database connection node
+(jdbc:derby://localhost:1527/sample[app on APP]) and choose
+Connect... 
+ <img alt="" src="README_files/0-Connect-DB.png">
+ </li>
+ <li>You might be prompted for a userid and password. Enter userid app and  password app . 
+ </li>
+ <li>Right click on the database connection node
+(jdbc:derby://localhost:1527/sample[app on APP]) and select 
+Execute Command... 
+ <img alt="" src="README_files/0-Execute-DB.png">
+ </li>
+ <li>Copy the contents of the <code>catalog.sql</code>
+file in the catalog
+directory and paste the contents into
+the SQL command window. </li>
+ <li>Click the Run SQL button in the task bar at the top
+to execute the query. 
+(Note it is normal to get an error message when running the SQL script
+the first time: 'DROP TABLE' cannot be performed on 'ITEM' because it
+does not exist.)
+ <img alt="" src="README_files/0-Run-DB.png">
+ </li>
+ <li>
+You can view the contents of a table or column by right-clicking the
+table or column and selecting View Data as shown  below: 
+ 
+ <a name="fig13"></a>
+ <table border="0" cellpadding="2" cellspacing="0" width="600">
+ <tbody>
+ <tr>
+ <td class="grey3" align="center"><img
src="README_files/ViewTabData.jpg" alt="Viewing the Contents of a Table"
style="border: 0px solid ; width: 600px; height: 196px;">
+ <div class="pad3"> Figure
+13. Viewing the Contents of a Table</div>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+ </li>
+
+</ol>
+<h3> 
+</h3>
+<h3>Running the Sample solution: 
+</h3>
+
+If you want to run the sample solution, you have to create the catalog
+database tables first as described above. 
+ 
+<ol>
+ <li>Open the <code>catalog</code> project as follows:
+ <ul>
+ <li>In NetBeans IDE, click Open Project in the File menu.
+This opens the Open Project dialog.</li>
+ <li>Navigate in the Open Project dialog to the
<code>catalog </code>
+directory and click the Open Project button.</li>
+ </ul>
+ 
+In response, the IDE opens the <code>catalog</code> project. 
+You can view the logical structure of the project in the Projects
+window (Ctrl-1). </li>
+ <li>Run the <code>catalog</code> by right-clicking on the
<code>catalog</code>
+project in the Projects window and selecting Run Project. The NetBeans
+IDE compiles the application, deploys it on Glassfish, and brings up
+the default page in your browser.  (at
+http://localhost:8080/catalog/).</li>
+ <li>If you have problems, open the
+catalog/setup/sun-resources.xml file and verify that the
+property values it specifies match those of the database you created.
+Edit the property values as necessary.</li>
+</ol>
+<h2> </h2>
+<h2> 
+</h2>
+<a
href="https://techdayscode.dev.java.net/servlets/ProjectDocumentList?folderID=9890";>
+</a>
+
+<h3>Explanation of the usage of JSF 2.0 and Java EE 6 in a sample Store
+Catalog Application</h3>
+The image below shows the Catalog Listing page, which allows a user to
+page through a list of items
+in a store. 
+ 
+<div style="margin-left: 40px;"> <img alt="" style="width: 472px; height:
541px;" src="README_files/petcatjsf2.jpg"> 
+</div>
+ 
+<h3>JSF 2.0 Facelets XHTML instead of JSP 
+</h3>
+For JSF 2.0, Facelets XHTML is the preferred way to declare JSF Web
+Pages. JSP is supported for backwards compatibility, but not all JSF
+2.0 features will be available for views using JSP as their page
+declaration language.  JSF 2.0 Facelets has some nice features
+like templating (similar in functionality to Tiles) and composite
+components, which I'm not going to discuss here but you can read about
+that in this article: <a
href="http://www.ibm.com/developerworks/java/library/j-jsf2fu2/index.html";>http://www.ibm.com/developerworks/java/library/j-jsf2fu2/index.html</a>
+and in this Tech Tip <a
href="/enterprisetechtips/entry/true_abstraction_composite_ui_components">Composite
+UI Components in JSF 2.0.</a> 
+ 
+ 
+The Catalog application's resources 
+ 
+JSF 2.0 standardizes how to define web resources. Resources are any
+artifacts that a component may need in order to be rendered properly --
+images, CSS, or JavaScript files.  With JSF 2.0 you put resources
+in a resources
+directory or a subdirectory. 
+<img alt="" style="width: 297px; height: 532px;"
src="README_files/resources.jpg"> 
+ 
+In your Facelets pages, you can access css files with the 
+<h:outputStylesheet>,  javascript files with the
+<h:outputScript> , and images with the <h:graphicImage> JSF
+tags. The list.xhtml uses the <code>
+<h:outputStylesheet</code> tag to load the <code>styles.css
</code>stylesheet
+, and the <code><h:graphicImage</code>
+tag to display images from the resources as
+shown below: 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from:  list.xhtml 
+ </td>
+ </tr>
+ <tr>
+ <td> <code> 
+ </code><code><h:outputStylesheet
+name="css/styles.css" target="body"/> 
+ 
+ <h:graphicImage
+library="images" name="banner_logo.gif"  />   
</code><code> 
+ 
+ </code></td>
+ </tr>
+ </tbody>
+</table>
+ 
+ 
+The Catalog application uses a resource bundle to contain the static
+text and
+error messages used by the Facelets pages. Putting messages in a
+resource bundle makes it easier to modify and internationalize your
+Application text.  The messages are in a properties file in a java
+package directory. 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from:  messages.properties  
+ </td>
+ </tr>
+ <tr>
+ <td> <code></code><code> 
+ </code>Title=Pet Catalog 
+Next=Next 
+Previous=Prev 
+Name=Name 
+ <code> 
+ </code><code> 
+ </code></td>
+ </tr>
+ </tbody>
+</table>
+ 
+ 
+The resource bundle is configured in the faces-config.xml File (you
+don't need any other
+configuration in the faces-config.xml for JSF 2.0, as explained later
+you no longer have to configure managed beans and navigation with XML).
+ 
+ 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from:  faces-config.xml 
+ </td>
+ </tr>
+ <tr>
+ <td> <code></code><code> 
+ </code><application> 
+    <resource-bundle> 
+       
+<base-name>web.WebMessages</base-name> 
+        <var>msgs</var> 
+    </resource-bundle> 
+</application> 
+ <code> 
+ </code><code> 
+ </code></td>
+ </tr>
+ </tbody>
+</table>
+ 
+ 
+ 
+The List.xhtml facelets page uses a JSF <code style="font-weight: bold;
color: rgb(204, 0, 0);" class="cCode">dataTable</code>
+component to display a list of
+catalog items in an html table.  The dataTable component is useful
+when you want to show a set of
+results in a table. In a JavaServer Faces application, the <code
style="color: rgb(204, 0, 0); font-weight: bold;" class="cCode">UIData</code>
+component
+(the superclass of dataTable)  supports binding to a collection of
+data objects. It does the
+work of iterating over each record in the data source. The HTML <code
style="font-weight: bold; color: rgb(204, 0, 0);"
class="cCode">dataTable</code>
+renderer
+displays the data as an HTML table. 
+ 
+In the list.xhtml web page the dataTable is defined as shown
+below: 
+(Note: Red
+colors
+are for Java
EE
+tags, annotations code, 
+and Green
+is
+for my code
+or variables) 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from:  list.xhtml 
+ </td>
+ </tr>
+ <tr>
+ <td> <code> 
+ </code><code><h:dataTable value='#{catalog.items}' var='row'
+border="1" 
+      cellpadding="2"
cellspacing="0"></code><code> 
+ 
+ </code></td>
+ </tr>
+ </tbody>
+</table>
+ 
+The <code style="color: rgb(204, 0, 0); font-weight: bold;"
class="cCode">value</code> attribute of a <code style="font-weight: bold;
color: rgb(204, 0, 0);" class="cCode">dataTable</code>
+tag references the data to be included
+in the table. The <code style="font-weight: bold; color: rgb(204, 0, 0);"
class="cCode">var</code>
+attribute specifies a
+name that is used by the components within the <code style="font-weight:
bold; color: rgb(204, 0, 0);" class="cCode">dataTable</code>
+tag as an alias to the data referenced in the <code style="font-weight:
bold; color: rgb(204, 0, 0);" class="cCode">value</code>
+attribute of <code style="font-weight: bold; color: rgb(204, 0, 0);"
class="cCode">dataTable</code>.  In the <code style="font-weight: bold;
color: rgb(204, 0, 0);" class="cCode">dataTable</code>
+tag from the <code class="cCode">List.jsp</code>
+page, the <code style="font-weight: bold; color: rgb(204, 0, 0);"
class="cCode">value</code> attribute points to a list
+of catalog items. The <code style="font-weight: bold; color: rgb(204, 0,
0);" class="cCode">var</code>
+attribute points
+to a single item in that list. As the <code style="color: rgb(204, 0,
0); font-weight: bold;" class="cCode"></code><code style="font-weight: bold;
color: rgb(204, 0, 0);" class="cCode">dataTable</code>
+component<code style="color: rgb(204, 0, 0); font-weight: bold;"
class="cCode"></code> iterates through the list, each reference to
<code>dataTableItem</code><code class="cCode"></code> points to the
current item in the
+list. 
+ 
+<h3> JSF 2.0 Annotations instead of XML configuration</h3>
+The dataTable's <code style="font-weight: bold; color: rgb(204, 0, 0);"
class="cCode">value</code>
+is bound to the <code>items</code>
+property
+of the <code>catalog</code> managed
+bean. With JSF 2.0 managed beans do not have to be configured in the
+faces-config.xml file, you annotate the managed beans instead as shown
+below: 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: <code>Catalog</code>.java</td>
+ </tr>
+ <tr>
+ <td> <code> 
+ 
+ @ManagedBean 
+ @SessionScoped 
+public class Catalog
+implements Serializable { 
+ 
+ </code><code> 
+ </code><code></code> 
+ <code> 
+ </code> </td>
+ </tr>
+ </tbody>
+</table>
+By convention, the name of a managed bean is the same as the class
+name, with the first letter of the class name in lowercase. To specify
+a managed bean name you can use the name attribute of the ManagedBean
+annotation, like this: @ManagedBean(name = "Catalog"). 
+ 
+ 
+This <code>Catalog</code>
ManagedBean <code>items</code>
+property is defined as shown below: 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: <code>Catalog</code>.java</td>
+ </tr>
+ <tr>
+ <td> 
+     private
+List<Item> items = null; 
+ 
+    public List<Item> getItems() { 
+        if (items == null) { 
+           
+getPagingInfo(); 
+           
+items = getNextItems(pagingInfo.getBatchSize(),
+pagingInfo.getFirstItem()); 
+        } 
+        return items; 
+    } 
+ 
+ <code> 
+ 
+ </code> </td>
+ </tr>
+ </tbody>
+</table>
+ 
+ 
+The getItems()
+method returns a List of item objects<code style="color: rgb(204, 0, 0);
font-weight: bold;" class="cCode"></code>.
+The JSF <code style="font-weight: bold; color: rgb(204, 0, 0);"
class="cCode">dataTable</code>,
+supports data binding to a
+collection of data objects.  The <code style="font-weight: bold; color:
rgb(204, 0, 0);" class="cCode">dataTable</code>
+object is modeled as a collection
+of row objects that can be accessed by a row index.  The APIs
+provide mechanisms to position to a specified row index, and to
+retrieve an object that represents the data that corresponds to the
+current row index.    
+ 
+The <code>Item</code>
+properties <code style="font-weight: bold;">name</code>, <code style="font-weight: bold;">imagethumburl</code>,
+and <code>price</code>
+<code></code>are
+displayed with the <code>column</code>
+component: 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: list.xhtml 
+ </td>
+ </tr>
+ <tr>
+ <td> <code> 
+ <h:dataTable var="row"
value="#{catalog.items}"> 
+ </code><code style="font-weight: bold;">  <h:column> 
+      <f:facet
+name="header"> 
+          <h:outputText value="#{msgs.Name}"/> 
+      </f:facet> 
+      <h:commandLink
+action="#{catalog.showDetail(row)}" value="#{row.name}" /> 
+ 
+</h:column></code><code style="font-weight: bold;"> 
+  <h:column> 
+      <f:facet
+name="header"> 
+          <h:outputText value="#{msgs.Photo}"/> 
+      </f:facet> 
+ </code><code style="font-weight: bold;"><h:graphicImage
+library="images" name="#{row.imagethumburl}"/></code><code style="font-weight:
bold;"> 
+ 
+</h:column></code><code> 
+   <h:column> 
+      
+<f:facet name="header"> 
+          
+<h:outputText value="#{msgs.Price}"/> 
+      
+</f:facet> 
+      
+<h:outputText value="#{row.price}"/> 
+  
+</h:column> 
+ </h:dataTable> 
+ 
+ </code> </td>
+ </tr>
+ </tbody>
+</table>
+ 
+The <code>column</code>
+tags represent columns of data in a <code style="font-weight: bold; color:
rgb(204, 0, 0);" class="cCode">dataTable</code>
+component. While
+the <code style="font-weight: bold; color: rgb(204, 0, 0);"
class="cCode">dataTable</code> component is iterating over the rows of
+data, it processes
+the UIColumn component associated with each <code>column</code>
+tag for each row in
+the table. 
+ 
+The <code style="font-weight: bold; color: rgb(204, 0, 0);"
class="cCode">dataTable </code>component  iterates through the
+list
+of items
+(<code>catalog.items</code>) 
+and displays the <code></code>item (<code>var="row")
</code>attribute <code>value. </code>Each
+time UIData iterates through the list of items, it renders one cell in
+each <code>column</code>. 
+ 
+The dataTable and column tags use <code>facet</code>
+to represent parts of the
+table that are not repeated or updated. These include <code>header</code>s,
+footers,
+and captions. 
+ 
+<h4>Java EE 6: JSF 2.0,  EJB 3.1, and Java Persistence API
+(JPA)  2.0 
+</h4>
+The <code>Catalog</code>
ManagedBean annotates the field <code>private
+ItemFacade itemFacade;</code> 
+with <code>@EJB</code>
+, which causes an <code>itemFacade</code>
+EJB to be
+injected when the managed bean is instatiated. The<code>
+Catalog</code> <code>getNextItems
</code>method
+calls the <code>ItemFacade
+</code>Stateless EJB which uses the Java
+Persistence API
+EntityManager
+Query object to return a list of items.
+<code></code> 
+ 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: Catalog.java</td>
+ </tr>
+ <tr>
+ <td> <code> 
+ </code><code>@ManagedBean 
+ @SessionScoped 
+public class Catalog
+implements Serializable {</code> 
+ <code> 
+ @EJB 
+    private ItemFacade itemFacade; 
+ 
+    public List<Item>  getNextItems(int
+maxResults, int firstResult) {  
+      
+return itemFacade.findRange(maxResults,
+firstResult);     
+   } 
+ 
+ </code> </td>
+ </tr>
+ </tbody>
+</table>
+ 
+<a href="/enterprisetechtips/entry/a_sampling_of_ejb_3">EJB 3.1 No-interface local client
View</a> 
+<code></code> 
+With EJB 3.1, local EJBs  do not  have to a implement
+separate interface, that is, all public methods of the bean class are
+automatically exposed to the caller. 
+ 
+<a style="font-weight: bold;"
href="/enterprisetechtips/entry/a_sampling_of_ejb_3">Simplified
+Packaging</a> 
+ 
+With Java EE 6, EJBs can be directly packaged in a WAR file just like
+web components. 
+ 
+The <code>ItemFacade</code>
+EJB uses the Java
+Persistence API
+EntityManager
+Query object to return a list of items. The <code>ItemFacade</code>
+EJB annotates the field <code>private
+EntityManager
em;</code> 
+with <code style="color: rgb(204, 0, 0);">@PersistenceContext</code> ,
+which causes an entity manager to be
+injected when it is instatiated. 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: ItemFacade.java</td>
+ </tr>
+ <tr>
+ <td> <code> 
+ </code><code>@Stateless 
+public class ItemFacade
+{</code> 
+ <code> 
+ @PersistenceContext(unitName
+= "catalogPU") 
+    private EntityManager
+em; 
+ 
+    public List<Item> findRange(int maxResults,
+int firstResult) { 
+ Query
+q =
+em.createQuery("select object(o) from Item as o"); 
+        q.setMaxResults(maxResults); 
+       
+q.setFirstResult(firstResult); 
+        return q.getResultList(); 
+    } 
+ 
+ </code> </td>
+ </tr>
+ </tbody>
+</table>
+ 
+<h4 style="font-weight: normal;">The Java Persistence <a
href="http://java.sun.com/javaee/5/docs/api/javax/persistence/Query.html";>Query
+APIs</a> are used to create and execute queries that can return a
+list of results.  The JPA Query interface provides
+support for pagination via the setFirstResult() and setMaxResults()
+methods: <code>q.setMaxResults</code>(int maxResult)
+sets the maximum number of results to retrieve. <code>q.setFirstResult</code>(int startPosition)
+sets the position of the first result to retrieve.</h4>
+In the code below, we show the <code>Item</code>
+entity class which maps to the  ITEM table that stores the
+item instances. This is a
+typical Java Persistence entity object. There are two requirements for
+an entity: 
+<ol>
+ <li>annotating the class with an @Entity
+annotation. 
+ </li>
+ <li> annotating   the primary key identifier with @Id 
+ </li>
+</ol>
+Because the fields name, description.... are basic mappings from the
+object fields to columns of the same name in the database table, they
+don't have to be annotated.  The O/R  relationships with
<code>Address</code>
+and <code>Product</code>
+are also annotated. For more information on
+defining JPA entities see <a
href="http://www.apress.com/book/bookDisplay.html?bID=10093";>Pro
+EJB 3: Java Persistence API book</a>. 
+ 
+<a name="code-example-2" target="bpcatalog"></a>
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: Item.java</td>
+ </tr>
+ <tr>
+ <td> <code> 
+ @Entity 
+public class Item
+implements java.io.Serializable { 
+ 
+ </code><code style="color: rgb(204, 0, 0); font-weight:
bold;">@Id</code><code> 
+    private Integer id;</code><code></code><code> 
+    private String name;    
+    private String description;    
+    private String imageurl;    
+    private String imagethumburl;  
+    private BigDecimal price; 
+ @ManyToOne 
+    private Address
+address; 
+ </code><code> @ManyToOne 
+    private Product
+product;</code> 
+ <code> 
+    public Item() { } 
+ </code> 
+ <code>    public String getName() { 
+       
+return name; 
+    }</code><code> 
+    public void setName(String name) { 
+       
+this.name = name; 
+    }</code><code> 
+ </code><code> 
+    ... 
+}    
+ 
+ </code> </td>
+ </tr>
+ </tbody>
+</table>
+ 
+ 
+ 
+The <code>Catalog</code>
+ManagedBean pages through the list of <code>Item</code>s
+by
+maintaining the PagingInfo.firstItem and PagingInfo.batchSize
+attributes and passing these as
+parameters to the  <code></code><code>getNextItems</code>(firstItem,
+batchSize) method.
+The <code>catalog</code>'s
+scope  is
+defined with the annotation <code>@SessionScoped</code>,
+a JSF Managedbean
+with session scope will be stored in the session meaning that the
+bean's properties will stay alive for the life of the Http Session. 
+ 
+ 
+A JSF <code>commandButton</code>
+is  used to provide a button to click on to
+display the next page of items.  The <code>commandButton</code>
+tag is used to submit an action event
+to the application.  
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: list.xhtml</td>
+ </tr>
+ <tr>
+ <td> <code> 
+  <h:commandButton
+ action="#{catalog.next}"
+value="#{msgs.Next}" />    
+ </code> 
+ </td>
+ </tr>
+ </tbody>
+</table>
+ 
+This <code class="cCode">commandButton action
+</code>attribute
+references the <code>catalog</code>
+Managed bean <code>next</code>()
+method which calculates
+the
+next page's first row number  and returns a logical outcome
+String, which causes the list.xhtml
+page
+to display the next page's
+list .
+The <code>catalog</code>
+<code>next</code>
+method is defined as shown below: 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: <code>catalog</code>.java</td>
+ </tr>
+ <tr>
+ <td> 
+ <code>   public String next() { 
+       if (firstItem + batchSize
+< itemCount()) { 
+          
+firstItem += batchSize; 
+       } 
+       return "list"; 
+   } 
+ </code> 
+ </td>
+ </tr>
+ </tbody>
+</table>
+ 
+<h3> JSF 2.0 Simplified Navigation 
+</h3>
+ 
+The JavaServer Faces
2.0  <code style="color: rgb(204, 0, 0); font-weight:
bold;">NavigationHandler</code>
+convention adds .xhtml to the logical outcome of the action method (in
+this example <code style="color: rgb(0, 102, 0); font-weight:
bold;">list</code>)
+and
+loads that file, in this case, it loads the <code style="font-weight:
bold;">list.xhtml</code>
+page after this method returns. If the action doesn't begin with a
+forward slash (/), JSF assumes that it's a relative path.  You can
+specify an absolute path by adding the slash like this "/items/list". 
+ 
+ 
+A JSF <code>commandLink</code>
+is  used to provide a link to click on to
+display a page with the <code style="font-weight: bold;">item</code> details. This <code
style="font-weight: bold;" class="cCode">commandLink
+action</code><code class="cCode"> </code>attribute 
+references The <code>catalog</code>
+<code>showDetail()</code>
+method: 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: list.xhtml</td>
+ </tr>
+ <tr>
+ <td> <code> 
+   <h:column> 
+       <f:facet name="header"> 
+          <h:outputText
+value="Name"/> 
+       </f:facet> 
+       <h:commandLink action="#{catalog.showDetail(row)}"
+value="#{row.name}"/>    
+   </h:column> 
+ </code> 
+ </td>
+ </tr>
+ </tbody>
+</table>
+ 
+<a style="font-weight: bold;"
href="http://weblogs.java.net/blog/cayhorstmann/archive/2009/07/say_sayonara_to_1.html";>With
+JSF 2.0 you can now specify parameters in method expressions.</a> The
<code>dataTable</code>
<code>row</code>
+object associated with the selected <code></code>link
+is passed as a parameter in the  <code></code><code>"#{catalog.showDetail(row)}"</code><code></code>
+method
+expression. 
+The <code>Catalog</code>
+<code>showDetail()</code>
+method  gets the <code>item</code>
+data from the
+input parameter,
+and returns a string which causes the detail.xhtml
+page to display
+the item details : 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: <code>Catalog</code>.java
+ </td>
+ </tr>
+ <tr>
+ <td> <code> 
+    public String showDetail(Item
+item)
+{ 
+        this.item = item; 
+        return "detail"; 
+    } 
+ </code> 
+ </td>
+ </tr>
+ </tbody>
+</table>
+ 
+The JavaServer Faces <code style="color: rgb(204, 0, 0); font-weight:
bold;">NavigationHandler</code>
+adds .xhtml to the logical outcome of the action, <code>detail</code><code style="color:
rgb(0, 102, 0); font-weight: bold;"></code> and loads
+that file. In this case, the
+JavaServer Faces implementation loads the <code style="font-weight:
bold;">detail.xhtml</code>
+page after this method returns. 
+ 
+The detail.xhtml uses the <code>outputText</code>
+component to display the <code>catalog</code>
+ManagedBean's <code>item</code>
+properties: 
+ 
+<table class="examplecode" border="1" cellpadding="2" cellspacing="0">
+ <tbody>
+ <tr class="bg-white">
+ <td>Code Sample from: detail.xhtml</td>
+ </tr>
+ <tr>
+ <td> <code> 
+   
+<h:outputText
+value="#{catalog.item.name}"
+title="Name" /> 
+   
+<h:outputText value="#{catalog.item.description}"
+title="Description"/> 
+    <h:graphicImage library="images"
+name="#{catalog.item.imageurl}" title="Imageurl" /></code><code> 
+   
+<h:outputText value="#{</code><code>catalog</code><code>.item.price}"
+title="Price" /> 
+   
+<h:outputText
value="#{</code><code>catalog</code><code>.item.address.city}"
+title="Address" /> 
+   
+<h:outputText
value="#{</code><code>catalog</code><code>.item.contactinfo.email}"
+title="Address"/>
+  </code> 
+ 
+ </td>
+ </tr>
+ </tbody>
+</table>
+ 
+<div style="margin-left: 5px;">
+ <img alt="" style="width: 782px; height: 759px;"
src="README_files/showdetail.jpg"> 
+</div>
+ 
+ 
+<h3><a href="/alexismp/entry/lightweight_glassfish">GlassFish
+v3 is a lightweight server</a></h3>
+<ul>
+ <li>OSGi-based; Embedded API; RESTful admin API; Lightweight and fast
+startup; </li>
+ <li>iterative development cycle "edit-save-refresh browser":
+ <ul>
+ <li>Incremental compile of all JSF 2.0 artifacts when you save. </li>
+ </ul>
+ <ul>
+ <li>Auto-deploy of all web or Java EE 6 artifacts</li>
+ </ul>
+ </li>
+ <li>Session retention: maintain sessions across
+re-deployments</li>
+</ul>
+ 
+ 
+Conclusion 
+This concludes the sample application which demonstrates a pet catalog
+web application which uses Java EE 6, GlassFish v3 and MySQL. 
+ 
+ 
+ 
+<h2 style="margin-left: 40px;">For more information see the following
+resources:</h2>
+<ul>
+ <li><a href="/enterprisetechtips/entry/a_sampling_of_ejb_3">A
+Sampling of EJB 3.1</a></li>
+ <li><a href="http://java.sun.com/javaee/technologies/javaee6.jsp";>Java
+EE 6 Technologies</a> 
+ </li>
+ <li><a href="https://javaserverfaces.dev.java.net/";>JSF 2.0 Home page
+Project Mojarra</a></li>
+ <li><a href="http://java.sun.com/javaee/javaserverfaces/";>SDN
+JavaServer Faces Page</a> 
+ </li>
+ <li><a
href="http://www.ibm.com/developerworks/java/library/j-jsf2fu1/index.html";>JSF
+2 fu, Part 1: Streamline Web application development</a></li>
+ <li><a
href="/enterprisetechtips/entry/true_abstraction_composite_ui_components">Composite
+UI Components in JSF 2.0</a> 
+ </li>
+ <li><a
href="http://java.sun.com/javaee/6/docs/firstcup/doc/p5.html";>Creating
+Your First Java EE 6 Application</a></li>
+ <li><a href="http://weblogs.java.net/blog/rogerk/";>Roger Kitain's
+Blog (co-spec lead for JSF 2.0)</a></li>
+ <li><a href="http://weblogs.java.net/blog/edburns/";>Ed Burns's Blog
+(co-spec lead for JSF 2.0)</a></li>
+ <li><a
href="http://weblogs.java.net/blog/cayhorstmann/archive/2009/07/say_sayonara_to_1.html";>Cay
+Horstmann's Blog: JSF 2.0 specifying parameters in method expressions</a> 
+ </li>
+ <li><a
href="http://refcardz.dzone.com/refcardz/javaserver-faces-20";>JavaServer
+Faces 2.0 Ref Card</a> 
+ </li>
+ <li><a href="http://weblogs.java.net/blog/driscoll/";>Jim Driscoll's
+Blog</a></li>
+ <li><a href="/alexismp/entry/lightweight_glassfish">Top
+reasons why GlassFish v3 is a lightweight server</a></li>
+ <li><a
href="http://java.dzone.com/articles/what-you-can-expect-from-glass";>What
+You Can Expect From GlassFish v3</a></li>
+ <li><a href="http://www.apress.com/book/view/1430219548";>Beginning
+Java™ EE 6 Platform with GlassFish™ 3: From Novice to
Professional Book</a> 
+ </li>
+</ul>
+ 
+ 
+ 
+
+</body></html>
\ No newline at end of file
Index: NB68/catalog/nbproject/project.properties
===================================================================
--- NB68/catalog/nbproject/project.properties (revision 0)
+++ NB68/catalog/nbproject/project.properties (revision 69)
@@ -0,0 +1,71 @@
+build.classes.dir=${build.web.dir}/WEB-INF/classes
+build.classes.excludes=**/*.java,**/*.form
+build.dir=build
+build.generated.dir=${build.dir}/generated
+build.generated.sources.dir=${build.dir}/generated-sources
+build.test.classes.dir=${build.dir}/test/classes
+build.test.results.dir=
[truncated due to length]

[netbeans-samples~samples:69] (Commit message missing)	ondrej58	09/16/2009

[netbeans-samples~samples:69] (Commit message missing)

ondrej58

09/16/2009