Author(s) : Dhrubojyoti Kayal Publisher : Apress Date       : 2008 Pages     : 345 Format    : PDF ISBN-13  : 9781430210108

About the Author
DHRUBOJYOTI KAYAL is an agile developer architect with almost a decade of experience working with Java EE. During this time, he has actively contributed to the architecture, design, and development of products and applications using enterprise Java technologies. His areas of interest include the Spring Framework, JBoss SEAM, OSGi, refactoring and prefactoring, rich Internet applications, Scrum, and XP. He currently works with Capgemini Consulting, where he helps project teams with the architecture, design, and development of Java EE projects for leading vendors in the telecom, media, and entertainment sectors. Prior to Capgemini, Dhrubojyoti worked for TATA Consultancy Services, Oracle, and Cognizant Technology Solutions.

Download Link

Author(s) : Joseph D. Gradecki, Nicholas Lesiecki Publisher : Wiley Publishing, Inc. Date        : 459 Pages      : 2003 Format    : PDF ISBN       : 0471431044

Most applications, particularly enterprise-level applications, are not one module of code that exists in a single file. Applications are collections of modules that work together to provide some desired functionality defined by a set of requirements. Theoretically, developers can create modules that contain discrete functions; so a security module and a login module might be combined with an HTTP module to create a Web server application. Due to the nature of object-oriented tools and languages, however, this ideal of modular programming is seldom realized. Instead, developers are often forced to create modules that have mixed goals; a single function such as logging in a user might actually be distributed among several modules in an application. This is the case with the Apache Web server, for example; 37 of its 43 modules contain code that handles user login. This practice leads to tangled code that is more prone to errors and is difficult to debug, refactor, document, and support. The goal of aspect-oriented programming (AOP) is to solve these types of development problems. AOP emphasizes the creation of aspects, which are modules that centralize distributed functionality. To put AOP theory into practice, the Palo Alto Research Center (PARC) created AspectJ. AspectJ is an open-source language that functions as an extension to Java. AspectJ is 100- percent compatible with Java: AspectJ’s aspects work side by side with Java classes to deliver a comprehensive application. Benefits of using AspectJ with Java include:
     * Less tangled code
     * Shorter code
     * Easier application maintenance and evolution
     * Applications that are easier to debug, refactor, and modify
     * Code that is more reusable—developers can create libraries of aspects in much the same way they already create libraries of objects in OOP

Download Link