WO2009082900A1

WO2009082900A1 - Page component layout method and device

Info

Publication number: WO2009082900A1
Application number: PCT/CN2008/072465
Authority: WO
Inventors: Jianjun Liu
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-12-29
Filing date: 2008-09-23
Publication date: 2009-07-09
Also published as: CN101470591A; CN101470591B

Abstract

A page component layout method is disclosed. The method which uses two different types of JSP tags including container tag and component tag includes: detaching layout logic from the component tags, finding layout manager corresponding to the container tag in which component tags located, and implementing the layout of the component tag. A device for generating HTML code by JSP is also disclosed. Because the layout code is generated by layout manager associated with the container tag, component tags have nothing to do with the layout logic, and it is possible to implement different layout requirements by using different container tags.

Description

Page control layout method and device

The present application claims priority to Chinese Patent Application No. 200710307876.0, entitled "Page Control Layout Method and Apparatus", filed on Dec. 29, 2007, the entire disclosure of which is incorporated herein by reference.

Technical field

The present invention relates to the field of page layout technology, and specifically relates to a method for implementing a page control layout through a Java Service Page (JSP: Java Server Page) tag and a corresponding code for generating a HyperText Markup Language (HTML: HyperText Markup Language) through a JSP tag. s installation.

Background technique

At present, in order to simplify the difficulty of writing HTML code, it is more and more common for developers to develop pages according to the writing habits of page controls. In these applications, the implementation of page control layout through JSP tags is an important part, usually in the following two ways:

