Author: Itabashi Azeri from: J Road
Thread
First of all, threads are a basic knowledge that J2EE beginners is easy to ignore, which can be said that no matter which door from the Java world enters J2EE, threads are the way.
I don't remember where I saw the following paragraph:
In the past, probably only courageous programmers were brave in using PThread and Win32 threads, and modern language such as Java is trying to save us in writing some fearful applications such as parallel computing.
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)
It is the first website I recommend about J2EE books. In this book, the author explains multithreaded, thread pool, concurrently access objects and variables simultaneously with simple examples, image easy to understand, simultaneously access objects and variables simultaneously (Concurrent Access to Objects and variables, these are where we often happen in the usual servlet / JSP programming. 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"
Design Patterns
The thread world is like the microbial world, complicated and almost no boundary, as a programmer of the information system, if it is too persistent to the micro-level of pure technology, it may waste too much valuable time and energy, after basic mastering multithreading mechanism, need more Focus on J2EE design application.
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 model in 2002: "Design mode: can be used for object-oriented software", which is the second print version of December 2000, so classic must read books, 8,000 books have not been sold in 2 years, compared to those who are hustle and hype, sell over 10,000, more and more likely, the impetuousness of our society is very good. 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 example applications, and the books for providing examples have the following:
Mark Grand's Patterns in Java Series;
"Java and Mode" of American Chinese 阎 Hong;
The author's "Java Practical System Development Guide";
EJB
EJB is an important part of J2EE. J2EE recommends the core of your business function in EJB, EJB is similar to the "full-family bucket" of Kensate, will be packaged together in the actual basic functionality, if you are a Pastest or personalized customers, I think you may not only be satisfied with "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.
"Excellent EJB (Second Edition)" (followed: http://www.javafan.net/softview.jsp? Id = 110)
It is relatively thorough to the principle of EJB, but the book will push some essential principles in the book to CORBA, and there is no careful introduction to CORBA. I think beginners should be able to be able to stop here. If you are very interested in the bottom floor of EJB, I It is recommended to read JBoss source code. In fact, JBoss source code will soon dislocation under the attack of your tirelessly drilled.
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.
"EJB design mode" (followed by: http://www.javafafan.net/softview.jsp? Id = 69) is the classic of this area, in the book, the author points out the characteristics of using CMP, DAO mode Importance, DTO mode variant, etc. While reading this book, if you refer to Sun's PetStore source code, you will have a half-time effect.
After reading the two books above, it is very important to practice. EJB is in use with the EJB Reference configuration. The principle is this: the caller ----> EJB Reference ---> Call EJB JNDi Name --- -> Call EJB, these details can only be encountered when using problems, or you can find some electronic tutorial instances in this area.
Only one or two EJB instances are commissioned, then you can stand out to express your idea: I like or don't like it? References can also be provided when architecture selection: Is it lightweight or heavyweight? Blind exclusion EJB or believes that EJB is the only solution and other two extreme views. It is necessary, and the strip main roads are key, telescopic and performance are key. Here is a book from a pure design angle: Rod Johnson's "J2EE Design Development Programming Guide", English is Expert One-ONE J2EE DESIGN DEVELOPMENT, Rod Johnson from a perfect design angle It is pointed out that the shortcomings of EJB, these shortcomings, he is using the black body logo, very eye-catching, while he will use the normal small font to use the normal small font to use the extra workload of EJB, it is easy to write. Of course, Rod Johnson hosted the Spring Framework Development in order to implement its ideal design as code, if there is a J2EE field has a perfect design requirement, but also supports mature applications, and it is an industry standard. What is it? What year is yearning, the Spring framework has been a useful exploration in this regard.
Cluster, web service and resource integration
For medium-sized software systems, clusters and web services are required to master, there are not many books. How to integrate J2EE new technologies and existing resources, also belong to an exploratory area, and look forward to having a good book in these aspects.
