Understanding J2EE design patterns

zhaozj2021-02-11  219

Chapter II J2EE Design Mode

After we form a simple cognition of the frame, pattern. As a background knowledge, this chapter we primarily understand and understand J2EE design patterns to get the full picture of J2EE design mode. Due to the detailed introduction of the entire J2EE mode on Sun's website [i], it is not necessary. But there is a picture, according to the intrinsic requirements of this article, it must be seen. From this we will further clear the framework, mode, specific techniques (such as J2EE technology), design a relationship between applications.

[ii]

You can understand this picture:

First, it directly shows the relationship between this mode and various modes in the J2EE technical system. In the J2EE mode system to date, the modeling mode is such as such, and they are distributed at unhafficated levels of J2EE technology, interacting with each other with interaction with the interaction between the hierarchy. It is worth emphasizing that this is the J2EE mode of J2EE. The new design mode will continue to appear as practical. More interesting is that the model is classified [III] and the abstract design division method [IV], these two division methods have given the feeling of elemental cycle table, I am afraid that there will be the utility of elemental cycle table in practical practice. Promote the generation of new models.

Second, it reflects that J2EE technology is a framework software. The framework can be considered a package suitable for a certain area. This package provides a solution for various problems in the field. J2EE is a framework software that provides a set of APIs for enterprise-class computing. This framework software is reflected in something similar to workflows, a business solution order from beginning to end.

Again, it implies the flesh and blood before the framework and design mode. The frame is blood, is the skeleton, the design pattern is meat, the meat is attached to the blood and the skeleton, and there will be various design patterns in the framework. The design pattern is a fine-grained element with a state of view of the architecture, while the frame is coarse particle size. The design pattern is an important component of the support architecture. This is a building design, which requires architectural architectural design when architectural design; construction, construction rules and patterns. Under the framework of J2EE, "Elements" currently covering is 15, of course, the elements that have not been discovered are objective.

Finally, it contains the concept of application design. Essentially design a good scalable application itself is to design a framework structure. However, this framework is in another layer of frame. This is a class of frames within the J2EE technology (framework) system. We can design many frameworks suitable for more specific applications based on J2EE technology, which can be more convenient to develop and higher efficiency. In this frame, there can be several kinds, or even the design mode in all the above figure, after all, the design mode is just a brick. However, a good frame design can bring us any benefits brought by J2EE, with the features they have; the simple frame structure may be cured into a non-expandable application. In fact, there are now many open source organization's framework structures, such as Cocoon, Struts, etc. They all have different applications [V].

[i] http://java.sun.com/j2ee/boeprints/design_patterns/

[II] Image Source: http://java.sun.com/boeprints/patterns/catalog.html

[III] Classification method in "Core J2EE Patterns".

[IV] Division method of "design mode" book.

[V] Most framework structures are open source. There are thousands of open source projects on http://sourceforge.net/.

Cocoon's download address: http://xml.apache.org/cocoon

Struts download address (this framework is integrated after jbuilder8): http://jakarta.apache.org/struts

转载请注明原文地址:https://www.9cbs.com/read-3759.html

New Post(0)