This project has the exact same requirement as Project 0. The difference is that we need to implement it using Java EE rather than Perl.

The (highly readable) authoritative documents on Servlets and JSP are posted under Resources along with their APIs. Also posted is a tutorial and a link to a site with JEE highlights.

See the page of Project 0.

The same variations listed in Project 0 apply as-is to this project. In addition, the following enhancements over our reference implementation (posted as Proj1B.war are to be explored:

• Persist the webapp data when the controller is destroyed and load it when it starts. Be careful not to mix concerns; specifically: saving data is the concern of the model; the name of the file is the concern of the end-user; the path leading to the file is environmental and is therefore the concern of the controller.

• Migrate messages (such as Cannot be Blanck) from the controller to the view.

• Make one error message appear in red and the other in blue.

• Reset the user's count if the user remained idle for 1 minute, i.e. even if the session has not expired.

• Send an error message if the used URL includes the string “York” (case insensitive), e.g. /york.do. Ideally, set some unuser HTTP error status code and have web.xml auto serve an error page (see the <error-page> tag in web.xml).

The following two variations require filters and listeners:

• If a client managed to enter over five countries within a session, flag it as a “Power User” and post its IP at the top of each served page.

• Inject a new validation rule: “countries less than three characters are not allowed during lunch hour”