JPH10269072A - Application development method - Google Patents

Abstract

(57) [Summary] [Problem] To respond to a request from a client computer,
An object of the present invention is to provide a method capable of transferring a template file in which a script program for generating display information of page b is described to a file system on a server computer or a file system on a computer that can be referenced from the server computer. A process for inputting a name of a template file to be read by a program for generating display information of a web page, a portion referring to the template file, and a portion describing a process for calling another processing program are described. The process of acquiring information, the process of displaying the obtained information on the output device, the process of correcting unresolved references and calls, and the template files included in the obtained list and the implementation files of the processing programs can be referenced. The problem is solved by performing a process of transferring the file to a file system on a computer.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention reads a file containing a script program from a file system on a server computer, interprets and executes the script program, generates Web page display information, and discloses the information on the server computer. In a system that performs the script program described in a specific file, interpret and execute the script program.
The file belongs to a method of developing a server application that operates in conjunction with a Web server and stores the necessary files from the file system of the development computer to the file system of the server computer.

[0002]

2. Description of the Related Art In recent years, the Internet, which is a worldwide network, and WWW (World Wid) which is one of information disclosure applications on the Internet.
With the development of e-Web), browsing a Web page disclosed on a Web server of a server computer using a Web browser on a client computer has been widely performed. The display information of the Web page is HTML (Hype
rtext Markup Language). For the WWW, see "OPENDESI
GN, No. 13, April 1996, pp. 4-5 of "CQ Publishing Company" (Reference 1). Details of HTML are described in pp. 40-59 of Reference 1.

A method of disclosing a Web page on a Web server includes a method of storing display information of a Web page in a file on a file system of a server computer, and transferring the stored contents of the file as it is to a client computer. And executing a page generation program for generating Web page display information on the server computer in response to a request from the client computer, and transferring the Web page display information generated by the page generation program to the client computer. There is a dynamic way.

[0004] As a system capable of dynamically generating display information of a Web page using the dynamic method,
There are the following: In either system, a file (hereinafter, referred to as a template file) describing a script program for generating display information of a Web page is stored in a file system on a server computer, and a request from a client computer is stored. In accordance with the method, the page generation program reads the template file, interprets and executes the script program described in the template file based on the value of the parameter specified from the client computer, and generates the display information of the Web page. doing. In any of the systems described below, the contents of the template file read by the page generation program in order to generate display information of the Web page are in a format in which a script program is embedded and described in ordinary HTML. I have.

(1) Internet Information
Tion Server 3.0 (Microsoft
About this system, "PCWEEK JAPANES
E EDITION, NOVEMBER 15, 1996
VOLUME 7, NUMBER 40, SoftBank ”(Reference 2), p. 1. In a form embedded in HTML, a script program written in script languages VBScript and JavaScript is executed on a server computer to dynamically execute HTML. "Ati" that can generate data and return it to the web browser
ve Server Page ".

The function of creating an HTML file is provided by another system "FrontPage97". F
rontPage 97, p. 25
Is described in.

(2) LiveWire (Netsca
pe Communications) (2) is described in “Nikkei Open System, No. 37, April 1996, Nikkei BP” (Reference 3). 282-293. (2)
The system has a function of executing a script program described in a script language JavaScript in a format embedded in HTML on a server computer, dynamically generating HTML data, and returning the generated HTML data to a Web browser.

[0008] Each of the above systems analyzes the description of the static part described in HTML from the description included in the template file read by the page generation program, and refers to the reference relation between the files and the unresolved reference. It has a function to present the information of the user to the user. However, it does not have a function of analyzing the processing of a part of a script program described in a script language and presenting information of a reference relation between files and information of an unresolved reference to a user.

[0009]

In each of the above-mentioned prior arts, a page generation program started on a server computer reads a template file in which a script program is described, interprets and executes the script program, and displays Web page display information. Was generated, and a server application to be disclosed on the server computer could be developed. However, there were the following problems.

(1) When a certain template file is specified as a component of the server application, a set of a template file and a processing program to be referred to in accordance with the processing of the script program in the specified template file is specified. The user himself had to analyze the contents of the script program. Further, when another template file or processing object is referred to in the script program described in the referenced template file, this operation has to be repeated. For this reason, much effort was required to specify all the sets of the template file and the processing program required when executing the server application, and to place them on a file system that can be referred to by the page generation program.

(2) The reference relationship between the template files based on the processing of the script program portion of the template file obtained in (1) cannot be listed on the output device. For this reason, it has been difficult to grasp the reference relation of the entire template file constituting the server application.

[0012]

To solve the above problems, the following means are provided.

(1) On a file system of a development computer, a template file describing a script program for generating display information of a Web page and an implementation file of a processing program operated from the script program are stored. A means for selecting a template file to be used as a component of the server application and specifying its name.

(2) Analyzing the script program described in the template file specified in (1), identifies a location referring to the template file and a location calling another processing program, and refers to And the means to identify the callee.

(3) A means for repeating the processing of (2), obtaining a list of template files and processing programs to be referred to when the server application is executed, and displaying the list on an output device.

(4) Means for obtaining an unresolved reference or call out of the reference destination and the call destination obtained in (2) and displaying it on an output device.

(5) Means for correcting and solving the unresolved reference and call obtained in (4).

(6) Means for transferring a set of a template file and a processing program mounting file required when executing the server application to a server computer that executes a Web server or a file system on a computer that can be referred to from the server computer. .

[0019]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the present invention will be described below.

FIG. 2 shows a hardware configuration of a computer device for implementing the present invention. The computer 200
A main storage device 206 serving as an internal storage device, an external storage device 203 for storing an entity of a file managed by a file system, a central processing device 204 for executing a program stored in the main storage device 203, and an input from a user An input device 202 for receiving data, a display device 201 for outputting a processing result of the computer, and a network device 205 for transmitting and receiving data between the computers via a network line. These devices are connected to each other by a bus device 207 for transferring data.

The present invention is realized by controlling data input from or output to these devices, and data processing and inspection in accordance with a program loaded in the main storage device 206.

Before describing specific processing procedures, terms used in the present embodiment will be described. In the present invention, an application program that operates in cooperation with a Web server program is called a “Web server application”. Also, an object in which a processing procedure that is externally disclosed based on the object orientation is implemented as a method is called a “processing object”, and a file including the implementation of the processing object is called a “processing object module file”. For the object orientation, see "Hirofumi Onozawa, Distributed Object Oriented CORBA, Soft Research Center (1996)" (pp. 4). 13-2
1. The method of accessing the processing object from the outside is described in the distributed object-oriented technology CORBA (Common Object Req).
west Broker Architecture)
In the case of pp. Pp. 176-178. In the example shown in this document, a naming service is provided to provide a service for registering and using an object reference which is reference information of an object. Name the object and register it in the naming service, and the client program
Access the object by searching for the object from the registered name. Here, since the naming service does not assume a specific implementation, there may be an implementation using an existing system implementation and an implementation using a file system. In this embodiment, a method is used in which the name of a processing object and the name of an implementation file of the processing object are registered in a file on the file system, and the implementation of the processing object is searched from the registered processing object name.

