Expert ont on one EE development without EJB notes

Expert ont on one EE development without EJB
Author: Rod Johnson
Recommended book: Expert one on one EE Design and development
Martin Fowler "Patterns of Enterprise application Architecture"
Gang of Four's "design Model"
"Core java Patterns"
Recommended Sites: Theserverside
Artima.com
Core Java EE patterns website
Chapter One: Why "without EJB", summing up a sentence, in the framework without the need for distributed support, EJB over-design disadvantage
Distributed and RMI support is not necessary for most Java EE applications, but developers must provide support code for these requirements
Software Design principles:
Simple
"We should minimize the complexity of the architecture and support only realistic (and reasonably predictable) needs, and do not attempt to advance
Take into account all the problems, but in order to be simple, it is necessary to pay more attention to the design quality of the architecture to ensure the future
The ability to refactor it so that it can cope with more complex requirements. Refactoring the architecture is not as simple as refactoring the code, but since we
If you do not want to be forced to modify a lot of code when faced with new requirements, you must focus on refactoring the architecture "
High yield: the weaknesses of EJBS
Object-Oriented Oo
"OO design is more important than specific technologies such as Java EE, and we should try to avoid making technical choices (such as Java EE) from interfering
We use the "
Business needs first
Attach importance to the experience process
Attention to Testability

Expert ont on one EE development without EJB notes