About the scalable Web architecture design - Description files for frame structures (DOJAVA) Abstract: This article detailed the definition of description files on scalable web framework structures. And to create the Java model of the frame. The framework is characterized by: forms, form nested, view configurable, views are defined, built on the Struts framework. Pure personal idea, there may be a lot of childish, please give pointers and promotion. How to define: I have been thinking about how to define the description file of the frame structure. I will consider: 1. Integrity from the following aspects: Any case in the allowable range of the frame can be described. 2. Semanticity. All descriptions must be unique, clear. 3. Consistency. All descriptions must be unified and cannot conflict with each other. 4. Can reference nature. All description elements must be up to access, and they must be easy to access. 5. Maintainability. Description files are configurable, scalable, regenerable. 6. Readability. All descriptions must be easy to understand. Now I need such a description file: describe the framework web page, which is the web page of Frame. I analyzed the eclipse plugin description file. It is defined as:
There are four main tags in Plugin.xml: Plugin, Requires, Runtime, Extension. Where the Plugin tag provides basic information for the Welcome plug-in we have to develop, in addition to Name, Version, Provider-name, the most important thing is ID, we can index to this element by it. The Requires tab is listed in the needed plugin, here we want to use the Eclipse Workbench and SWT API, thus import the org.eclipse.ui plugin. The Runtime label is specified in the file name of the JAR package where we developed the plugin. The Extension tag is the information of the plugin extension point. Org.eclipse.ui.views is the observation window extension provided by the Eclipse system. Our example is a view window (this shows that we are going to further development in org.eclipse.ui.views extension. EXTension also includes two tags of Category and View, and declare the class name of the Welcome plugin in the properties of the View. I thought I found the baby, I was very excited! You look, how wonderful structure. The declaration of the external package, the runtime library, the extension point setting, the definition of the view. The most shining is the extension point. This means that all plugins can have the capacity of the container, and the plugin can be inserted into another plugin. The plugin itself is scalable. Frame demand: When I started to build such a Java model, I met a problem. How can I insert the plug-in view into the frame view? How can I achieve communication between the framework and the plugin, including the delivery of an event. First, explain the specific application of this framework and the techniques used. This framework is a web application. The form is configurable, it may be that the upper and lower divided are two, or the left and right is divided into two, and the form is nested. The specific views of each region of the form can also be configured, which may be a navigation bar or may be a list box. Techniques are intended to use Struts architecture, retain action, bean, view. They can help us complete some of these cumbersome work. So the container management can only be the ActionServlet container of the Struts itself or its subclass. Struts is a highly configurable, highly scalable MVC framework, which can be used to develop any web applications that can be thought of with Java technology. Each portion of the MVC mode has a correlation part in Structs. In Struts, Action is a control layer, bean is a model layer, and View is a view layer. Now let's consolidate the framework requirements so we better analyze and define the description file of the framework. 1. Forms can be configured 2. Forms Nested 3. View Configurable 4. View can be defined 5. Built on the Struts framework: Ok, now I know what we need to do. Our description files need to include the following elements: 1. Form Description 2. Extended Point Description 3. ANtion is associated with the view description, because Struts has associated action. So we only need to manage Action. The definition of the view is handed over to Struts. The description file formed is as follows: / * Begin plugin definition * /
/ * BEGIN extension area definition * / / / / Define two extensions / * End extension definition