Further, as described in the "prior art", W
A file including a script program for generating display information of an eb page is called a “template file”.

FIG. 1 shows the operating environment and configuration of the Web server application development system 116. First, the operating environment will be described. As the operating environment, WWW, which is a conventional technique described in “Prior Art”, is used. The development computer 101 is a computer that executes the Web server application development system 116. The server computer 102 is a computer that executes the Web server application execution system 119. The client computer 104 is a computer that executes the Web browser system 115. Development computer 101, server computer 10
2 and the client computer 104 are connected by a network line 103. The external storage device 203 of the development computer 101 stores the template file 108
, A processing object module file 109, and a processing object registration file 107.

Next, the configuration will be described. The Web server application development system 116 includes a template file debugging process 105, a call information management table 106, an unanalyzed template table 117, and a call information temporary storage table 118. We
b server application development system 116
b) Obtain information specifying a template file and a processing object module file necessary for executing the server application execution system 119, and list the names of the specified files on the display device 2 as an output device.
01, and identifies the unresolved reference included in the script program described in the template file, and displays the information for specifying the reference destination information on the display device 201.
, And a process of correcting unresolved references is performed.
Subsequently, the Web server application execution system 1
The template file and the processing object module file necessary for executing the program 19 are transferred to a disk device which is the external storage device 203 on the server computer 102, and stored as a file on the file system. The template file 113 and the processing object module file 114 correspond to the stored files. The Web browser system 115 transfers the HTML data transfer request input by the user from the input device 202 to the Web server application execution system 119. Based on the request transferred from the Web browser system 115, the Web server application execution system 119 reads the template file 113, interprets and executes a script program included in the template file 113, generates HTML data, and sends the HTML data to the Web browser system 115. Forward. When interpreting and executing the script program, the Web server application execution system 119 refers to and reads another template file 113 so as not to describe the script program, activates the processing object, receives the processing result, and embeds the processing result in the template file. Perform processing. The Web browser system receives the transferred HTML data and displays it on the display device 201.

Before specifically describing the Web server application development system 116 according to the present invention, the Web server application development system 116
The basic operation of the Web server application execution system 119 and the Web browser system 115 to which is applied will be described.

FIG. 7 shows a processing object registration file 1
07 shows the data structure of the data. The content of the processing object registration file 107 is an array having a data structure called a processing object registration entry 701 as an element. The processing object registration entry 701 has a data structure including an integer 702 called an index, a character string 703 indicating the name of the processing object, and a character string 704 indicating the name of a module file in which the processing object is mounted.

Next, the relationship between the components will be described with reference to the flowcharts of FIGS.

