Evaluating Presentation Layer Development Frameworks for EJB Applications in J2EE Architecture

Documente

Thesis

Background

For medium to large organizations, information systems play an important role for information storage and retrieval. They are used to support business processes such as decision-making. In information systems, huge amounts of data need to be manipulated and visualized. One way to handle this complexity is to use Enterprise JavaBeans (EJB) in a J2EE architecture. Since EJB are not designed to work in the Presentation Layer, suitable Presentation Layer Development frameworks where introduced to improve the infrastructure of the information systems. The MeDIC (Metric Definition Integration Calculation) system [1] and XAM (eXam Assignment and Management) system are typical representatives of such information system.

In the proposed architecture, the Data Layer and Business Logic Layer are realized by EJB. The Facade pattern realizes a simple interface for the Presentation Layer. The Presentation Layer of the two applications is currently implemented using JSP/Servlet technology. They use a Command pattern which will cause huge amount of command classes that can clutter up the design.

Nowadays, many frameworks, like Java Server Faces (JSF), Wicket, and Tapestry, exist that cover the Presentation Layer. They provide a huge variety of features and architectures. The goal of this Master Thesis is to evaluate those frameworks in the context of the two information systems, MeDIC and XAM including the current JSP/Servlet solution.

Assignment

The goal of this Master Thesis is to evaluate frameworks for the Presentation Layer of the two information systems MeDIC and XAM including the current solution (JSP/Servlet and Command pattern). The first step is to gather the requirements from the developers who implement the systems. Then analyze the requirements, select possible Presentation Layer Development frameworks, and implement prototypes. The prototypes must fulfill the requirements, and must be able to work with the current infrastructure. The frameworks should reduce the code complexity, and must be able to work with IBM Websphere Server 7.0 which is the existing system?s web server.