Documente Academic
Documente Profesional
Documente Cultură
html
consult the Release Notes and FAQs for known problems and workarounds. For detailed information about the
supported servers and Java EE platform, see the Release Notes.
Support
FAQs
Designing the Home Page Sun Microsystems Support Plans
You begin by building a home page that includes the Tree component and the TRIP database table. The following
figure shows the page.
More
Contribute Documentation!
Docs for Earlier Releases
1. Create a new Visual Web JSF application project, name it DatabaseTree, and enable the Visual Web
JavaServer Faces framework.
2. From the Basic section of the Palette, drag a Tree component onto the Page, type Travel Information, and
press Enter. In the Properties window, set the id property to displayTree and the clientSide property to
True.
When clientSide is True, every child node (expanded or not) is sent to the client, but is not made visible
unless the parent node is expanded. When clientSide is False, only the child nodes of the expanded parent
nodes are rendered.
3. Select Tree Node 1, right-click, and choose Delete from the pop-up menu.
For this application, you do not need the initial tree node that the IDE creates because you are populating the
tree programmatically. If you do not remove the node, the values set in the JSP tag attributes take precedence
over the runtime settings, and the page displays the node.
4. Drag a Message Group component from the Palette onto an out-of-the-way place on the page, such as the
1. Open the Services window, expand the Databases node and verify that the Travel database is connected.
If the jdbc node for the TRAVEL database's badge is broken and you cannot expand the node, the IDE is not
connected to the database. To connect to the TRAVEL database, right-click the jdbc node for TRAVEL and
choose Connect from the pop-up menu. If the Connect dialog box appears, enter travel for the Password,
select Remember Password During This Session, and click OK.
Note: If you are using Apache Tomcat, copy the derbyClient.jar file to the
<tomcat_install>/common/lib directory before you try to connect to the database.
2. Expand the jdbc node for the TRAVEL database, then expand the Tables node as seen in the following figure.
4. In the Navigator window, expand the SessionBean1 node, right-click the tripRowSet node, and choose Edit SQL
Statement.
The Query Editor appears in the editing area, with a TRIP table diagram.
5. From the Services window, drag the Travel > Tables > PERSON node and drop it next to the Trip table diagram
in the Query Editor, as shown in Figure 3.
Another table diagram appears with a link, or join, between the two table diagrams.
7. In the Design Grid of the Query Editor, find the NAME row for the TRAVEL.PERSON table. Click in the Sort Type
cell and choose Ascending from the drop-down list.
This action sorts the names in the database table alphabetically by last name.
8. Find the DEPDATE row for the TRAVEL.TRIP table. Click in the Sort Type cell and choose Ascending from the
drop-down list.
This action sorts the trip dates from earliest date to latest date. The following figure shows the Query Editor.
1. Open Page1 so that the Navigator window is visible. In the Navigator window, right-click the RequestBean1
node and choose Edit Java Source.
2. Under the constructor public class RequestBean1 extends AbstractRequestBean, declare the
property as follows:
3. Right-click in the Java Editor and select Refactor > Encapsulate Fields.
4. In the Encapsulate Fields dialog, check the boxes to create getter and setter methods as shown in the figure
below. Make sure that the variable declaration for field visibility is private and accessor visibility public, and
click Refactor.
5. Open Page1 in the Java Editor and scroll to the prerender method. Replace the body of the prerender
method with the following code shown in bold:
if (nbrChildren == 0) {
// List of outer (person) nodes
List outerChildren = displayTree.getChildren();
// Erase previous contents
outerChildren.clear();
// List of inner (trip) nodes
List innerChildren = null;
// Execute the SQL query
tripDataProvider.refresh();
// Iterate over the rows of the result set.
// Every time we encounter a new person, add first level node.
// Add second level trip nodes to the parent person node.
boolean hasNext = tripDataProvider.cursorFirst();
while (hasNext) {
Integer newPersonId =
(Integer) tripDataProvider.getValue(
"TRIP.PERSONID");
if (!newPersonId.equals(currentPersonId)) {
currentPersonId = newPersonId;
TreeNode personNode = new TreeNode();
personNode.setId("person" + newPersonId.toString());
personNode.setText(
(String)tripDataProvider.getValue(
"PERSON.NAME"));
// If the request bean passed a person id,
// expand that person's node
personNode.setExpanded(newPersonId.equals
(expandedPersonId));
outerChildren.add(personNode);
innerChildren = personNode.getChildren();
}
This code reads the trip records, which are ordered by the personId. For every personId, the code creates a
new level-one node in the Tree. The code then creates a level-two node (nested node) for every trip associated
with that personId. Finally, the code binds the second-level trip node to the tripNode_action method, which
you create later in this section.
6. Right-click in the source and choose Fix Imports from the popup menu to fix the class not found errors. In the
Fix All Imports dialog box, ensure that java.util.List appears in the List field and click OK.
1. Open the Projects window, right-click the Web Pages node and choose New > Visual Web JSF Page from the
pop-up menu. Name the new page Trip.
2. Open the Services Window and drag the Tables > TRIP node onto the Visual Designer for the Trip page.
The Navigator window shows a tripDataProvider node in the Trip section and a tripRowSet1 node in the
SessionBean1 section.
3. In the Navigator Window, right-click the tripRowSet1 node and choose Edit SQL Statement.
4. In the Design Grid of the Query Editor, right-click any cell in the TRIPID row and choose Add Query Criteria. In
the dialog box, set the Comparison drop-down list to =Equals and select the Parameter radio button. Click OK.
You see =? in the Criteria column for TRIPID, which adds the following WHERE clause in the SQL query.
WHERE TRAVEL.TRIP.TRIPID = ?
5. Open the Trip Page in the Visual Designer. From the Basic section of the Palette, drag a Hyperlink component
on the page, type Home, and press Enter.
6. In the Properties window for the Hyperlink component, click the ellipsis button for the action property,
select hyperlink1_action from the drop-down list, and click OK.
The IDE adds the hyperlink1_action event handler to the Java source.
7. Drag a Message Group component from the Palette to the page and place it to the right of the Hyperlink
component.
8. From the Layout section of the Palette, drag a Property Sheet component onto the page. Place it below the
Hyperlink component.
The Property Sheet component provides a container for laying out the trip information. The Property Sheet
component contains a Property Sheet Section, which in turn contains a Property component.
9. Select Property Sheet Section 1. In the Properties window, set the label property to Trip Details.
Note: If the project source level is set to 1.4, the property sheet label is not updated after you change it in the
Properties window.
10. In the Outline window, expand propertySheet1 > section1 and then select the property1 node. In the
Properties window, set the label property to Departure Date: and press Enter.
11. In the Outline window, select section1, right-click, and choose Add Property from the pop-up menu. In the
Properties window, set the label property to Departure City: and press Enter.
12. Drag a Static Text component from the Palette and drop it on the property1 node in the Outline window.
The Static Text becomes a subnode of property1. The Static Text also appears in the Visual Designer.
13. Right-click the Static Text component and choose Bind to Data from the pop-up menu. If necessary, click the
Bind to Data Provider tab to bring that tab to the front. In the dialog box, select TRIP.DEPDATE in the Data
field, as shown in the following figure, and click OK.
The current date appears in the Static Text component in the Visual Designer.
14. Add a Static Text component to property2. Bind the Static Text to TRIP.DEPCITY.
Adding Code
Here you add code so that the Trip page can get the tripid stored in Page1 and Page1 can get the personid stored in
the Trip page.
1. Open the Trip page in the Java Editor and scroll to the prerender method. Add the following code (shown in
bold) so that the method gets the tripId that was stored in Page1.
if (parmTripId != null) {
Integer tripId = new Integer(parmTripId);
try {
getSessionBean1().getTripRowSet1().setObject(1, tripId);
tripDataProvider.refresh();
} catch (Exception e) {
error("Cannot display trip " + tripId);
log("Cannot display trip " + tripId, e);
}
}else {
error("No trip id specified.");
}
}
The setObject method sets the trip query's first argument to the tripId. That is, the method replaces the ? in
the query with the tripId. This query only has one argument so you only have to call setObject once. The call
to tripDataProvider1.refresh() calls CachedRowSet.release() and resets the
CachedRowSetDataProvider's cursor. It does not execute the CachesRowSet at this time.
2. Scroll to the hyperlink1_action method. Add the following code (shown in bold) to pass the personId to
Page1:
1. RIght-click anywhere in the Design view of the Visual Designer and choose Page Navigation.
2. Click the connector port on the Page1.jsp icon and drag a connector to the Trip.jsp icon.
3. Expand the Trip.jsp icon and drag a connector from the Hyperlink component to the Page1.jsp icon. The
following figure shows the page navigation setup.
4. Run the application. On the Home page, expand an traveler name and click a trip date.
The Trip page opens with details for that trip, as shown in the following figure.
5. On the Trip page, click the Home link. Note that on the Home page, the first-level node of the last trip you
selected is still expanded.
6. Continue exploring the application by expanding and contracting the first-level Tree nodes and clicking the trip
dates.
3. In the page 1 prerender method, replace the following code with the code in Code Sample 5.
tripNode.setUrl("/faces/Trip.jsp?tripId=" +
tripDataProvider.getValue("TRIP.TRIPID").toString());
ExpressionFactory exFactory =
getApplication().getExpressionFactory();
ELContext elContext =
getFacesContext().getELContext();
tripNode.setActionExpression(
exFactory.createMethodExpression(
elContext, "#{Page1.tripNode_action}",
String.class, new Class<?>[0]));
5. In the Trip page prerender() method, replace the body with the following code:
The JavaServer Faces 1.1 Tree component cannot use the getSelected method or the
getCookieSelectedTreeNode method to determine which node was selected. If users have their browser
cookies turned off, these methods will not return the correct values. Also, for browsers with the cookies turned
on, the cookie might return the wrong value the first time the user visits a page and clicks a node. If there are
leftover cookies from a previous visit, the previously selected value might be returned. Because the JavaServer
Faces 1.2 version of the Tree component does not use cookies to save the selected value, this is not an issue
for the 1.2 version.
The highlighting of Tree nodes is not cleared between sessions. If you run the program in this tutorial more
than once, the node that was selected in the last session is highlighted in the new session when the page first
opens. This problem is due to the use of cookies to transmit the selected node ID.
Summary
In this tutorial, you built a tree structure from data in a database. You built a two-page application, the first page of
which included a Tree component. You populated the first-level nodes in the Tree with names from a database, and
the second-level nodes with the trips for that person. You linked each trip on the first page to a second page, which
displayed the details for that trip.
See Also
Using Databound Components to Access a Database
Shop SiteMap About Us Contact Legal By use of this website, you agree to the NetBeans Policies and Terms of Use
Companion Powered by
Projects: