Separation of navigation routing code in J2EE web applications

Authors:
Minmin Han;Christine Hofmeister
Affiliations:
Computer Science and Engineering Dept, Lehigh University, Bethlehem, PA;Computer Science and Engineering Dept, Lehigh University, Bethlehem, PA
Venue:
ICWE'05 Proceedings of the 5th international conference on Web Engineering
Year:
2005

Citing 6
Cited 3

Improving Web information systems with navigational patterns

WWW '99 Proceedings of the eighth international conference on World Wide Web
Separating features in source code: an exploratory study

ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Implementing distribution and persistence aspects with aspectJ

OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
An Overview of AspectJ

ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
AOP: Does It Make Sense? The Case of Concurrency and Failures

ECOOP '02 Proceedings of the 16th European Conference on Object-Oriented Programming
Tapestry in Action (In Action series)

Tapestry in Action (In Action series)

Modeling and verification of adaptive navigation in web applications

ICWE '06 Proceedings of the 6th international conference on Web engineering
Characterizing navigation maps for web applications with the NMM approach

Science of Computer Programming
Surveying navigation modelling approaches

International Journal of Computer Applications in Technology

Quantified Score

Hi-index	0.01

Visualization

Abstract

The navigation routing code of a web application is the part of the code involved in routing a request from a web page through the appropriate components on the server, typically ending with the display of a response page. Common maintenance activities are to change the sequence of pages or the processing for a page, and for these activities the navigation routing code must be located, understood, and possibly modified. But in J2EE applications this code is spread among a number of components, making maintenance costly. We describe an approach for separating this navigation routing code, using either Aspect Oriented Programming (AOP) or conventional OO techniques. We demonstrate how this improves maintainability by converting three exemplar applications from Sun and Oracle, with a 4- to 11-fold reduction in the number of files containing navigation routing code and in the lines of code in these files.