This is a J2EE project practice, spending me a year.
Technology Architecture
JSP -> Serverlet -> SessionBean -> Dao -> Database
There is no existing frame, but the thoughts are similar.
Care to be a luxury:
The JSP page of the front desk is highly reused, all button tips, page layout, buttons method and point to all are dynamic, from academic management (semester management, course directory management, teacher student management, class schedule, teaching task) ...), teacher function (personal teaching task, student grades) ..), student function (personal curriculum plan, personal selection plan, personal class, grade view.) All functions are only used in the front desk JSP page. In the case of the entity's query page, the great space left in the business process and the enhancement of the function.
Can improve:
There are too many Serverlets in the front desk, without a unified main serverlet management, you can use Struts to solve this problem.
The EJB of the background is used in the design, and there is no object-oriented mechanism in the design, so access or forms a table operation, you can use Hibernate to solve this problem.
