Four Books and five classics of J2EE

Every time I see the word "four books and five classics", my mind always comes up with the famous saying: "There are too many articles except the four books, is it true that I am the only one?" The term "fabricated" refers to the so-called "pseudosutra" explained by later scholars by Confucius and Mencius ". Under such a title, most of the books I want to recommend today are explanations of J2EE by others. A well-rounded title makes me write a paradox of speech. However, for a technology that has been around for seven years and is about to be upgraded (the Enterprise Java of the next version will be renamed javaee), I believe that what readers need is no longer an entry-level teaching material, it's about "how to use it to develop real applications. This article will provide readers with several J2EE best practices from different perspectives, hoping that they will help readers who are familiar with Java programming but lack understanding of J2EE to draw a tour map of this huge world.

J2EE Core Model (version 2)

Core J2EE patterns (2ndEdition), Deepak Alur, translated by Liu tianbei, Mechanical Industry Press, May 2005

The preface made by the translator for this book is straightforward enough: "If all the previous tutorials are about the 'content' elements in J2EE development-that is, to teach us what to do, this book focuses on the 'form' element here, which is how to do it to develop an efficient and elegant J2EE system. What you have learned from this is not just the 'j2ee techno', but the 'how to use J2EE for design '." However, it is worth noting that the "J2EE technology" mentioned here should be more accurately described as "Sun's J2EE technology" or "Orthodox J2EE technology ", that is, "EJB-based J2EE technology ". For some reason (please allow me to sell a bit), this type of J2EE technology presents great complexity, so the solution in the book (that is, "Mode ") it often presents awesome skills. My suggestion for this book is that readers should keep in mind each of these solutions and their reverence for these solutions, which will help you fully understand the value of the next book.

Expert one-on-one J2EE development without EJB
Rod Johnson, translated by javaeye, Electronics Industry Press, August 2005

Uncover the foreshadowing: the "Orthodox" J2EE is so complicated, largely because of the existence of EJB. As a developer with ten years of Java experience and longer enterprise application development experience, Rod Johnson firmly believes that there are indeed many less complex problems in the world, finding a less complex solution for these problems is what he (and his spring framework) hopes to achieve. The beauty of this J2EE development without EJB is that it not only points out the problem of EJB, I have elaborated on a complete and self-consistent Java Enterprise Application Architecture of "without EJB". The Information System of Walmart, the world's largest supermarket chain, was built on this architecture, this fact proves the legitimacy of the architecture. I recommend this book after the J2EE Core model because I am worried that readers will no longer be interested in reading the previous book after reading J2EE development without EJB, thus, we missed an opportunity to fully understand the EJB technology.

Even more commendable, Rod Johnson does not try to claim that his solution is a perfect method for Java Enterprise applications. Throughout the book, readers can feel that Johnson most wishes to convey to readers a "evidence-based architecture" method based on practice. If this book has its unique merits, I think it is not because it promotes IOC or AOP, but because it helps some readers break through the technical knowledge, learn to select an architecture based on your needs and practices.

Enterprise Application Architecture Model

Patterns of enterprise application architecture, translated by Martin Fowler, Wang huaimin, Mechanical Industry Press, July 2004

After reading the first two books, the readers will probably be able to understand the common technologies, Problems and Solutions of J2EE, and then Martin Fowler will be the first to appear. Fowler is a technical missionary who is good at summing up others' experience. This poeaa is one of his typical works: no original materials, however, many ancient technologies have been deeply analyzed and elaborated. How much is its value? You just need to look at the J2EE Core Model, J2EE development without EJB, and. NET Enterprise Solution Model, a kind of good books can know how frequently they reference the content.

The disadvantages of this poeaa book-the same as many other models-are too "formal": There is a lack of more practical examples, and the list and elaboration of 47 models seem a bit cool, the answer to the question "when to use/do not use a certain mode" is very difficult. However, among the books involved in this article, only this one may not require additional recommendations, it is because it is difficult for you to read this poeaa once and again when someone quotes a word like "unit of work" or "transaction script" without explanation in an article or conversation.

Enterprise integration patterns

Gregor hohpe, etc., Addison-Wesley, January 1, October 2003 (no Chinese translation yet)

This book has a deep heart: "If someone tells you that enterprise application integration is a very easy task, this person is either wise or stupid, or for commercial reasons, you may want to trust something that he is about to sell." For most Java programmers who are used to object-oriented programming, it is a nightmare to enable enterprise application integration (EAI) that is full of asynchronous/cross-process calls; in the early information-based institutions such as banks and insurance, the demand for EAI is just as common. The tension between the two makes this book-in some particular cases, for some specific people-as if it were like sounds of heaven. In a sense, this book is also helpful for breaking the word Superstition: It describes "service-oriented architecture" (SOA) as one of the six application types of enterprise application integration, the application scenarios and advantages and disadvantages of various types are summarized. Martin Fowler calls it the "Sister book of poeaa" in the order it makes. From the perspective of filling in the application scenarios of a large category of enterprises not covered by poeaa, this title is worthy of the name, and the author's technology and writing are worthy of this praise.

Java Modeling in color with UML

Peter Coad, Prentice Hall, August 1, June 1999 (no Chinese translation)

The purpose of this book is to make it clear that a competent J2EE developer should have certain domain modeling capabilities. However, in terms of popularity, the recommended object should be "Analysis Mode" or "Domain Driven Design", rather than the "small book" that has almost never attracted attention in China ". Unfortunately, Martin Fowler lacks a summary of his practical experience, eric Evans's last question about how to turn a business concept into a domain model is not the least important. But fortunately, Peter Coad is a famous ghost, only in this way can we ensure that the content on the 221 page of the district is indeed something to say.

From the perspective of computer science, the more formal and recursive the method is, the more practical it is. Eric Evans's description of DDD in "Understanding needs" is very operable, several Basic meta-models proposed by Peter Coad provide extraordinary guidance for actual modeling. when most people analyze business models, peter Coad's meta-model in the field of business analysis can be seen by his "talents. As for "color-based UML", it is nothing more than an intuitive description of the meta-model. This "book" is the second-to-second best practice guide for Object-Oriented (rather than case-oriented) enterprise application business modeling.

***

As you can see, in the five books I have recommended, I have not introduced the popular monographs on Hibernate, spring, and other frameworks, nor have I talked about the books of emerging technologies such as AOP and Ajax. J2EE is a practical field, especially in today's mature world. It may be more valuable to guide "how to use it. Among my recommendations, there are many "old books" that have been published for three or five years. This may prove that the "more than Chan, more than Chan, is more than just wine, but also the accumulation of technology.