FIG. 3 is a flowchart showing the flow of processing of the Web browser system 115 and the Web server application execution system 119. FIG.
Display device 201 by Web browser system 115
6 is a display example of a Web browser screen 403 to the Web browser. By reading the HTML data shown by 500 in FIG. 5 into the Web browser system 115, the Web browser shown in FIG.
b Browser screen 403 can be displayed. First, in step 301. On the web browser screen 403, a URL (Universal Res) is input from the input device 202.
source Locator). For the URL, refer to pp. 139 of Reference 1 described in “Prior Art”. 6-1
0. To specify the URL,
There are a method of inputting a character string from the input device to the input area 402 of the b-browser screen 400 and a method of designating a part called an anchor indicated by 401 with the screen designating device as the input device 202. The anchor indicated by 401 is displayed based on the portion indicated by 501 in the HTML data of FIG. When an anchor indicated by 401 is designated by the screen pointing device, 50
URL “http: // cgi-bin /
page? TEMPLATE = SHOPDOOR. TM
The same result as when PL & SHOPNAME = A "is obtained. Next, at step 302, the designated U
The RL is transmitted to the Web server program 110 executed on the server computer 102, and a request for transferring HTML data is made. When the Web server program 110 receives the transmitted URL in step 304, the Web server program 110 executes HTML data generation processing 111 in CGI (C
Ommon Gateway Interface). About CGI,
"Doctor Dobbs Journal Japan Version, Vol. 5, N
o. 6, June 1996, Shosyosha, pp.
This is described at 30-37.

In the URL indicated by 502, "pag
e ”is the module name of the program that implements the HTML data generation processing 111, and TEMPLATE = SH
OPDOOR. TMPL and SHOPNAME = A are parameters to be passed to the HTML data generation processing 111. The activated HTML data generation processing 111 includes:
The HTML data 307 is generated, and the generated HTML data 307 is transmitted to the Web server program 110. When the processing of the HTML data generation processing 111 ends, the Web server program 110
The TML data 307 is received in step 306, and further transferred to the Web browser system 115. The Web browser system transmits the transferred HTML data 30
7 is received in step 303, and the Web browser screen 40
3 display characters, images, and the like.

FIG. 6 is a flowchart of the HTML data generation processing 111. First, in step 601, the TEM
Gets the character string specified in the PLATE parameter.
In the example of the URL indicated by 502, TEMPLAT
The value of the E parameter is “SHOPDOR.TMPL”. Next, in step 602, the template file 11 whose name is specified by the TEMPLATE parameter
3 is read. Subsequently, in step 603, the script program included in the read data is analyzed, and a call is made according to the script program.

In this embodiment, two types of calls, that is, a process object call and an include call, are used as calls performed in step 603. The processing object call is executed by the processing object module file 11
4 is a process of calling the processing object mounted on the processing object No. 4 and embedding the processing result of the processing object in the read data. The include call is a process of embedding the contents of the specified template file 113 in the read data according to the script program.

In the present embodiment, there is a page generation call as a call other than that performed in step 603. The page generation call is performed in the HTML data generation processing 111.
Generated by reading the template file 113
The processing after the processing step 301 is executed by the hyperlink included in the TML data 307, and H
Template file 1 in TML data generation processing 111
13 shows a calling relationship between the template files 113 such that the HTML file 307 is read and the HTML data 307 is generated. Note that the hyperlink is described in p. 5 is explained.

FIG. 8 and FIG. 9 are description examples of the template file.

FIG. 10 shows HTML data 307 generated based on the template files shown in FIGS.
Shows an example of the contents of the above.

FIG. 11 is a diagram showing a case where the Web browser system 115 reads the HTML data shown in FIG.
6 is a display example of an web browser screen 403.

The processing of step 603 will be described below with reference to FIGS. In this embodiment, the template file is defined by embedding a script program in a normal HTML description. The script program is described in a section surrounded by “<! ＠” and “>” to distinguish it from a portion described in ordinary HTML. Variables are represented by character strings starting with "@". Processing step 601
The parameters obtained in can be handled as variables in the script program included in the template file. For example, the URL indicated by 502 is
If you specify 01, in the script program,
It can be handled as the variable $ SHOPNAME of the value "A".

The template file SHOPDOR.
In the TMPL (801), the portions indicated by 802 and 805 are the script programs. The script program 802 represents the processing object call, and is described in one line in a format of “<! @ EXEC variable name = processing object name.method name ()>”. The script program 802 represents a process of calling the GetGender method of the processing object PERSON and setting the return value to a variable $ GENDER.

The activation of the processing object is performed by referring to the processing object registration file 107 and obtaining the path name 704 of the module file corresponding to the value of the name 703 of the processing object. If the character string registered in the computer name 705 of the same entry is not empty, the processing object module file 114 on the computer specified by the computer name 705 is activated via the network line 103. If the registered character string is empty, the server computer 1
02 starts the processing object module file 114 on the disk device.