First, the requirements for layout directly using HTML code, nesting JSP tags in the code for layout. Here is an example: In the above example, <xxx:A/> <xxx:B/> are JSP tag A and JSP tag B respectively (the start and end tags of the two JSP tags are merged together); > </table> is the layout start code and layout end code, respectively, before and after the two groups <3⁄4><3⁄4 (1> and <^(1></^> are nested in "<table>...... </table >" layout start and end code of JSP tag A and JSP tag B. This layout will display the upper and lower areas, display the contents of tag A in the upper area, and display the contents of tag B in the lower area.

The inventors of the present invention found in the research and practice of this method that the development difficulty associated with the layout has not been reduced in this method, and the developer needs to be familiar with the HTML code in order to write the code related to the page layout.

Second, the JSP tag generates the HTML code of its own layout at the same time. An example is as follows:

<xxx:form><xxx:A/><xxx:B/></xxx:form>

In the above example, <xxx:form></xxx:form> is the start and end tags of the JSP tag form. In the process of executing the above JSP tags, each JSP tag not only needs to generate its own content. The HTML code, also to generate the HTML code of its own layout, as shown below:

<form><table><tr><td>Content of tag A </td></tr><tr><td>Content of tag B

</tdx/tr></table></form>

Where <table> </table> is the layout code generated by the JSP tag form; before and after the two groups of inventors of the present invention found in the research and practice of this method, in this method, although the developer does not need to manually Write HTML code to implement the layout, but because the layout logic is fixed in the label, for the already completed label, the flexible layout requirements cannot be met. In addition, if you do not understand the layout logic used by the label, it is easy to cause conflicts in the layout of the generated HTML code after the label is executed, and destroy the overall layout structure of the page.

Summary of the invention

The embodiment of the invention provides a page control layout method and a corresponding device, which can realize the layout requirement of the JSP label simply and flexibly.

A page control layout method, comprising: executing a container start tag of a container tag, comprising: calling a layout manager corresponding to the container tag to generate a layout start code; executing a component tag in the container tag, including, according to the The container tag in which the component tag is located obtains a layout manager corresponding to the container tag, and the layout manager is invoked to generate a component layout start code and a component layout end code associated with the component tag; and the container that executes the container tag ends The tag includes, by calling, a layout manager corresponding to the container tag, and generating a layout end code.

An apparatus for generating HTML code by using a JSP tag, comprising: a Java service page engine, a container execution unit, and a component execution unit; the Java service page engine, configured to execute a Java service page file, when executing to a container tag Calling the container execution unit for execution, when the component tag is executed, calling the component execution unit to execute; the container execution unit having an interface for acquiring a layout manager, configured to: according to the Java service page engine Executing a call when the container of the container tag starts the tag, calling a layout manager corresponding to the container tag to generate a layout start code; and calling according to the call of the Java service page engine when executing the container end tag of the container tag The layout manager corresponding to the container tag generates a layout end code; the component execution unit has an interface for acquiring a layout manager, configured to: according to the call of the Java service page engine when executing the component label, according to the component label Container label obtained with the container label A corresponding layout manager is invoked, and the layout manager is invoked to generate a component layout start code and a component layout end code associated with the component tag.

And a computer program product comprising computer program code, which when executed by a computer, causes the computer to perform the steps of the aforementioned page control layout method.

And a computer readable storage medium, wherein the computer readable storage medium stores computer program code, when the computer program code is executed by a computer, the computer program code can cause the computer to perform the aforementioned Steps in the page control layout method.

In the technical solution of the embodiment of the present invention, two different types of JSP tags are used: a container tag and a component tag, the layout logic is stripped from the component tag, and the corresponding layout manager implementation component tag is found through the container tag where the component tag is located. Layout; because the layout manager associated with the container tag is responsible for the generation of the layout code, so that developers do not need to directly write the layout code, the development is simple; and, the component tag itself has nothing to do with the layout logic, can achieve different through different container tags Layout requirements, flexible and error-free.

DRAWINGS

1 is a schematic diagram of main steps of a page control layout method according to an embodiment of the present invention;

2 is a schematic diagram showing the basic logical structure of an apparatus according to an embodiment of the present invention;

3 is a schematic flow chart of a page control layout method according to an embodiment of the present invention;

4 is a schematic diagram showing the logical structure of a device corresponding to the method of the embodiment of the present invention;

FIG. 5 is a schematic flowchart of a second page control layout method according to Embodiment 2 of the present invention; FIG.

6 is a schematic diagram showing the logical structure of an apparatus corresponding to the method of the second embodiment of the present invention;

7 is a schematic flow chart of a method for layout a three-page control according to an embodiment of the present invention;

FIG. 8 is a schematic diagram showing the logical structure of an apparatus corresponding to the third method of the embodiment of the present invention.

detailed description

Embodiments of the present invention provide a page control layout method and corresponding apparatus. Referring to FIG. 1, the page control layout method of the embodiment of the present invention mainly includes the following steps:

Al. The container start tag of the container tag is executed, and the layout manager corresponding to the container tag is called to generate a layout start code.

Two different types of JSP tags are used in embodiments of the invention: container tags and component tags. By The component label needs to be placed in the container label, and therefore, the container label adopts a structure including a container start label and a container end label. Each container label is associated with the corresponding layout manager, which is negative by the layout manager

A2. Executing a component label in the container label, comprising: obtaining a layout manager corresponding to the container label according to the container label of the component label, calling the layout manager to generate a component layout start code and component layout end associated with the component label Code.

The component tag can take the form of a structure that includes a component start tag and a component end tag, or a structure in which the start and end tags are merged together. There may be one or more component tags in the container tag. If there are multiple component tags, execute each component tag in this step to generate the associated component layout start code and component layout end code.

A component tag can include one or more components that can be of a type or a consistent type. When generating the component layout start code and the component layout end code, you need to generate the component layout start code and the component layout end code for each component in the component label separately.

Further, the component tag usually needs to provide certain content, so executing the component tag in the container tag may further include generating the component content code between the steps of generating the component layout start code and the component layout end code; In the case of components, the respective component content code generated separately should be between the component layout start code and the component layout end code of the corresponding component. The so-called component content code can be composed of the component content start code and the component content end code; or it can be a single object component content code, such as text, which can be regarded as including the component content code of the single object in the component content. In the code or component content end code, if included in the component content start code, the component content end code may be empty, and if included in the component content end code, the component content start code may be empty.

A3. Executing a container end tag of the container tag, including, calling a layout manager corresponding to the container tag, and generating a layout end code.

Of course, the container tag can also have its own content, similar to the component content, and can be composed of the container content start code and the container content end code; or it can be a single object container content code. Therefore, in the process of executing the container start tag, after generating the layout start code, the container content code of the single object may be generated; or, in the process of executing the container end tag, the single object may be generated first. The container content code, and then perform the operation of calling the layout manager; or, during the execution of the container start tag, after generating the layout start code, generate the container content start code, and then in the process of executing the container end tag, Generate a container content end code, and then perform an operation that calls the layout manager. Wherein, the case of generating the container content code of the single object may also be regarded as performing the steps of generating the container content start and end code respectively, but the result of one of the execution steps is

In addition, if a component tag T is not in a container tag, or a component tag T is in another component tag, when the component tag T is executed, obtaining the corresponding layout manager operation will return a null value. The generation of the component tag T layout code is not performed.

The following describes the software objects involved from the perspective of code design according to the above page control layout method:

The container tag is primarily used to associate the layout manager. Since the layout manager needs to be called to implement the layout, the container tag provides a code interface to get the layout manager. Of course, in order to achieve flexible configuration of the layout manager, the container tag can further provide a code interface for setting the layout manager, so that the layout manager's layout logic can be modified and set by executing the container tag. Further, if the container tag has its own content, the container tag may further provide a code interface for generating a container content start code and a code interface for generating a container content end code, and if the container content is a single object container content code, one of the generated tags The code snippet provided by the code interface of the content can be empty. There are four interfaces, the code interface for generating the layout start and end code, and the code interface for generating the component layout start and end code.

The component tag is independent of the layout logic, so a code interface for generating the component content start code and the component content end code can be provided. If the component content is a component content code of a single object, the code segment provided by one of the code interfaces can be empty.

Referring to FIG. 2, corresponding to the above page control layout method, the apparatus for generating HTML code by using a JSP tag according to an embodiment of the present invention mainly includes a JSP engine (abbreviated as "engine," in FIG. 2) 101, and a container execution unit 102. And component execution unit 103.

The JSP engine 101 is configured to execute the JSP file, and the container execution unit 102 is called to execute when the container tag is executed. When the component tag is executed, the component execution unit 103 is called to execute. The container execution unit 102 has an interface for acquiring a layout manager, configured to: according to a call of the JSP engine 101 when executing a container start label of the container label, calling a layout manager corresponding to the container label to generate a layout start code; according to the JSP engine When the container end tag is executed by the container tag, the layout manager corresponding to the container tag is called to generate a layout end code.

The component execution unit 103 has an interface for acquiring a layout manager, and: according to the call of the JSP engine 101 when executing the component label, obtaining a layout manager corresponding to the container label according to the container label of the component label, and calling the layout The manager generates a component layout start code and a component layout end code associated with the executed component tag.

Further, the container execution unit 102 may further have an interface for setting a layout manager; such that the container execution unit 102 is further configured to set a layout manager corresponding to the container label according to a call of the JSP engine 101 when executing the container label. .

In the above basic scheme of the embodiment of the present invention, two different types of JSP tags are used: a container tag and a component tag, and the layout logic is stripped from the component tag, and the layout of the component tag is determined by the layout of the container tag where the component tag is located. The manager is responsible for the developer not having to write the layout code directly, and the development is simple; and, the component tag itself has nothing to do with the layout logic, and can be implemented by placing it in different container tags to achieve different layout requirements, and the use of the tag itself does not need to be generated and Layout-related HTML code, so it does not cause layout conflicts after the label is executed, ensuring the correctness of the layout logic.

The method and apparatus of the present invention are further described in detail below by way of specific examples.

Embodiment 1 A layout method of a page control, referring to FIG. 3 (in FIG. 3, a pair of oppositely-directional arrows with the same label indicate corresponding call and return, and further, due to the container execution unit/component actuator label/component label as The main body, the representation in the subsequent flowchart is the same, and will not be described again. It includes the following steps:

Al, the JSP engine (abbreviated as "engine" in Figure 3) calls the container execution unit to execute the container start tag of the container tag.

A2. The container execution unit executes the container start tag, and calls the layout manager corresponding to the container tag to generate a layout start code.

A3, the JSP engine calls the component execution unit to execute the component start label of the component label in the container tag Sign.

A4. The component execution unit executes a component start tag, and obtains a layout manager corresponding to the container tag according to the container tag where the component tag is located.

A5. The layout manager obtained by the component execution unit call generates the component layout start code.

A6. Usually the component tag needs to provide certain content, so when the component execution unit executes the component start tag, in addition to generating the component layout start code, the component content start code is further generated; the code segment can be empty. sign. . , , , a8, the component execution unit executes the component end tag, typically, the component content end code can be generated; this code snippet can be empty.

A9. After generating the component content end code, the component execution unit obtains a layout manager corresponding to the container tag according to the container tag where the component tag is executed.

Al0, the layout manager obtained by the component execution unit call generates the component layout end code.

All, the JSP engine calls the container execution unit to execute the container end tag of the container tag.

Al2, the container execution unit executes the container end tag, and calls the layout manager corresponding to the container tag to generate a layout end code.

In the above execution process, if the container tag includes a plurality of component tags inside, the steps of a3 ~ alO are repeated for each component tag.

Referring to FIG. 4, corresponding to the page control layout method of the first embodiment, the component execution unit 203 in the apparatus for generating the HTML code by using the JSP tag in the embodiment of the present invention may specifically adopt the following structures, including:

a first start unit 2031 for invoking a call to a component of a component tag according to a JSP engine (abbreviated as "engine" in FIG. 4), and obtaining a container tag based on the container tag in which the component tag is located The layout manager corresponding to the tag calls the obtained layout manager to generate the component layout start code.

The first ending unit 2032 is configured to obtain, according to the JSP engine 201, a call when the component end tag of the component tag is executed, and obtain a layout manager corresponding to the container tag according to the container tag where the component tag is located, and invoke the obtained layout management. Generates a component layout end code. The JSP engine 201 and the container execution unit 202 of FIG. 4 can employ the logical structure of the aforementioned JSP engine 101 and container execution unit 102.

For a better understanding of the first embodiment of the present invention, the following description will be made by way of example. For example, the JSP tag used in a JSP file includes the container tag grid, the component tag, and the component tag B:

<xxx:grid><xxx:A/><xxx:B></xxx:B></xxx:grid>

The JSP engine executes the above JSP file. When parsing the container start tag <xxx:grid> of the container tag grid, the container execution unit generates a layout start code (generated by calling the corresponding layout manager. For the sake of brevity, the following is omitted. Description, no longer repeat the description):

<table>

When the JSP engine parses into the component tag ^ :^> (the start and end tags are merged together), the component execution unit gets its container "grid" to find the relevant layout manager, and generates the component layout start code:

Then execute the component tag A to generate the start tag and end code of the component tag A's own content: <input type="text" name="A" ... ></input>

The component execution unit then generates the component layout end code through the layout manager:

</td></tr>

When the JSP engine parses the component start tag 3⁄40«:8> of component tag B, the component execution unit gets the container "grid" to which it is located, generates the component layout start code, and the component of component tag B. Content start code:

When the JSP engine parses the component end tag <^0«:8> of the component tag B, the component execution unit gets the container "grid" to which it is located, generates the component content end code of the component tag B, and the component layout end code:

</input></td></tr>

Finally, when the JSP engine parses the container end tag <^0«:^(1> of the container tag grid, the container execution unit generates a layout end code:

</table>

The output of the total HTML code is: <table><tr><td><input type="text"name="A"...></input></td></tr><tr><td><inputtype="text"Name="B" ... ></input></td></tr></table>

The corresponding layout effect is displayed in the browser as two lines, component A is displayed on the upper line, and component B is displayed on the lower line. Obviously, the component content code of component tag B can also be output once like component tag A, for example, output in the start code, then the end code output is empty.

Embodiment 2 A page control layout method differs from the first embodiment in that component tags have different types of components, and each component needs to have its own component layout start code and component layout end code. Referring to Figure 5, the following steps are included:

The bl, JSP engine (abbreviated as "engine" in Figure 5) calls the container execution unit to execute the container start label for the container label.

B2. The container execution unit executes a container start tag, and calls a layout manager corresponding to the container tag to generate a layout start code.

B3. The JSP engine invokes the component execution unit to execute the component start tag of the component tag in the container tag.

B4. The component execution unit executes a component start tag, and obtains a layout manager corresponding to the container tag according to the container tag where the component tag is located.

B5. The component execution unit acquires the front component in the executed component tag.

When a component tag needs to be responsible for generating the content of multiple components, it can contain multiple components. In this embodiment, three types are classified according to the role of the component: the front component, the main component, and the rear component. The main component usually refers to the main output of the component tag, which is generally one. If there is other nested content in the component tag, it will be the nested content of the main component, and the main component may or may not use the embedded content. The front component refers to the component that needs to be output in front of the main component. There may be more than one front component. Post component refers to the component that needs to be output behind the main component. There can also be more than one rear component.

For example, as shown in the "Input Box" component tag of a form field, you can define "Title", "Input Box", "Description", and three components, where the "Input Box" component is the main component, "Title," The component, "description" is the post component.

B6. The layout manager obtained by the component execution unit call generates the pre-component layout start code. B7. Usually the pre-component needs to provide certain content, so the pre-component content start code is further generated; this code fragment can be empty. B8. Generate the pre-component content end code; this code snippet can be empty.

B9. The layout manager obtained by the component execution unit call generates the pre-component layout end code.

If there are multiple pre-components obtained in step b5, repeat the steps b6 ~ b9 for each pre-component to obtain the layout code and content code of all the pre-components.

Bl0, the layout manager obtained by the component execution unit call generates the main component layout start code; bll, usually the main component needs to provide certain content, so the main component content start code is further generated; the code fragment can be empty. label.

Bl3, the component execution unit executes the component end tag, usually, the main component content end code can be generated; this code fragment can be empty.

Bl4. After generating the main component content end code, the component execution unit obtains a layout manager corresponding to the container tag according to the container tag where the executed component tag is located.

Bl 5, the layout manager obtained by the component execution unit call generates the main component layout end code. Bl6, the component execution unit obtains the post component in the executed component tag.

Bl7, the component execution unit calls the obtained layout manager to generate the post component layout start code. Bl8, usually the post component needs to provide some content, so the post component content start code is further generated; this code snippet can be empty.

Bl9, the generated component content end code; this code snippet can be empty.

B20. The component execution unit calls the obtained layout manager to generate the post component layout end code. If there are multiple post-components obtained in step bl6, repeat the steps bl7 ~ b20 for each post-component to obtain the layout code and content code of all the post-components.

B21. The JSP engine invokes the container execution unit to execute the container end tag of the container tag.

B22. The container execution unit executes a container end tag, and invokes a layout manager corresponding to the container tag to generate a layout end code.

Referring to FIG. 6, corresponding to the page control layout method of the second embodiment, the component execution unit 303 in the apparatus for generating the HTML code by using the JSP tag in the embodiment of the present invention may specifically adopt the following structures, including:

a second start unit 3031 for using a JSP engine (abbreviated as "engine" in FIG. 6) 301 When the component of the component tag starts to be tagged, ^^ obtains the layout manager corresponding to the container tag according to the container tag where the component tag is located; acquires the pre-component in the component tag, and calls the obtained layout manager before generating The component layout start code and the front component layout end code; the obtained layout manager generates the main component layout start code.

The second ending unit 3032 is configured to obtain, according to the call of the JSP engine 301 when executing the component end tag of the component tag, obtain a layout manager corresponding to the container tag according to the container tag where the component tag is located, and invoke the obtained layout management. The main component layout end code is generated; the post component in the component tag is obtained, and the obtained layout manager generates the post component layout start code and the post component layout end code.

The JSP engine 301 and the container execution unit 302 in Fig. 6 can employ the logical structure of the aforementioned JSP engine 101 and container execution unit 102.

A method of controlling a plurality of different types of component layouts by component tags is provided in this embodiment. For a better understanding of the second embodiment of the present invention, the following description will be made by way of example. For example, the JSP tag used in a JSP file includes a container tag grid and a component tag A. The component tag A breaks itself into three components: a front component "label", a main component, and a post component "description":

<xxx:grid><xxx:A label= "Title of component A" description= "Description of component A" /></xxx:grid>

The JSP engine executes the above JSP file. When parsing the container start tag <xxx:grid> to the container tag grid, the container execution unit generates a layout start code:

<table>

When the JSP engine parses into component tag A (the start and end tags are merged together), the component execution unit gets its container "grid" to find the relevant layout manager, and generates the pre-component layout start code:

Then, generate the content start and end code of the front component "label" (the front component "label" is used to generate the title content, which is a single object):

The title of component A

The component execution unit then generates the pre-component layout end code through the layout manager:

</td> Similarly, the component execution unit generates the layout start code and content code of the main component and the layout end code of the main component:

Then, the layout start code, content start and end code of the post component "description" is generated (the post component "description" is used to generate the description content, the content is a single object), and the layout end code:

<td> Description of component A </td></tr>

Finally, when the JSP engine parses the container end tag <^00^1^> of the container tag grid, the container execution unit generates a layout end code:

</table>

The output of the total HTML code is:

<table><tr><td>The title of component A</td><td><input type="text" name="A" .. ·> </input></td> <td>Component A Description</td></tr></table>

The corresponding layout effect is that one line is displayed in the browser, the title is displayed on the left side, the main component content is displayed in the middle, and the description content is displayed on the right side.

Embodiment 3 A page control layout method differs from Embodiment 1 in that a component tag contains a plurality of components of a distinguishable type, and each component needs to have its own component layout start code and component layout end code. Refer to Figure 7, including the following steps:

The cl, JSP engine (abbreviated as "engine" in Figure 7) calls the container execution unit to execute the container start tag of the container tag.

C2. The container execution unit executes a container start tag, and calls a layout manager corresponding to the container tag to generate a layout start code.

C3. The JSP engine invokes the component execution unit to execute the component start tag of the component tag in the container tag, and the code returned by the execution process may be empty. sign. . , , , , c5, the component execution unit executes the component end tag, and obtains a layout manager corresponding to the container tag according to the container tag where the component tag is executed.

C6. The component execution unit acquires each component in the executed component tag. When a component tag needs to be responsible for generating content of multiple components, multiple components may be included. In this embodiment, the types of components in the component tags are not distinguished, and the components included are uniformly operated.

C7. The layout manager obtained by the component execution unit call generates the component layout start code.

C8, usually the component needs to provide certain content, so the component content start code is further generated; this code fragment can be empty.

C9, generate component content end code; this code snippet can be empty.

Cl0, the layout manager obtained by the component execution unit call generates the component layout end code.

If there are multiple components obtained in step c6, repeat the steps of c7 ~ cl0 for each component, and obtain the layout code and content code of all components.

Cll, the JSP engine calls the container execution unit to execute the container end tag of the container tag.

Cl2, the container execution unit executes the container end tag, and calls the layout manager corresponding to the container tag to generate a layout end code.

In the above steps, steps c5 ~ cl0 can also be performed during the execution of the component start tag. When this tag is used, the returned code can be empty.

Referring to FIG. 8, corresponding to the page control layout method of the third embodiment, the component execution unit 403 in the apparatus for generating the HTML code by using the JSP tag in the embodiment of the present invention may specifically adopt the following structures, including:

The third start unit 4031 is configured to execute the component start tag according to a call of the JSP engine (abbreviated as "engine" in FIG. 8) 401 when the component of the component tag is started.

a third ending unit 4032, configured to obtain, according to the JSP engine 401, a call when the component of the component tag ends the tag, and obtain a layout manager corresponding to the container tag according to the container tag where the component tag is located; Each component of the call; the obtained layout manager separately generates the component layout start code and the component layout end code of each component.

The JSP engine 401 and the container execution unit 402 in Fig. 8 can employ the logical structure of the aforementioned JSP engine 101 and container execution unit 102.

A method of controlling a plurality of component layouts of the same type by component tags is provided in this embodiment. For a better understanding of the third embodiment of the present invention, the following description will be made by way of example. For example, the JSP tag used in a JSP file includes the container tag grid, the component tag A, and the component tag A. Solved into three components: "contentl" , "content2'\ "content3" :

<xxx:grid><xxx:A list="contentl, content2, content3 "/></xxx:grid>

<table>

When the JSP engine parses into the component tag A (the start and end tags are merged together), the component execution unit obtains the three components it contains and gets the container "grid" to find the relevant layout manager. Do the following for each component in turn:

Generate the component layout start code for the component "contentX" (representing 1, 2, 3 ):

Then, generate the content start and end code for "contentX" (the content is a single object): contentX

Then, generate the component layout end code for the component "contentX" (X for 1, 2, 3): </td>, or </td></tr>

After all the components have been executed in a loop, the processing of component label A ends.

</table>

The output of the total HTML code is: </table>

The corresponding layout effect is to display one row and three columns in the browser, the first column shows contentl, the second column shows content2, and the third column shows content3.

In the technical solution of the embodiment of the present invention, two different types of JSP tags are used: a container tag and a component tag, the layout logic is stripped from the component tag, and the corresponding layout manager implementation component tag is found through the container tag where the component tag is located. Layout; because the layout manager associated with the container tag is responsible for the generation of the layout code, the developer does not need to directly write the layout code, which simplifies the development and maintenance of the component tag; and, the component tag itself is independent of the layout logic, and can be different. Container tags implement different layout requirements, are scalable, flexible, and error-prone. Further provision A method of controlling multiple or different types of component layouts through component tags can support more flexible application methods.

A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be completed by a program instructing related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: ROM, RAM, disk or CD, etc.

The foregoing detailed description of the page control layout method and corresponding apparatus provided by the embodiments of the present invention is only for helping to understand the method of the present invention and its core ideas; meanwhile, for those skilled in the art, according to the present invention The scope of the present invention is not limited by the scope of the present invention.

Claims

OP080518 WO 2009/082900 PCT/CN2008/072465 - 16- Claims

A page control layout method, comprising:

Executing a container start tag of the container tag, comprising: calling a layout manager corresponding to the container tag to generate a layout start code;

Executing the component tag in the container tag, comprising: obtaining a layout manager corresponding to the container tag according to the container tag where the component tag is located, invoking the layout manager to generate a component layout associated with the component tag Code and component layout end code;

Executing the container end tag of the container tag includes invoking a layout manager corresponding to the container tag to generate a layout end code.

2. The page control layout method according to claim 1, wherein:

The container start tag of the execution container tag further includes: generating a container content code of the single object after generating the layout start code; or

The container end tag of the execution container tag further includes: generating a container content code of the single object, and then performing the operation of calling the layout manager; or

The container start tag of the execution container tag further includes: after generating the layout start code, generating a container content start code; the executing the container end tag of the container tag further includes: generating a container content end code, and then executing the call layout Manager operation.

3. The page control layout method according to claim 1, wherein: the container tag includes one or more component tags, and each of the steps of executing the container start tag and executing the container end tag respectively Component label.

4. The page control layout method according to claim 1, wherein:

The component tag in the execution container tag further includes, between the step of generating the component layout start code and the component layout end code, generating the component content code, the component content code being a component content code of a single object or starting from the component content The code and component content end code are composed.

The page control layout method according to any one of claims 1 to 3, wherein the calling layout manager generates a component layout start code and a component layout end code associated with the component tag as follows:

Executing a component start tag of the component tag, including: obtaining a layout manager corresponding to the container tag according to the container tag where the component tag is located, calling the layout manager to generate a component cloth OP080518

WO 2009/082900 PCT/CN2008/072465

- 17- Bureau start code;

Executing the component end tag of the component tag includes: obtaining a layout manager corresponding to the container tag according to the container tag where the component tag is located, and calling the layout manager to generate a component layout end code.

6. The page control layout method according to claim 5, wherein:

The component start tag of the execution component tag further includes: generating a component content code of the single object after generating the component layout start code; or

The component end tag of the execution component tag further includes: generating a component content code of the single object, and then performing the operation of obtaining the layout manager; or

The component start tag of the execution component tag further includes: after generating the component layout start code, generating a component content start code; the component end tag of the execution component tag further includes: generating a component content end code, and then performing the obtaining The operation of the layout manager.

The page control layout method according to any one of claims 1 to 3, wherein the component tag includes three types of components: a front component, a main component, and a rear component; The end code includes layout start and end codes for the three types of components; the call layout manager generates a component layout start code and a component layout end code associated with the component tag specifically as:

Executing a component start tag of the component tag, comprising: obtaining a layout manager corresponding to the container tag according to the container tag where the component tag is located; acquiring a front component in the component tag, calling the layout manager to generate a front component layout start code and a front component layout end code; calling the layout manager to generate a main component layout start code;

Executing a component end tag of the component tag, comprising: obtaining a layout manager corresponding to the container tag according to the container tag where the component tag is located, calling the layout manager to generate a main component layout end code; acquiring the component The post component in the tag calls the layout manager to generate the post component layout start code and the post component layout end code.

8. The page control layout method according to claim 7, wherein:

The component start tag of the execution component tag further includes: generating a pre-component content code of the single object or separately generating the pre-component content start code and the pre-component content between the steps of generating the pre-component layout start code and the pre-component layout end code End code; and/or, OP080518

WO 2009/082900 PCT/CN2008/072465

The component end tag of the execution component tag further includes, after the step of generating the post component layout start code and the post component layout end code, generating a post component content code of the single object or separately generating the post component content start code and Post component end code; and/or,

The component start tag of the execution component tag further includes: generating a main component content code of the single object after generating the main component layout start code; or: the component end tag of the execution component tag further includes: generating a main component of the single object a content code, and then performing the operation of obtaining the layout manager; or, the component start tag of the execution component tag further includes: generating a main component content start code after generating the component layout start code, the component of the execution component tag The closing tag further includes generating a main component content end code and then performing the operation of obtaining the layout manager.

9. The page control layout method according to claim 7, wherein:

In the step of acquiring the front component in the component tag, the obtained front component is more than one, and the front component layout start code and the front component layout end code of each front component are respectively generated, and then the generated main component layout start code is executed. Steps; and/or,

In the step of obtaining the post component in the component tag, the obtained post component is more than one, and the post component layout start code and the post component layout end code of each post component are respectively generated.

The page control layout method according to any one of claims 1 to 3, wherein the component tag includes one or more components; the calling layout manager generates a component layout associated with the component tag. The start code and component layout end code are specifically:

Executing a component start tag of the component tag;

Executing a component end tag of the component tag, comprising: obtaining a layout manager corresponding to the container tag according to the container tag where the component tag is located; acquiring each component in the component tag; calling the layout manager respectively Generate component layout start code and component layout end code for each component.

11. The page control layout method according to claim 10, wherein:

The component end tag of the execution component tag further includes: generating a component content code of the single object or separately generating the component content start code and the component content end code between the steps of generating the component layout start code and the component layout end code of each component .

12. An apparatus for generating a hypertext markup language code by a Java service page tag, comprising: a Java service page engine, a container execution unit, and a component execution unit; OP080518

WO 2009/082900 PCT/CN2008/072465

The Java service page engine is configured to execute a Java service page file, and when the container tag is executed, the container execution unit is called to perform execution, and when the component tag is executed, the component execution unit is called to perform execution;

The container execution unit has an interface for obtaining a layout manager, configured to: according to the call of the Java service page engine when executing a container start label of the container label, invoke a layout manager corresponding to the container label to generate a layout start a code; according to the call of the Java service page engine when executing the container end tag of the container tag, calling a layout manager corresponding to the container tag to generate a layout end code;

The component execution unit has an interface for obtaining a layout manager, configured to: obtain, according to the call of the Java service page engine when executing the component label, a layout corresponding to the container label according to the container label where the component label is located a manager that invokes the layout manager to generate a component layout start code and a component layout end code associated with the component tag.

13. The apparatus according to claim 12, wherein: the container execution unit further has an interface for setting a layout manager; the container execution unit is further configured to: when the container label is executed according to the Java service page engine The call to the layout manager corresponding to the container tag.

The device according to claim 12 or 13, wherein the component execution unit comprises:

a first start unit, configured to: according to the call of the Java service page engine when executing a component start tag of the component tag, obtain a layout manager corresponding to the container tag according to the container tag where the component tag is located, and invoke the The layout manager generates a component layout start code;

a first ending unit, configured to: according to the call of the Java service page engine when executing a component end tag of the component tag, obtain a layout manager corresponding to the container tag according to the container tag where the component tag is located, and invoke the The layout manager generates a component layout end code.

a second start unit, configured to obtain, according to the call of the _java service page engine when the component of the component tag is started, obtain a layout manager corresponding to the container tag according to the container tag where the component tag is located; The front component in the component tag, before calling the layout manager OP080518

WO 2009/082900 PCT/CN2008/072465

-20- component layout start code and front component layout end code; calling the layout manager to generate a main component layout start code;

a second ending unit, configured to: according to the call of the _java service page engine when executing the component end tag of the component tag, obtain a layout manager corresponding to the container tag according to the container tag where the component tag is located, and invoke the location The layout manager generates a main component layout end code; acquires a post component in the component tag, and calls the layout manager to generate a post component layout start code and a post component layout end code.

a third start unit, configured to execute the component start tag according to the call of the Java service page engine when executing a component start tag of the component tag;

a third ending unit, configured to obtain, according to the call of the Java service page engine when executing a component end tag of the component tag, obtaining a layout manager corresponding to the container tag according to the container tag where the component tag is located; Each component in the component tag; invokes the layout manager to generate a component layout start code and a component layout end code of each component.