Applied Software Engineering Using Apache Jakarta Commons

Applied Software Engineering Using Apache Jakarta Commons

Chapter 1 - Introduction
Chapter 2 - Four-and-a-Half Levels of Granularization
Chapter 3 - Instantiating Objects
Chapter 4 - Scalability
Chapter 5 - Serialization of Java Objects
Chapter 6 - Messages and Asynchronous Processing
Chapter 7 - Collections and Searching for Objects
Chapter 8 - Configuration and Logging
Chapter 9 - Computer Algorithms
Chapter 10 - Distributed Internet Services
Chapter 11 - Project Management
Appendix A - Making Decisions Quantifiable
Appendix B - About the CD-ROM
Appendix C - The GNU General Public License (GPL)
List of Figures
List of Tables
List of Listings
List of Sidebars

---

Apache and many people will associate the name with a Web Server. Maybe some will associate Apache with other projects. What few do is associate Apache as an organization that helps developers create Open Source products. At the highest level is the Apache Software Foundation (ASF); below that are individual projects like the Apache Web Server, Extensible Markup Language (XML), and Jakarta.

The Jakarta and XML projects contain a number of Java-based projects, which include Web Servers, XML processors, and other useful solutions. Many of these solutions share components that allow you to do common things like logging, class instantiation, and serialization. Those common components are called the Commons, which is the focus of this book.

The Commons are reusable components created through using experience, not abstract thinking. When a developer wants to create a component, he typically evaluates the need, comes up with a design, and then implements it. The problem with this approach is that it may or may not solve the needs of the developer who is using the components. Another problem is that there are many different frameworks that do this. The difference between other frameworks and Commons components is that components from the Commons are based on experience and need.