The entire script program 805 represents a conditional branch. If the value of the variable $ GENDER is "male", the script program 803 is executed; otherwise, the script program 804 is executed. Script program 803 and script program 80
4 indicates the include call, and “<! ＠”
Include template file name> ”in one line. The script program 803 reads the template file MAN.TMPL and embeds the contents in the location where this processing is described. Indicates a process of reading the template file WOMAN.TMPL and embedding the contents in a place where the present process is described.

Next, the template file MAN. TM
PL (901) and WOMAN. TMPL (904)
Is described. Portions 902, 903, 905 and 906 are script programs,
Each of them represents the page generation call. The page generation call is "<A HREF =" http: //
/ Cgi-bin / page? TEMPALTE = template file name & argument 1 = value of argument 1 & argument 2 =
Argument 2 value &. . . & Argument n = value of argument n ">" Portions indicated by 902 and 905 are template files WEAR. H generated by HTML data generation processing 111 based on TMPL (907)
A hyperlink to the TML data 307 is shown.
The portion indicated by 903 is a template file GOL
F. A hyperlink to the HTML data 307 generated by the HTML data generation processing 111 based on the TMPL is shown. The portion indicated by reference numeral 906 is a template file COSMETIC. HT based on TMPL
HTML generated by the ML data generation processing 111
A hyperlink to the data 307 is shown.

Subsequently, the template file WEAR.
The description contents of TMPL (907) will be described. The entire part indicated by reference numeral 908 is a script program. The script program 908 represents a repetitive process,
Script programs 909, 910 and 91 internally
Including 1. The script program 909 and the script program 910 are processing object calls. The script program 909 represents a process of calling the GetGood method of the GOODSDB object and setting the processing result to the variable $ GOOD. The script program 910 represents a process of calling the GetPrice method of the GOODSDB object and setting the processing result to the variable $ PRICE. The script program 911 includes the variables $ GOOD and $ P
This shows a process of embedding the content set in the RICE at the location where both variable names are described. In step 602, the template file SHOPDOR. T
10 is an example of HTML data generated in step 603 when an MPL (801) is read. 1101 is H
TML data 1001 is transferred to Web browser system 115
6 is a display example of a Web browser screen when reading is performed by using the Web browser. When the location indicated by the anchor 1102 is designated on the Web browser screen 1101 by the screen pointing device, step 302 is executed again based on the hyperlink 1002 included in the HTML data 1001, and as a result, the template File W
EAR. The TMPL (907) is read, and step 603 is executed again to generate HTML data 307. 1003 shows an example of the generated HTML data 307. 1103 is a display example of a Web browser screen when the HTML data 1003 is read by the Web browser system 115. Further, in step 604, the HTML data 307, which is the processing result of step 603, is
Send it to the web server program 110.

As described above, the Web browser system 115 and the Web server application execution system 119
Ends the description.

Next, the operation of the Web server application development system 116 according to the present invention will be specifically described.

FIG. 12 shows a flowchart of the template file debugging process 105 included in the Web server application development system 116. First, in step 1201, one or more file names included in the template file 108 stored on the file system of the disk device of the development computer 101 are designated from the input device 202. Step 120
2, the template file 108 specifying the name
Is read, a script program included in the read data is analyzed, and information on a call included in the script program is obtained. Subsequently, call information is also acquired for the template file 108 referred to by the call. By repeatedly performing this process, information on the call relationship regarding the template file 108 and the processing object is acquired, and the acquired information on the call relationship is stored in the call information management table 106. Then step 120
In step 3, the data in the call information management table 106 is read, and the names of all template files and processing objects used in the Web server application execution system are displayed on the display device 201. Further, in step 1204, from the data stored in the call information management table 106, information on an unresolved call in which the template file or the processing object of the call destination is not available is obtained and displayed on the display device 201. If there are outstanding calls in step 1205,
Proceeding to step 1207, the template file 108 and the processing object module file 109 required to execute the Web server application execution system 119 are transferred to the server computer 102, stored in the disk device of the server computer 102, and the processing ends. I do. If there is an unresolved call in step 1205, the process returns to step 1202 after correcting the unresolved call in step 1206.

Next, the data structure used in the template file debugging process 105 will be described.

FIG. 15 shows an unanalyzed template table 1
17 shows a data structure of the seventeenth embodiment. The unanalyzed template table 117 is a table for registering information of a template file whose call information included in the script program has not been analyzed yet. The content of the unanalyzed template table 117 is an array having a data structure called an unanalyzed template entry 1501 as an element. The unparsed template entry 1501 has a data structure including an integer 1502 called an index, a character string 1503 indicating the name of the template file 108, and an integer 1504 indicating the status of the template file. The integer 1504 indicating the state is a constant DE
It can take the value of either FAULT or constant ADD. DEFAULT indicates the template file specified in step 1201 first, and ADD indicates the template file added by the processing in step 1202 and subsequent steps.

