J2EE is actually there is no four books, because J2EE has always been a raging Dajiang, innovation, continuous development, this is a technology leading us to the future. Of course, how to get the guidance of the relevant guidelines in this momentum of the trend of the shallow trend. This article will recommend J2EE books from both a thread and mode. Both of these are just two different directions, and threads start from microscopic, underlying mechanisms; and mode is from design heights to see J2EE. Thread first, thread is a basic knowledge that J2EE beginners is easy to ignore, can be said, no matter which door from the Java world enters J2EE, threads will pass. I don't remember where I saw a paragraph of English: In the past, probably only courageous programmers were brave in using PThread and Win32 threads, modern language such as Java is trying to save some fearful applications such as parallel computing, etc. we. J2EE's servlet and ejb ensure that we don't have to worry about threads and synchronization, we will use technology such as thread pools to support our applications. It can be seen that the thread is the most basic underlying mechanism of J2EE. Each servlet / JSP program is actually a thread program. If you don't know how to thread / multi-threaded principle, how can I protect J2EE's servlet / jsp? There are many authorities in thread calculations, Dou Lee is undoubtedly the outstanding representative of this area, his parallel computing package has joined the latest JDK1.5 version, his books belong to the foundation, but this book may not be very suitable. J2EE beginners who only understand threads. "Java Thread Programming] http://www.china-pub.com/computers/common/info.asp?id=15888 is the first letter I recommend about J2EE books, in this book, With simple examples, the image is easy to understand from a single-thread, thread pool, concurrent access object and variable simultaneously, these are our usual servlet / JSP programming Where you often happen, in this book, the author clearly shows us these details and important technologies. At the same time, we also let us fully understand the direct multithreading application is a "fear" thing. That is very interesting, I also found a post with me in an online bookstore community, saying that this book is "a book that makes the classic" (http://www.china-pub.com /computers/bbs/addfolow.asp?id=22869&rootid=2&banidid=1). The design mode thread world is like a microbial world, complicated and almost no boundary, as a programmer of the information system, if it is too strong in such pure technology, it may waste too much valuable time and energy, after basic mastering multi-thread mechanism, Need more attention to J2EE design applications. J2EE is a unique framework or standard in the Java world, so we first need to master Java-based design applications, these design and application skills, the forerunners have been summarized by long-term practices, they call it design model.
In J2EE applications, only a large number of design patterns can reflect the highest tenet of separation and decoupling, in order to make their J2EE system clamps, distinct, such systems really have good scalability, robust robustness And convenient maintainability. GOF 23 design model has become a classic. In 2002, I published 23 design patterns Java in my website. It was hard to find this information in Chinese Google, which made me very surprised, maybe the Chinese is indeed Very real, only to the algorithm, data structure, etc., I am interested in the concept, in fact, I have been repeated and others: design mode is not pure abstract concept, it is a summary of practice, like UML, is a AC and encoding the language. I bought the Chinese version of GOF 23 design mode in 2002: "Design mode: can be used for object-oriented software" (http://www.china-pub.com/computers/common/info.asp Id = 684), is the second print version of December 2000, so classic must be read, 8,000 books have not sold it in 2 years, compared to those who are hustle-oriented, in the publication of several months The internal sales is over 10,000, and the more impetuous and urgent work in our society. Of course, although this thin book helps translators by four Chinese people, they must be thinking about it, but they have made the biggest efforts, but there are many translators in the book, affecting its sales. Since this classic GOF design pattern is more difficult, beginners should be more about understanding and mastering GOF design patterns from instance applications, and the books for providing examples have the following: Mark Grand Patterns in Java Series; American Chinese "Java and Mode"; the author's "Java Practical System Development Guide"; EJB EJB is an important part of J2EE, J2EE recommends putting your business function in EJB, EJB is similar to Ken "Full Buy", pack the basic functions required in the actual need, if you are a picky or personalized customer, I think you may not only be just in "full-family bucket." Regardless of whether "full bucket" is right, understand what it is in it is a necessary process. Mastering EJB needs to start from two aspects: basic principles and how to use. "Jing EJB (Second Edition)" (http://www.huachu.com.cn/itbook/itbookinfo.c?lbbh=bb07629881) is a relatively thorough explanation of EJB principles, but the book will push some essential principles Give CORBA, and didn't have a careful introduction to CORBA. I think beginners should be able to stop here. If you are very interested in the bottom floor of EJB, I recommend reading JBoss source code, in fact, JBoss source code is under the attack of your tirelessly Soon will soon. Object pool, RMI and transaction mechanism should be the three directions of EJB. These three technical directions can recommend a lot of books for learning research, and they will not say it here. EJB is mainly divided into EJB containers and EJB applications. Beginners should pay more attention to how to build an EJB application system, because EJB provides powerful and very characteristic, so use them to be very careful, follow certain premise and rules, thereby , EJB design mode can't not understand.
