Java Reference
In-Depth Information
Figure 12-51.
Notice that the value for employeeNumber is specified as 111 followed by seven plus signs. Any guesses on what
is going on?
Do you remember that earlier we discovered that the values in the text fields were being padded with blanks? In
this case, because we bound the parameter to the RRL's employee number field, the parameter field was also padded
with spaces (+ is the URL representation of a blank space).
Because it didn't require any coding, this solution (links and parameters) was much easier to implement.
However, if there are many employees, users would have to scroll extensively to locate the desired employee number
and SelectEmp would be very “busy” visually.
So which is the best solution? Unfortunately, there is no easy answer to the “which way is best” question. Using
either technology (scripting variables vs. links and parameters) is viable. When making the decision on which
technologies/solutions to use, an organization must weigh the business need (how important is it to make the
application available) versus how important it is to carefully design the application and choose the best technology to
maximize eye appeal, performance, ease of use, code reuse, and maintainability.
Results of the Tutorial
Let's look at the results:
1.
In the TutorialsJSF project, a new package in WebContent named c12.
2.
In WebContent/c12, the following new Facelet files:
AllEmps.xhtml GetEmp.xhtml InsertEmp.xhtml
SelectEmp.xhtml UpdateEmp.xhtml
3.
Inside of Java Resources: src, three folders called:
com.ibm.faces.sdo pagecode pagecode.c12