FIG. 16 shows the data structure of the call information temporary storage table 118. The call destination temporary storage table 118 is a table for temporarily storing information of a template file or a processing object called by a script program of a specific template file. The content of the callee temporary storage table 118 is an array having a data structure called a callee template entry 1601 as an element. The callee template entry 1601 is
An integer 1602 called an index, a character string 1603 indicating the name of a template file or a processing object to be called, and an integer 160 indicating a type of call
4 is a data structure composed of Integer 1604 indicating the type of call is a constant GENERATE, INCL
It can take any value of UDE and OBJECT. Each value represents a page generation call, an include call, and a processing object call in order.

FIG. 17 shows the call information management table 10
6 shows the data structure of FIG. The call information management table 106 is a table for holding information on template files and processing objects necessary for executing the Web server application execution system 119, and information on call relations regarding the template files and processing objects. The contents of the call information management table are the call information management entry 1
An array having a data structure called 701 as an element.
The call information management entry 1701 includes an integer 1702 called an index, a character string 1703 indicating the name of the template file or the processing object, and an integer 17 indicating the type of the template file or the processing object.
04, an integer 1705 indicating the status of the template file or the processing object, and an integer 1706 indicating the address on the memory of the callee information management area 1800. Integer 170 indicating the type
4 can take either the constant TEMPLATE or the constant OBJECT. Each value represents a template file and a processing object in order. The integer 1705 indicating the state has the same meaning as the integer 1504 indicating the state in the unparsed template entry 1501.

FIG. 18 shows a callee information management area 180.
0 shows the data structure. The contents of the callee information management area 106 are
An array having a data structure called 01 as an element. The callee information management entry 1801 includes an integer 1802 called an index, an integer 1803 indicating the line number of a place where the call is described in the template file, an integer 1804 indicating the type of call, and a callee template file or processing object. A character string 1805 indicating the name, and an integer 180 indicating the state of the call
6 is a data structure composed of. The integer 1804 indicating the type of call has the same meaning as the integer 1604 indicating the type of call in the callee template entry 1601. Integer 1806 indicating the status of the call
Can take a value of either a constant OK or NG.
OK indicates that the called template file or processing object exists. NG indicates that the reference is unresolved because the called template file or the processing object does not exist.

Next, each step of the flowchart of FIG. 12 will be described in detail.

FIG. 13 is a flowchart showing step 120 in FIG.
2 shows the flowchart of FIG. First, in step 1301, the values of the index 1502, template file name 1503, and state 1504 are registered in the unanalyzed template table 117 for each of the template files specified in step 1201. It is assumed that all the values of the state 1504 are DEFAULT.

Subsequently, in step 1302, it is checked whether or not the contents of the unanalyzed template table 117 are empty. If the contents are empty, the processing is terminated. If not, step 1 is executed.
Go to 303.

In step 1303, the template file name 1503 and the state 1504 included in the last entry 1501 of the unanalyzed template table 117
Is taken out and set in variables TEMPLATE and STATUS, respectively.

Next, in step 1304, step 13
The last entry 1501 of the unanalyzed template table 117 referred to in step 03 is deleted.

In step 1305, the call information management entry 17 is added to the end of the call information management table 106.
01 is added, the value of TEMPLATE is registered in the name 1703 of the template file or the processing object, and the value of STATUS is registered in the state 1705.

In step 1306, if the file name is T
The template file 108 which is EMPLATE is read, and the script program of the template file 108 is analyzed to identify a place where the processing of the call is described. Specifically, the line described in the format of “<! @ EXEC variable name = processing object name.method name ()>” is determined to be the processing object call, and “<! @ INCLUDE template file name” > ”Is determined to be the include call, and“ <A HREF =
“Http: // cgi-bin / page? TEMP
LATE = template file name & argument 1 = argument 1
Value & argument 2 = value of argument 2 &. . . & Argument n = Value of Argument n ">" The line described in the format is determined to be the page generation call. For each part where the processing of the call is described, the line number in the template file 108, the type of the call, and the name of the processing object or the template file to be called are acquired, and an entry 1601 is added and registered. The acquired line number is registered in the line number 1603 of the call information temporary storage entry 1601, the acquired call destination name is registered in the call destination name 1604, and the call type 160
In 5, the acquired call type is registered.

At step 1307, the value 1 is set to the loop control variable i. At step 1308, if the value of i exceeds the number of entries in the call information temporary storage table 118, the process returns to step 1302; Goes to step 1309. The processing after step 1309 is to inspect each template file or processing object referred to by a call in the script program included in the specific template file 108. In step 1309, the name of the call destination 1604 of the i-th entry 1601 of the call information temporary storage table 118 is obtained, and the variable D
Set a value in ESTINATION. Next step 1
At 310, a check is made for a callee whose name is DESTINATION. Details of the processing in step 1310 will be described with reference to FIG. After adding 1 to the value of the variable i in step 1311, the process returns to step 1308.

In the above processing, the call information management table 106 stores information on template files and processing objects necessary for executing the Web server application execution system 119, and information on call relations regarding the template files and processing objects. Is done.

