Java Reference
In-Depth Information
• Enterprise beans
• Local, no-interface-view session and singleton beans
• JAX-RS resources in a session bean
• Java EE security constraints on the administrative interface business methods
• All enterprise beans packaged within the WAR
• JavaServer Faces technology, using Facelets for the web front end
• Templating
• Composite components
• A custom formatter,
PhoneNumberFormatter
• Security constraints on the administrative interface
• AJAX-enabled Facelets components
• Custom converters for the entity classes used in the user-interface compon-
ents
The Duke's Tutoring application has two main user interfaces, both packaged within a
single WAR file:
• The main interface, for students, guardians, and staff
• The administrative interface used by the staff to manage the students and guardi-
ans, and to generate attendance reports
Apart from the main and administrative interfaces, there is a JUnit test that demonstrates
how to use the embedded EJB container to test the business logic of the session beans.
Main Interface
The main interface allows students and staff to check students in and out, and record when
students are outside at the playground.
Java Persistence API Entities Used in the Main Interface
The entities used in the main interface encapsulate data stored and manipulated by Duke's
Tutoring, and are located in the
dukestutoring.entity
package in the
dukes-
tutoring-common
project.
The
Person
entity defines attributes common to students, guardians, and administrators
tracked by the application. These attributes are the person's name and contact information,
including phone numbers and email address. The phone number and email address attrib-
utes have Bean Validation annotations to ensure that the submitted data is well-formed.
