June 3, 2011, 9:44 p.m.
posted by franni
Using the Case Study in Our Book
As we discussed at the beginning of this chapter, this simple case study is complex enough that we can demonstrate the choices you can make when using it to design J2EE applications. It's not a one-object toy application, but it's not overly complicated. We'll use it in several ways as we proceed through the chapters.
Employee management (creating, removing, and updating Employees in a relational database) is a topic that we'll revisit several times so that you can learn how to understand the trade-offs that the various parts of WebSphere and J2EE give you. We'll examine a simple Employee Management System in Chapter 7, and discuss different design aspects of implementing the database access and user interface portions in Chapters 12, 13, 14, and 21. We'll also examine how to secure that part of the application in Chapter 29.
The TimeSheet entry and display portion of the case study is another rich area that we'll explore repeatedly. In Chapters 11 and 15, we'll talk about two different choices for implementing part of the Web-based user interface of the application. In Chapters 23, 24, and 25, we'll introduce how to implement database persistence in that part of the application using some of WebSphere's built-in persistence capabilities. In Chapters 30 and 31, we'll examine how to put all of the technologies together into a single whole that uses all the different pieces you've examined in the previous chapters. Other chapters will also often refer to smaller portions of the case study presented in previous chapters to illustrate the differences in alternative technologies where you have a choice between two or more options.
Later on, as you learn more about building user interfaces with J2EE and the WebSphere product family, we will show you what the user interface of our case study system will look like.