FIG. 14 is a flowchart showing step 131 in FIG.
9 is a flowchart showing a detailed process of the process No. 0. The variable i in this flowchart is the same as the variable i in FIG. First step 1401
Then, the value of the call type 1605 included in the i-th entry 1601 of the call information temporary storage table 118 is acquired, and if the value is OBJECT, step 1 is executed.
Proceed to 409. Otherwise, that is, if the acquired value is GENERATE or INCLUDE, the process proceeds to step 1402. Here, steps 1402 through 14
Until 06, the processing when the call destination is a template file is performed from step 1409 to step 1413.
The above shows processing when the call destination is a processing object.

First, the case where the call destination is a template file will be described. In step 1402,
It is checked whether there is a template file 108 whose file name is DESTINATION. If not, in step 1403, the variable EXIS is set to the constant F
ALSE is set, and the routine proceeds to step 1407. If there is, at step 1404, a constant T is set to the variable EXIST.
The RUE is set, and the process proceeds to step 1405. Step 1
In step 405, the contents of the call information management table 106 are checked to check whether an entry 1701 whose value of the name 1703 matches DESTINATION is registered. If it has already been registered, the process proceeds to step 1407; otherwise, the process proceeds to T step 1406. In step 1406, an entry 1501 is added to the unanalyzed template table 117. The value of the name 1503 of the entry to be added is DESTINATION, and the value of the state 1504 is ADD. Step 140
When 6 is completed, the process proceeds to step 1407.

Next, a case where the call destination is a processing object will be described. In step 1409, the processing object whose name is DESTINATION is
It is checked whether it is registered in the processing object registration file 107. If registered, step 141
After setting the value FALSE to the variable EXIST with 0, the process proceeds to step 1407. If not registered, the value TRUE is set to the variable EXIST in step 1411, and the process proceeds to step 1412. In step 1412,
The contents of the call information management table 106 are checked, and the name 1
It is checked whether a call information management entry 1701 whose value of 703 matches DESTINATION is registered. If it has already been registered, the process proceeds to step 1407, and if it has not been registered, the process proceeds to step 1413. In step 1413, an entry 1701 is added to the call information management table 106. The value of the name 1703 of the entry to be added is DESTINATION, and the value of the state 1705 is ADD. Step 141
When 3 is completed, the process proceeds to step 1407.

In the following step 1407, the address 1706 of the memory of the callee information management area 1800 is acquired by referring to the call information management entry 1701 added to the end of the call information management table in step 1305 of FIG. In step 1408, an entry 1801 is added to the end of the callee information management area 1800 with reference to the address acquired in step 1407. Next, the data of the i-th entry 1601 is extracted with reference to the call information management table 118. The value of the line number 1603 is set in the line number 1803 of the entry 1801 to be added to the call destination information management area 1800, and the call type 16 is set in the call type 1804.
05 is set, the value of the callee name 1605 is set in the callee name 1805, and the call state 1 is set.
In 806, the value of the variable EXIST is set.

The description of the flowchart of FIG. 14 has been completed.

FIG. 19 shows a flowchart of step 1203.

FIG. 20 shows a list of template files and processing objects necessary for executing the Web server application execution system 119 on the display device 2.
1 shows a screen displayed at 01.

A process for displaying a list of necessary template files and processing objects on the display device will be described with reference to FIGS. 19 and 20.

First, in step 1901, 1 is set to a loop control variable i. If the value of i exceeds the number of entries in the call information management table 106 in step 1902, the process ends. Otherwise, step 19
Go to 03. In step 1903, the index 1702 of the call information management table 106 acquires the values of the name 1703, type 1704, and state 1705 of the template file or processing object with reference to the entry 1701 of i, and displays the acquired result on the screen 2008.
To be displayed. In the example of FIG. 20, 2004, 2005, 2
The portion denoted by 006 indicates the contents of the entries whose index 1702 values are 1, 3, and 6, respectively. In the display area 2001, the value of the state 1705 is DE.
If it is FAULT, nothing is displayed, and if the value is ADD, the character string "automatic addition" is displayed. Display area 20
In 02, a character string registered in the name 1703 of the template file or the processing object is displayed.
In the display area 2003, the value of the type 1704 is TEMPL.
If it is ATE, display the string "template",
If the value is OBJECT, a character string “processing object” is displayed. Subsequently, in step 1904, 1 is added to the value of the variable i, and the process returns to step 1902.

By performing the above-described processing, a list of template files and processing objects required for executing the Web server application execution system 119 can be displayed on the screen 2008.

FIG. 21 shows a flowchart of step 1204.

FIG. 22 shows a screen on the display device 201 for displaying information on unresolved calls included in the script program of the template file.

Referring to FIGS. 21 and 22, a description will be given of a process of displaying unresolved call information included in the script program of the template file on the display device.

