Excellent job showing continual progress on this via the time log and regular commits on the project. Problem statement and GitHub repository will serve you well as part of your portfolio. Good use of properties files, .gitignore, templating jsps, creating single-purpose methods and eliminating copy/paste code. Great work keeping the code neat, clean, and easily maintainable.
[x] Overall, good use of logging, watch for a few .printStackTrace(); statements that snuck in.
[ ] Have you thought about form validation?
[ ] There's opportunity for more granular testing: methods in EventBeanComparator, EventFactory and Utility package classes are just a couple examples.
[x] Bean package is very large, with some factories and other classes that are not just simple beans. How might you refactor the package structure to organize these a bit better?
[x] Remember constructors should be placed at the top of the class after instance variables and overridden constructors should call the no-arg constructor. Example where this was missed: SearchBean
[ ] What happens if there are exceptions in the application, for example a problem connecting to the database? How is the user notified of the problem, e.g. error page?
[x] In the various daos, how is the session closed?
Excellent job showing continual progress on this via the time log and regular commits on the project. Problem statement and GitHub repository will serve you well as part of your portfolio. Good use of properties files, .gitignore, templating jsps, creating single-purpose methods and eliminating copy/paste code. Great work keeping the code neat, clean, and easily maintainable.