The classics of the cultivation of Java EE

Java EE no classics, because the Java EE has been like surging river, innovation, and high-speed development, this is a leading us to the future technology. Of course, how to be in such a momentum such as the rainbow is not lost in the direction of the guidance of the relevant guide books. This article will recommend the Java-EE books from two aspects of thread and mode, these two aspects are just two different directions, the thread is from the micro, the underlying mechanism, and the pattern is from the design height to see the Java EE.

Threads (thread)

First of all, the thread is a lot of Java-ee beginners easy to ignore a basic knowledge, you can say, no matter what door in the world you are from a gate into the EE, threading is the way.

I can't remember where I saw the following paragraph in English:

In the past, only courageous programmers have dared to use pthread and Win32 threads, and modern languages such as Java are trying to save us by writing some scary applications such as parallel computing.

Java EE's servlet and EJB ensure that we don't have to worry about threads and synchronization, as long as we're programming as usual, the container automatically uses technology like thread pools to support our applications.

This shows that the thread is the most basic underlying mechanism of Java EE, each servlet/jsp program is actually a piece of thread programs, if you do not know how threading/multithreading some of the principles, how to skillfully control the servlet/jsp of Java EE?

There is a lot of authority in online computing, and Dou Lee is undoubtedly an outstanding representative of this, his parallel computing package has been added to the latest JDK1.5 version, his books are the cornerstone of the nature, but such books may not be suitable for just want to understand the threads of the Java beginners.

Java threading Programming (Java thread programming)

I recommended the first one about the Java EE book, in this book, the author in a simple example, from a single thread to explain to multithreading, thread pool (thread pool), concurrent access to objects and variables (Concurrent access to Objects and Variables), these are the places where we often have doubts in our usual servlet/jsp programming, and in the case of this book, the author clearly demonstrates these details and has important techniques. At the same time, let us deeply understand the direct production of multi-threaded applications is a "scary" thing.

Interestingly, I also found a post in the online bookstore community that I had the same opinion about, calling the book "a book to make the classics a thing of the past."

Design Patterns

Thread world is like the microbial world, complex and almost no boundary, as the information system programmer if too attached to such a pure technology micro-level, may waste too much valuable time and energy, in the basic grasp of multithreaded mechanism, need to pay more attention to the design of Java EE application.

Java EE is a unique framework or standard in the Java world, so we first need to master java-based design applications, these design application techniques are the forerunners through long-term practice summed up the experience, they called design patterns. In the application of Java EE, only a large number of use of design patterns, in order to embody the highest purpose of separation and decoupling, in order to make their own Java-EE system context clear, hierarchical, such a system really has a good scalability, strong robustness and convenient maintainability.

GoF 23 Design Patterns have become classic, 2002 I in my website J Road published 23 Design Patterns Java detailed explanation, unexpectedly in Chinese Google is difficult to find this information, which I am very surprised, perhaps the people are really very real, only to the algorithm, data structure and so on See, Touch the concept of interest, in fact, I have repeatedly told others: design pattern is not pure abstract concept, it is a summary of practice, like UML, is a communication and coding implementation of the language.

In 2002 years, I bought the Chinese version of the GOF 23 design models: Design mode: The basis of reusable object-oriented software, it is the 2nd time in December 2000, the printed version, so that the classics must read books, 8,000 volumes in 2 years have not sold out, compared to those noisy hype books, In the publication within a few months of sales, more and more appear to us the impetuous and quick success of society.

Of course, although this thin book by the four of people to help translate, presumably they also think about the worst, do their best, but there are still many translation defects in the book, affecting its sales.

Because this classic GOF design mode is more difficult to understand, beginners should be more from the example application to understand and master the Gof design pattern, related to provide examples of the application of the following books:

Mark Grand's patterns in Java series;

"Java and model" of Chinese-American Shanhong;

The author's "Java Practical system Development Guide";

Ejb

EJB is an important part of Java EE, it is recommended to put your business function core in EJB implementation, EJB is similar to the Ken's "family Bucket", the actual needs of the basic functions are packaged together, if you are a critical or personalized customer, I think you may not be satisfied with the "family bucket."

Whether the "whole family bucket" fits you, it's a necessary process to know what it's loaded with. Mastering EJBS requires two things: the basics and how to use them.

"Proficient in EJB (second edition)"

is a more thorough explanation of the EJB principle, but the book will be some of the essential principles of EJB to the CORBA, but not a detailed introduction to CORBA, I think beginners should stop here, if you are very interested in EJB low-level implementation, I recommend reading JBoss source code, In fact, the JBoss source code in your tireless study of the strength of the attack will soon fall apart.

Object pool, RMI, and transaction mechanisms should be the EJB principle to master Three directions, these three technical directions can also recommend a lot of books for study research, here is not said.

EJB is mainly divided into EJB container and EJB application system, beginners more attention should focus on how to build EJB application system, because the EJB provides powerful and very characteristic, therefore, uses them to be very careful, follows certain premise and the rule, thus, the EJB design pattern cannot be understood.

The EJB design pattern (post-note: http://www.javafan.net/softview.jsp?ID=69) is a classic in this regard, and in the book, the authors point out the use of CMP attention features, the importance of DAO patterns, and variants of the DTO pattern. Reading this book at the same time, if you refer to Sun's Petstore source learning, will have a multiplier effect,

After reading the above two books, hands-on practice is very important, EJB use of EJB Reference configuration is more cumbersome, the principle is this: the caller----> EJB Reference---> The jndi name of the invoked EJB----> called EJB , these details can only be encountered in practice, but also from the Internet to find some examples of electronic tutorials on this.

Only one or two EJB instances have been debugged before you can stand out and express your thoughts: do you like it or not? Structure selection can also provide a reference: is it lightweight or weight type? Two extreme views, such as blindly rejecting ejbs or thinking of EJB as the only solution, are undesirable, and all roads lead to Rome, and scalability and performance are key.

Here is a book that looks at EJB/J2EE from a purely design perspective: Rod Johnson's "Java EE Programming Guide", English is expert one-on-one Java design and Development,rod Johnson points out the EJB flaw in the book from a perfect design point of view, which he identifies with a bold, eye-catching, and is an understatement to use if the extra work that is done without EJB is marked with a normal small font. Of course, Rod Johnson, in order to implement its ideal design as code, hosted the spring Framework development, if the Java EE field has a perfect design requirements, but also to support the mature application, but also the industry standards, it is a very desirable thing, The spring framework has at least made useful explorations in this regard.

Clustering, Web services, and resource consolidation

For medium and large software systems, clustering and Web services are essential technologies, and there are few books available. How to integrate the new technology and existing resources, also belong to an exploratory field, look forward to these several aspects have good books come out.