First, at step 2101, 1 is set to the loop control variable i. If the value of i exceeds the number of entries in the call information management table 106 in step 2102, the process ends. Otherwise, step 21
In step 03, the address 1702 of the memory of the callee information management area 1800 is acquired by referring to the entry 1701 in which the value of the index 1702 of the call information management table 106 is i. Next, in step 2104, 1 is set to the loop control variable j. Then step 210
In step 5, the number of entries in the call information management area 1800 indicated by the address obtained in step 2103 is obtained.
If the value exceeds the acquired number of entries, the process proceeds to step 2109 to add 1 to the value of the variable i, and then returns to step 2102. If the value of j does not exceed the number of entries in the information management area 1800 in step 2105,
Proceed to step 2106. In step 2106, the call information management area 1800 indicated by the address obtained in step 2103 is referred to, and the value of the call state 1806 of the entry whose index 1802 is j is obtained. If the acquired value is NG, the process proceeds to step 2107,
If it is OK, the process proceeds to step 2108. Step 2
In 107, the index 1702 of the call information management table 106 obtains the value of the name 1703 of the call, and the index 1802 of the call information management area 1800 obtains the row number 1803 of the entry of j, the call type 1804, and the name of the call destination 1805. Then, the acquired value is displayed on the screen 2209. The display area 2201 displays a template file name 1703 and a line number 1803 in which an unresolved reference is described in the template file. The display area 2202 displays the name 1805 of the call destination. In the display area 2203, when the value of the call type 1804 is GENERATE, the character string “page generation” is displayed, and when the value is INCLUDE, the character string “include” is displayed, and the value is OBJEC.
In the case of T, a character string "object" is displayed. 221
A set of display items in the horizontal direction as shown in the example of No. 2 is called a display row. In FIG. 22, a display line 2204 indicates that “the template file TEMPLATE06.TMPL referred to by the page generation call described in the 15th line of the template file TEMPLATE02.TMPL does not exist”. The display line 2205 indicates “1 of the template file TEMPLATE02.TMPL”.
The processing object OBJECTB referenced by the processing object call described in the eighth line cannot be started. " The display line 2206 indicates “the template file TEMPLATE07.TMPL referred to by the include call described in the 21st line of the template file TEMPLATE03.TMPL.
Does not exist ". When the processing in step 2107 is completed, the value of the variable j is set to 1 in step 2108.
And returns to step 2105.

With the above processing, information on unresolved calls included in the script program described in the script program of the template file to be used can be displayed on the screen 2211 as a list.

FIG. 23 is a flowchart showing step 120 in FIG.
6 shows the flowchart of FIG.

First, in step 2301, the input device 202
Then, after inputting the path name of the file to be added in the input area 2207 on the screen 2209 displayed in step 2107, either the display area 2208 or the display area 2209 is designated by the screen pointing device, and the file to be added is designated. Is a template file or a processing object module file, and the display area 2210 is indicated by the screen instruction device. In step 2301, if the display area 2208 has been designated, the process proceeds to step 2306. If the display region 2209 has been designated, the process proceeds to step 2303. Step 23
In step 06, the file whose path name is specified in step 2301 is copied from the disk device and saved as the template file 108, and then the process proceeds to step 2307. In step 2307, it is determined whether to continue the operation. If the operation is to be continued, the process returns to step 2301. If not, the process ends. In step 2303, the file whose path name is specified in step 2301 is copied from the disk device and stored as the processing object module file 109. Subsequently, in step 2304, after inputting the name of the processing object from the input device 202, in step 2305, the name of the processing object and the path name of the module file in which the processing object is mounted are registered in the processing object registration file 107. Thereafter, the flow advances to step 2307.

In the above processing, the template file and the processing object necessary for executing the Web server application execution system 119 are stored in the development computer 10.
1 is stored in the disk device.

FIG. 24 is a flowchart showing step 120 in FIG.
7 shows a flowchart of FIG. First, at step 2401, 1 is set to the loop control variable i. In step 2402, it is determined whether or not the value of i exceeds the number of entries in the call information management table 106, and if it exceeds, the process ends. Otherwise, the process proceeds to step 2403. In step 2403, if the value of the type 1704 of the i-th entry 1701 of the call information management table 106 is TEMPLATE, the process proceeds to step 2404, and if the value is OBJECT, the process proceeds to step 2405.

In step 2404, step 2403
The name registered in the item 1703 in the entry 1701 obtained in step 1 is obtained, the template file 108 having the obtained name is transferred to the server computer 102, and the template file 11 which is a file on the disk device is obtained.
Save as 3.

In step 2405, step 2403
The name of the processing object registered in the item 1703 in the call information management entry 1701 acquired in the step is acquired, and in the processing object registration file 107,
If the value of the processing object name 1703 is
An entry 701 that matches the name acquired in step 03 is acquired, and a file name registered in the item 704 of the acquired entry 701 is acquired. Subsequently, step 2406
Then, the processing object module file 109 having the file name acquired in step 2405 is transferred to the server computer 102 and stored as the processing object module file 114 which is a file on the disk device. Further, in step 2407, step 2405
The name of the processing object acquired in step 1 and the name of the processing object module file 114 are
02 is registered as an entry of the processing object registration file 112 which is a file on the disk device.

