Open this "J2EE core mode", you will first pay attention to the two masters of the software methodology. After two preambles, it is then attached to a "translation". This idea is enough to ridiculously and 僭, not in Shakespeare.
After writing a script with the prince of Denmark. The judgment of the masters is unambiguous: "There is no such book, don't develop EJB." Their guarantee is enough to confirm that this book is in its aroma. It is "The J2EEBOOK).
Of course, for the majority of Chinese developers, we have already developed a large number of J2EE, and even EJB applications under the "no book". Those developing history filled with twists and turns seem to have some kind of programmer to produce some kind of confidence; in mastering a number of API details, several application servers configuration, several framework class library use method, they or open, or secretly Take yourself as a well-deserved Java corporate development expert - not, these words don't mean anything: What we want is, this book is precisely written for the above developers. This "J2EE core mode" is the maximum remedy and fulfilled. If the previous tutorials are introducing the "content" feature in J2EE development - that is, teach us "what" -, this book is concerned about "form" elements. It is "how to do" to develop an efficient, elegant J2EE system. The reader will learn from the middle, not only "J2EE technology", but "how to use J2EE technology".
In other words, if you haven't passed J2EE practice before, it will be hired in the "1 year J2EE development experience". This book does not contain the kind of knowledge that you have to swallow tonight. On the contrary, if you, The invisible "Java Enterprise Development Specialist", the pursuit of the position is "Senior Java Application System", if you expect the future, the boss will ask "How to achieve access control" tomorrow, "When to use fine-grained interface Design "" high-level "issues, then congratulations, tonight - or even in the future - you choose the readings of the lesson.
As a loyal reader of the first edition of this book, we (half a happy, half a surprised) found that this second edition in front of him constitute a new reading experience. The authors have revised technical details according to the latest J2EE technical specifications (especially EJB2.1); according to the research exchange of the model community, the authors have added several models; even some parts, discussions, examples, examples It is also completely different from the first edition; the original PSA project (first edition "Edition" one chapter) integrates the "sample code" section of the rest of the rest; and the new chapter discusses the end of the "micro-architecture". Concerns about WebService and other technologies, the in-depth discussion of various persistence programs (custom-made persistence, EJB, JDO, etc.) reflects the continued investment of the new version of this book.
Benefits from this book, here we also want to take the liberty of Chinese readers to recommend an efficient reading path: Compared with the first chapter, Chapter 5 "J2EE Mode Overview" is a more reasonable start of readers. point. Please pay particular attention to the discussion of "layering", "terminology" and mode / strategy, these are important concepts throughout the book! Second, it should be read on the Chapter 2, "Design Considering and Practices" and Chapter 3 "Business Layer Design Considering and Practice": Even if you don't plan to use any model, even if you don't care J2EE development, As long as your work is related to the distributed enterprise application system, the problems of these two chapters will be encountered sooner or later. As for each specific mode itself, we recommend readers to pay attention to the detailed "strategy" section and "design notes" that spread it. The former discussed a variety of implementation of the same model, which highlights some core concepts and considerations in specific development fields. A travel in Chinese is always a difficult trip. For the Chinese translator, "technical difficulty" is not challenged: the book discussed is the most well-known field of translators, so we can be responsible, in this Chinese translation, there is no technical details because of translation The ignorance or sparseness of the person deform or misinterpret. The principles and premise of this translation is the thorough understanding of the original text.
In fact, the difficulties encountered in the translator's work have mainly occurred in the "Tutor" level. Simply put, J2EE monographs generally face the two difficult situation of "turning, still do not turn": objects, function names, various elements in the UML chart, these contents are exposed to English, even English The propagander is probably read, so the part of the reader can understand as much as possible seems to be a reasonable approach --- After all, the development work is ultimately related to the code, and the code is definitely necessary. Out of "English". But on the other hand, the responsibility of translation is to let readers who do not have the original text can also access the work. If a large number of paragraphs (excluding sample code) are still preserved as English or "English", then readers cannot be intuitive. Get the information contained in the original text. After repeated trade-off, the solution of this translation is still compromised. We have taken the following principles in work:
First, the terminology uses general literature to translate, not self-created. For the names of each model, the name document template is the name, the name of the reconstruction method, and we refer to Li Yingjun et al. "Design mode", Xiong Festival, etc. "Refactor", etc., and some resources of the IBMDE VeloperWorks Chinese website.
Second, some common terms in this field, if this book is not performed, this book is not self-made, translated into Chinese, but retains English original words. The term term includes: applet, servlet, bean, entitybean, sessionbean, cookie, WebService, etc. According to our observation, in daily work, domestic developers have used to use the above terms in the original text. In some cases, we also clarify the usage of these terms in an annotated form.
Third, the object name in the mode is often naming according to the code style, such as "BusinessObject", "Customerto", etc. If you don't translate it completely, then many paragraphs that are flooding this kind of expression are difficult to understand. Our principle is that when a certain type of expression is first appearing in each natural segment, with parentheses, such as "BusinessObject", "Customerto", etc. I hope this practice can maintain the balance between easy-to-understand and concise.
Fourth, the sample code in the book has a considerable proportion, and the code annotation is the key to understanding these code. We translate all code notes into Chinese. For code (such as debugging information, etc.), which is displayed in the view (such as debugging information, etc.), and we have not changed to Chinese, just annotations the meaning of the output information when necessary. If the reader is more trust in the original code, you can also download from this book's official website http //www.corej2eepatterns.com/. Fifth, the original book does not contain a comment. All current annotations are translation. In the book, there is nothing in the book, and the translation is interpreted, and it is explained, make up, slightly okay. Like the above two principles, it is similar to the inner junction when the original speech --- but the translation task itself seems to be a "nozzle". In the viewer of enlightenment, sometimes the translator may not be as silent as the translator - but we can only make a picture to do nozzle without much mouth.
The original book has been completed by many people, and the multi-version revised is inevitable. The translation is revised in accordance with the latest errata in this book, and combined with reference to the first edition of this book, dozens of errors have been fixed.
(This article is the interpretation of the "J2EE Core Model" Chinese version published in March 2005, this newspaper is published in this newspaper)
