2. Introduction
• The Western Kentucky University travel forms web
page is designed to run on the departmental server
and to allow three different categories of user’s,
• Faculties can access the search, view, edit and add page
of their respective travel request data forms from the
database.
• Approver can access the search, view and approve the
data from the database page.
• Administrators can access the admin page to maintain
the database and it consists of all the required
functions.
3. Scope
• The main aim of this project is to automate
the submission of travel authorization process
and avoid the existing method of e-mail
submission. This will probably save employees
time and e-mail space.
4. Technology Used
• Adobe Dreamweaver
• HTML
• JSP
• MySQL
• UMLet version 10 http://www.umlet.com/
• Eclipse IDE
• Hibernate http://www.hibernate.org/6.html.
6. Hibernates to database access
• Hibernate layer resides in your JVM.
• Improves performance
– objects are cached in JVM and mapped to your
object model.
• Used in commercial applications
– JBoss for one (yes, another open source…)
– Many more opensource and commercial listed at:
http://www.hibernate.org/27.html
7. Importance of DAO
• DAO: Data Access Objects – design/pattern
• Purpose is to abstract your calls to the
database.
– Don't put SQL directly into your Java/JSP.
• You can change our database with minimal
affect on your code
• Identify bottle necks and bugs easier.
8. Comparison to SQL
• Problem with SQL
– never lived up to promise of standardization amongst
database vendors
– Uses Jdbc to access database – (no forced design)
– Is Relational
• With Hibernate:
– Caching
– Easier to code
– Standard access
– Is Object Oriented and maps to Relational.
9. Future work
• Proper implementation of hibernates mapping
• Using LDAP authentication