As described above, the Web on the server computer 102
The template file 113 and the processing object module file 114 necessary for executing the b server application execution system 119 are stored in the disk device on the server computer 102 in a form that the Web server application execution system 119 can use.

The Web server application development system 101 described in the present embodiment transfers the template file 113 and the processing object module file 114 to the disk device on the same computer as the computer on which the Web server program 110 is running. It is something to store. However, the template file 113 and the processing object module file 114 are transferred and stored in the disk device on another computer which can be referred to from the server computer 102 via the network line 103, and are stored in the item 705 of the processing object registration file 112. Processing object module file 1
14 by registering the name of the computer to which
The web server application execution system 119 can be executed in the same processing procedure as in the present embodiment.

The Web server application development system 116 according to one embodiment of the present invention has been described above.

[0084]

According to the present invention, a program is started on a server computer in response to a request from a client computer,
The program reads a template file including a script program for generating display information of a Web page, interprets the script program, executes W
When developing a Web server application execution system for generating display information of an web page and disclosing it on a server computer, when a template file is specified from template files stored in a storage device of the development computer, the specified template file Is analyzed to identify all the template files referred to based on the script program and the implementation files of the processing programs, and transfer them to the file system of the server computer. This allows the user to access the Web
A server application execution system can be easily developed.

[Brief description of the drawings]

FIG. 1 shows a system configuration and an operation environment for realizing an embodiment of the present invention.

FIG. 2 is a hardware configuration of a computer device that realizes an embodiment of the present invention.

FIG. 3 is a flowchart of a process of a Web browser system 115 and a Web server application execution system 119;

FIG. 4 is a display example of a Web browser screen.

FIG. 5 is an example of HTML data.

FIG. 6 is a flowchart of an HTML data generation process 110.

FIG. 7 is a data structure of a processing object registration file 107;

FIG. 8 is a description example 1 of a template file.

FIG. 9 is a second description example of the template file.

FIG. 10 HTML generated from a template file
It is an example of data.

FIG. 11 is a display example of HTML data 1000 by a Web browser.

FIG. 12 is a flowchart of a template file debugging process 105;

FIG. 13 is a flowchart of a process 1202 for acquiring a calling relationship between a template and a processing object.

FIG. 14 is a sub-flowchart of the process 1202.

FIG. 15 is a data structure of an unanalyzed template table 117;

FIG. 16 is a data structure of a call information temporary storage table 118;

17 shows a data structure of a call information management table 106. FIG.

FIG. 18 is a data structure of a callee information management area 1800.

FIG. 19 is a flowchart of a process 1203 for displaying information of a template file and a processing object necessary for executing the Web server application execution system 119.

FIG. 20 is a display screen of a template file and information of a processing object necessary for executing the Web server application execution system 119;

FIG. 21 shows a process 120 for displaying unresolved call information.
4 is a flowchart of FIG.

FIG. 22 is a display screen of unresolved call information.

FIG. 23 is a flowchart of a process 1206 for correcting an unresolved call.

24 is a diagram illustrating a process 1 of transferring a template file necessary for executing the Web server application execution system 119 and a module file in which a processing object is mounted to an external storage device of the server computer 102.
207 is a flowchart of FIG.

[Explanation of symbols]

101: development computer, 102: server computer, 10
3: Network, 104: Client computer, 20
1 display device, 202 input device, 203 external storage device, 204 central processing device, 205 network device, 206 main storage device.

Claims (4)

[Claims] 1. A method for developing a server application operating in conjunction with a Web server using a computer device, comprising: storing a template file including a script program for generating display information in a file system on the server computer; When developing a server application that interprets and executes a script program included in a template file to dynamically generate display information, transfers the display information to a client computer, and outputs the display information to an output device of the client computer, (1) The template file is stored in a file system on a development computer, (2) information for specifying the template file is input from an input device, and (3) information for identifying the specified template file is stored in a storage device. Recorded in
(4) analyzing the script program included in the template file in which the information is recorded, identifying the template file referred to when interpreting and executing the script program and the processing program to be operated; And (6) recording the template file and information identifying the operated processing program in the storage device.
(7) specifying the template file to be referred to when the server application is executed and the processing program to be operated, based on the information recorded in the storage device; and (8) the specifying An application development method, wherein a template file and a file containing the specified processing program are stored in the server computer or in a file system on a computer that can be referred to from the server computer. 2. The output device according to claim 1, wherein said output device outputs said template file referred to when said server application is executed and information specifying said processing program to be operated, based on said information identified in step (4). An application development method characterized by outputting to an application. 3. The template file which is not stored in the file system of the development computer among the template files referred to at the time of execution of the server application specified in step (7) of claim 1. An application development method, wherein information for specifying a file is output to the output device. 4. A file on which the processing program is mounted among the processing programs referred to at the time of execution of the server application specified in step (7) of claim 1 is a file of the development computer. An application development method, comprising: outputting, to the output device, information that specifies the processing program that is not stored in a system in a bootable form.