JP2006268121A - Web application system and program for the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To dispense with the coding of the processing of extracting data necessary for each business object in a business layer. <P>SOLUTION: When receiving form data 26, a call data transfer object creation processing part 22 of a presentation layer 20 extracts only data necessary for a business object 31 to be called from data included in the form data 26 by reference to a business object definition file 24, and copies it into a data transfer object 28 to transfer it to the business layer 30. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a web application system, and more particularly to a web application separated into a plurality of layers.

  The Web application is software used on a communication network that distributes screen information from a server serving as an information source to a user terminal, such as the Internet or an intranet (see, for example, Patent Document 1 below).

  Further, for example, in Patent Document 2, a business application conventionally has an input / output control function with a client, a business processing function, and a database operation function, whereas an I / O layer, a business application layer, and a database layer In this way, the display format and data input / output part (that is, the part that the I / O layer processes) and the database operation part (that is, the database layer) Since the processing part) is separated from the business application layer, an invention is proposed in which the productivity of the business application layer is improved.

  FIG. 8 shows a configuration example of such a Web application. In this example, the web application 200 includes four layers: a client layer 210, a presentation layer 220, a business layer 230, and a persistence layer 240. The client layer 210 operates on the client terminal. The presentation layer 220, the business layer 230, and the persistence layer 240 operate on a server and are created in an object-oriented programming language called Java (registered trademark).

The client layer 210 corresponds to a Web browser and transmits a request to the presentation layer 220.
The presentation layer 220 transmits screen information for displaying the Web screen to the client layer 210 in response to a request from the client layer 210. The presentation layer 220 calls the business logic of the business layer 230 when any data input or command instruction is given by the user on the displayed Web screen and form data corresponding to the data is sent. At this time, the form data is passed to the business layer 230. The presentation layer 220 also performs processing such as client authentication at the time of login.

  The business layer 230 executes a business process (business logic) of the Web application in response to a request from the presentation layer 220 and transfers the processing result to the presentation layer 220. The persistence layer 240 stores data used by the business layer 230 for processing in the database 250 and persists it.

  As described above, in the Web application, the software operating on the server is divided into a function for displaying a screen on a Web browser and receiving an input, a function for executing business logic independent of the screen display, and a function specialized for database access. By dividing, the independence and versatility of each function is enhanced.

If the independence of each function is increased, application development and modification can be performed for each function, and the work becomes more efficient. For example, by separating the presentation layer and the business layer, programs of these layers can be efficiently developed, and reduction of development costs and securing of quality can be expected. In particular, in reality, the business logic itself is hardly changed. On the other hand, the change of the screen as the user interface is performed relatively frequently. It can be expected that there will be no need to modify the business layer depending on changes.
JP 2003-15870 A JP 2002-373148 A

  Here, as described above, the presentation layer 220 passes form data when calling the business logic of the business layer 230, but the business logic does not require all the information of the form data. For this reason, the business layer 230 has to perform a coding operation for processing to extract only the data required by the business logic from the form data. This was very time consuming. In addition, since the business layer 230 normally performs processing specialized for each system, coding work is required for each system. Furthermore, if the content of the form data is changed due to the change of the screen or the like, coating must be performed each time. For this reason, there was a problem that it would be against the above expectations.

  If at least the presentation layer 220 and the business layer 230 are configured to be executed by separate Java virtual machines, and data transfer between the Java virtual machines is performed using RMI (Remote Method Invocation), the above business When the layer 230 returns the processing result to the presentation layer 220, there is a problem that there is data that cannot be transferred due to restrictions on RMI communication. In particular, when there is an instance of the mapping class in the response from the business layer 230, if there is data that cannot be transferred, it cannot be transferred to the presentation layer 220 as it is. Conventionally, it has not been possible to transfer such an instance of the mapping class to the presentation layer 220 side.

  The object of the present invention is to extract only the data required by the business logic when the presentation layer calls the business logic in the Web application system separated into at least the interface layer with the client and the layer that executes the business logic. Or providing a Web application system, its program, etc. that can be passed to the presentation layer side even when a mapping class instance is included in the response by the business layer.

  The application server according to the present invention includes an application server including a first virtual machine that interfaces with a client and a second virtual machine that executes various business objects. Definition storage means for storing the identification name of the data necessary for processing the business object in association with each business object, and allowing the client to display an arbitrary screen and inputting arbitrary data. Screen input / output control means for receiving a request including form data corresponding to the request, and when calling the business object corresponding to the request, the identification name of each data required by the calling business object is acquired from the definition storage means. Of the data included in the form data, Alias is configured to have a call data transfer control means for transferring only the data that matches one of the acquired identification name to said second virtual machine.

  The application server extracts only necessary data in the first virtual machine and passes it to the second virtual machine even if there is data that is not required in the business object in the form data. Therefore, there is no need to perform coding for the process of extracting necessary data on the second virtual machine side.

  Alternatively, the application server of the present invention is an application server having a first virtual machine that interfaces with a client and a second virtual machine that executes a business object, wherein the second virtual machine is the business object When various response parameters are passed from as a processing result, if there is an object of the mapping class in it, only the transferable data is extracted from the object and transferred to the first virtual machine And the first virtual machine is configured to have mapping class restoration processing means for restoring the transferable data transferred by the response data transfer means to restore the shape of the mapping class object. .

  In the application server, the second virtual machine uses, for example, an OR mapping technique, and a mapping class object is returned to the first virtual machine as a processing result. However, when the data transfer between the first virtual machine and the second virtual machine is serialized, such as RMI, for example, it cannot be serialized (that is, cannot be transferred) to the mapping class. Since the data is included, the mapping class cannot be transferred as it is. Thus, first, on the second virtual machine side, only transferable data is extracted from the mapping class object and transferred to the first virtual machine. The first virtual machine restores this transferable data to a usable state as a mapping class. Data that cannot be transferred is basically data that is not necessary on the first virtual machine side.

  According to the web application system, the program thereof, and the like of the present invention, in a web application system in which at least the presentation layer and the business layer are separated, when the presentation layer calls the business logic, only the data required by the business logic is obtained. It can be extracted and passed, eliminating the need for coding work in the business layer.

  Alternatively, even if a mapping class instance is included in the response by the business layer, it can be transferred to the presentation layer, and the mapping class instance is restored from the data transferred in the presentation layer. Thus, the mapping class can be substantially acquired as the processing result in the presentation layer, and the processing result can be displayed using this.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a functional block diagram of the Web application system of this example.
The first feature of the present invention relates to a call of business logic (business object) of the business layer 30 from the presentation layer 20 shown in FIG. The second feature relates to the return of the processing result from the business layer 30 to the presentation layer 20.

  The presentation layer 20 and the business layer 30 are on different Java virtual machines. The presentation layer 20 and the business layer 30 are mounted on the application server 2. In FIG. 1, two layers 20 and 30 are implemented on one server 2, but each layer 20 and 30 may be implemented on a separate server. The client layer 10 is mounted on the client machine 1. The database 40 is in a database server (not shown). The client machine 1, the application server 2, and the database server are connected to some network (for example, a LAN) and can communicate with each other.

  In FIG. 1, a screen input / output control object 21 in the presentation layer 20 basically performs input / output control of a screen displayed on the Web browser 11 of the client layer 10. The screen input / output control object 21 displays some input screen on the Web browser 11 of the client layer 10 and allows the user of the client machine 1 to input arbitrary data according to the input screen. Also, for example, commands such as update and search are input. In response to this, when a request (form data 26 or command) is sent from the client machine 1, the screen input / output control object 21 passes the form data 26 and the like to the calling data transfer object creation processing unit 22.

  When the call data transfer object creation processing unit 22 receives the form data 26, the call data transfer object creation processing unit 22 responds to a request from the client by referring to the business object definition file 24 stored in the storage device 23 (hard disk, memory, etc.). Only the data required by the business object 31 to be called is copied to the data transfer object 28 and passed to the business layer 30 side. This is the first feature.

  Note that RMI (Remote Method Invocation) is used for communication between the layers 20-30, that is, communication between Java virtual machines. As is well known, RMI allows you to call methods on objects that run on other Java virtual machines and pass parameters and return values. In particular, using Java RMI has an advantage that, for example, a derived class can be passed as an argument of a base class or an object itself can be converted into a byte stream, so that the object can be passed very easily.

  On the business layer 30 side, the called business object 31 executes a predetermined process and acquires the mapping class 33 of the database 40. Note that although it is actually an “instance (object) of a mapping class”, it may be abbreviated as “mapping class” in this description. Although omitted in FIG. 1, actually, as shown in FIG. 2, the persistence layer 214 accesses the database 202 and creates a database mapping class 33 (244) as a processing result.

  The second feature relates to processing for returning the mapping class 33 to the presentation layer 20 and displaying the processing result on the Web browser 11 of the client. That is, first, the mapping class 33 cannot be transferred to the presentation layer 20 as it is because of communication restrictions. That is, the mapping class 33 includes data that can be transferred and data that cannot be transferred. That is, the transfer of the data transfer object between the business layer 30 and the presentation layer 20 is performed by so-called “object serialization” (serialization) for communication by RMI as described above. Object serialization is to encode an object and the object referenced from it into a byte stream. The mapping class 33 may include data that cannot be serialized, which is the data that cannot be transferred. The data that can be object-serialized in the mapping class 33, that is, the data that can be transferred is known to be the property name and value.

  Therefore, first, the business object 31 that has acquired the mapping class 33 passes a predetermined response parameter including the mapping class 33 to the response data transfer object creation processing unit 32. The response data transfer object creation processing unit 32 transfers the response parameter to the presentation layer 20 by RMI or the like. When the mapping class 33 is included in the response parameter, Only the transferable data is extracted and transferred to the presentation layer 20.

  In the presentation layer 20, the mapping class restoration processing unit 25 restores the transferable data to a usable state as a mapping class (generates (restores) the mapping class 27), and performs this on the screen input / output control. Pass to object 21. Thus, when viewed from the screen input / output control object 21, the mapping class is returned as the processing result. Then, the processing result is displayed on the Web browser of the client. However, the mapping class 27 is not a complete restoration of the contents of the mapping class 33.

  The calling data transfer object creation processing unit 22, the mapping class restoration processing unit 25, and the response data transfer object creation processing unit 32 execute a predetermined application program stored in the storage device 23 of the application server 2. This is realized by reading and executing a CPU (not shown) or the like.

FIG. 2 shows a basic configuration example of the entire Web application according to the features of FIG.
The configuration shown in FIG. 1 is based on the basic configuration shown in FIG. The various functional parts are provided.

  2 includes a client layer 111, a presentation layer 112, a business layer 113, and a persistence layer 114. The client layer 111 has a Web browser 121 that operates on the client machine 1. The presentation layer 112, the business layer 113, and the persistence layer 114 operate on the application server 2 connected to the client machine 1 via a communication network (LAN or the like). The client layer 111, the presentation layer 112, and the business layer 113 correspond to the client layer 10, the presentation layer 20, and the business layer 30.

  The presentation layer 112 is executed by a single Java virtual machine, and the business layer 113 and the persistence layer 114 are executed by the same Java virtual machine. The Java virtual machine of the presentation layer 112 and the Java virtual machine of the business layer 113 and the persistence layer 114 may be on the same application server or on different application servers. The database 102 corresponds to the database 40 in FIG. 1 and is on a database server (not shown). This database server is connected to an application server or the like via a communication network.

  The presentation layer 112 includes an application server 131 that uses a Java Server Faces (JSF) 132 as a basic technology for presentation. The JSF 132 is a web application interface framework for the purpose of separating business logic and presentation design.

  The JSF 132 is a tool capable of developing a Web application with a graphical user interface (GUI), and can be arranged on a screen form by dragging and dropping screen components constituting the Web application with a mouse. In addition, a managed bean 133 corresponding to an event handler can be described for each component.

  The business layer 113 executes processing (business logic) related to business requirements of the system. The business layer 113 maps the processing request from the presentation layer 112 to a business logic implementation class (business object 142). The business layer 113 includes a business logic container 141 that generates a business object 142, and the business object 142 executes predetermined business logic. For example, POJO (Plain Old Java Object) is used as the business object 142. This eliminates the need for a special test environment when developing and testing the business object 142, and improves reusability.

  When receiving a processing request from the presentation layer 112, the business logic container 141 generates a business object 142 corresponding to the processing request and requests a business process. When the business process is completed, the business object 142 is discarded. When a plurality of processing requests arrive at the same time, a plurality of business objects 142 are generated simultaneously.

  The persistence layer 114 has an OR mapping 145 for accessing the database 102. The OR mapping 145 maps the data representation of the Java object model to a relational data model having a SQL (Structured Query Language) based schema. The OR mapping 145 generates a data access object (DAO) 143 from the schema of the database 102.

  When the application server 131 receives a request from the Web browser 121, the application server 131 notifies the managed bean 133 of the request, and the managed bean 133 calls the business logic container 141. In response to this, the business logic container 141 generates a business object 142.

  The generated business object 142 acquires a DAO 143 for performing database access, and acquires a mapping class 144 corresponding to the table of the database 102 using the DAO 143.

  The business object 142 returns a predetermined response parameter including the acquired mapping class 144 to the presentation layer 20 as a processing result. Based on the received processing result, the managed bean 133 in the presentation layer 20 notifies the Web browser 121 of the processing result and displays it. The managed bean 133 corresponds to the screen input / output control object 21 in FIG.

  Apart from such a Web application 101, applications 103 and 104 having no presentation layer are also provided. Unlike the Web application 101, the applications 103 and 104 are often of a type that starts processing at a set time or always executes processing.

  The application 103 includes a business layer 151 and a persistence layer 152. The business layer 151 has a batch process 153, and the persistence layer 152 has an OR mapping 154. The application 104 includes a business layer 161 and a persistence layer 162. The business layer 161 has a batch process 163, and the persistence layer 162 has an OR mapping 164.

  The batch processes 153 and 163 perform, for example, cooperation processing with other servers, data processing executed at night, communication processing with hardware, and the like. It is also possible to receive event notifications from the business object 142 and other batch processes, and to notify events to other batch processes.

Hereinafter, the first and second features shown in FIG. 1 will be described in more detail with reference to FIG. 1 and FIG.
First, the first feature will be described. Although not shown in particular, here, as an example, it is assumed that the employee information management screen is displayed on the browser 11, and this screen includes six items of employee number, name, address, age, department name, and special notes. It shall be. For example, identification names User_id, Name, Address, Age, Section, and Comment are assigned to each of these items. The form data 26 includes, for example, as shown in FIG. The name is associated with the data input by the user or the data displayed on the screen. Note that all of the above six items are not necessarily input items, and there may be items that are simply displayed. Therefore, for example, when “search” is executed and a part of the above six items is input as a search key, the business object 31 that executes the search only needs data as the search key. Other items will not be necessary.

  Further, the business object definition file 24 stores an identification name of data necessary for executing the business object in association with each business object. FIG. 3B shows a definition example related to a business object that requires only User_id, Name, and Section, compared to the example shown in FIG. These correspond to, for example, the search key.

  FIG. 4 shows a flowchart of processing executed by the call data transfer object creation processing unit 22. Hereinafter, this flowchart process will be described using the example shown in FIGS. 3 (a) and 3 (b).

  After the screen input / output control object 21 receives the form data as shown in FIG. 3A and stores it in a memory or the like, the call data transfer object creation processing unit 22 receives an arbitrary one from the stored form data. The identification name of one data is acquired (step S11). Further, a list of identification names of data required by the business object to be called (for example, FIG. 3B) is acquired from the business object definition file 24 (step S12). It is determined whether or not there is an acquired identification name (step S13). If there is (step S13, YES), data corresponding to the identification name acquired in step S11 is acquired from the form data 26 to obtain a data transfer object. 28 is copied (step S14). If there is no copy (step S13, NO), copying is not performed.

The above process is repeated until all the data in the form data 26 is executed.
If the above process is described using the examples shown in FIGS. 3A and 3B, first, the identification name “User_id” is acquired in step S11, and the identification name list shown in FIG. Are “User_id”, “Name”, and “Section”, and since there is “User_id”, the determination in step S13 is YES, and the identification name “User_id” and its data “1234” are copied to the data transfer object 28. . Similarly, since the next identification name “Name” exists in the list of identification names shown in FIG. 3B, the identification name “Name” and its data “Taro Yamada” are copied to the data transfer object 28. The same applies to the identifier “Section”.

On the other hand, since the identification names “Address”, “Age”, and “Comment” do not exist in the list of identification names, the data is not copied to the data transfer object 28.
Then, the data transfer object 28 is transferred to the business layer 30 side by RMI or the like.

  As described above, according to the first feature, when the business object 31 of the business layer 30 is called in the presentation layer, only the data required by the business object 31 can be extracted and passed. There is no need to perform coding work that takes time and labor at the layer 30. Since the business layer 30 is usually specialized for each system, the business layer 30 needs to be coded for each system. In addition, since the business logic of the business layer 30 is usually not changed much, the coding work of the business layer 30 should not be performed much after the layer construction. However, if the form data changes due to changes in the screen, etc., it is necessary to redo the coding work for the process of extracting the necessary data. On the other hand, according to the first feature, the presentation layer 20 can be corrected. Further, since the presentation layer 20 is not specialized for each system, it is highly versatile.

Next, the response data transfer object creation processing unit 32 and the mapping class restoration processing unit 25 according to the second feature will be described below.
FIG. 5 is a processing flowchart of the response data transfer object creation processing unit 32.

FIG. 6 is a processing flowchart of the mapping class restoration processing unit 25.
First, when the called business object 31 returns a response parameter as a result of executing the process, the response data transfer object creation processing unit 32 executes the process shown in FIG. 5 for each response parameter. . That is, first, the type is acquired from the response parameter to be processed (step S21). Then, it is determined whether or not the response parameter is an object inheriting the mapping class type (step S22). As a specific example, for example, if “hibernate” (http://www.hibernate.org/) is used in the persistence layer 214, “net.sf.hibernate.Lifecycle” This is to determine whether the object is inherited (extends). If the object inherits the mapping class type (step S22, YES), all the property names and values that can be transferred are acquired from this object, and these are used for mapping class transmission. The object is copied to the object, and this mapping class transmission object is stored in the data transfer object 34 (step S23). If it is not an object of the mapping class (step S22, NO), this response parameter is copied to the data transfer object 34 (step S24). The mapping class transmission object is given a type indicating that this is a mapping class transmission object. In addition, since the data that can be transferred is only the property name and value, and all other data cannot be transferred, a specific example of data that cannot be transferred is not particularly shown.

Then, the data transfer object 34 is transferred to the presentation layer 20 side by RMI.
The mapping class restoration processing unit 25 that has received the data transfer object 34 executes the process shown in FIG. 6 for each response parameter stored in the data transfer object 34. That is, the type of response parameter to be processed is acquired from the data transfer object 34 (step S31). Then, based on this type, it is determined whether or not the object is a mapping class transmission object (step S32). When the response parameter to be processed is the mapping class transmission object (step S32, YES), all the data (that is, the property name and value) stored in the mapping class transmission object are acquired and used. A new mapping class is generated (restored) (step S33).

  However, even if the data is restored, the data that cannot be transferred is not restored. The generated mapping class includes only the property name and value, which are the transferable data, and is formally in the form of a mapping class in which other data is empty. That is, as described above, it is restored to a state where it can be used as a mapping class. However, since the data necessary for the screen input / output control object 21 (data necessary for displaying the processing result on the Web browser 11) is usually only the property name and value, there is no particular problem. Nor does it have to be restored to the mapping class. However, in this system, as shown in FIG. 2, since the OR mapping technique is adopted for the persistence layer 114, it is natural that the response is passed in the form of a mapping class. Further, the mapping class corresponds to, for example, a table in the database 102. If the mapping class is used, a process for displaying the table can be easily performed. Therefore, it is desirable to restore to a state that can be used as a mapping class.

  Then, the generated mapping class is passed to the screen input / output control object 21. If the response parameter to be processed is not a mapping class transmission object (NO in step S32), the response parameter is passed to the screen input / output control object 21 as it is.

As a result, the screen input / output control object 21 displays the processing result on the Web browser 11.
As described above, according to the second feature, even when there is a mapping class in the response from the business layer 30 and it cannot be transferred to the presentation layer 20 side as it is, it can be transferred. Furthermore, by restoring this to the form of the mapping class and passing it to the screen input / output control object 21, it is possible to display the processing result in a form that makes use of the OR mapping technique.

  Finally, FIG. 7 shows a specific description example of the business object definition file 34 in the business layer 30 of FIG. The business object definition file 34 itself is not directly related to the above-described characteristics. Conventionally, in the business layer 30, for each business object, the parameter type that can be handled by the business object has been defined. It was done.

  As shown in FIG. 7, there are a description part common to all business objects 31 and a definition description part for each business object 31. In the definition description part for each business object 31, the type (type) of the parameter (response parameter) that can be handled by the business object 31 is defined. In the illustrated example, for example, an Integer type, a String type, an array type, and the like are defined. In the case of a business object 31 that can handle a mapping class as a response parameter, naturally, the type (type) of the mapping class is defined, and the processing of FIG. 5 basically targets such a business object 31. Yes. In Java and the like, an instance (object) of a mapping class inherits the type (type) of the mapping class.

  Thus, as described above, in the processing of steps S21 and S22 in FIG. 5, if the response parameter type to be processed is the mapping class type, the determination is YES, and the processing of step S23 is performed. Will be done.

  The business object definition file 24 and the business object definition file 34 in FIG. 1 show the same contents (input parameters and response parameters are defined together). If the presentation layer 20 and the business layer 30 are configured to be mounted on different server machines, the definition file 34 is created by copying the definition file 34, but the contents are the same.

It is a functional block diagram of the Web application system of this example. A specific configuration example of the entire Web application according to the feature of FIG. 1 is shown. (A) is a form data, (b) is a figure which shows the specific example of a business object definition file. It is a process flowchart figure by the data transfer object creation process part for a call. It is a process flowchart figure of the data transfer object creation process part for a response. It is a process flowchart figure of a mapping class restoration process part. It is a specific example of contents described in a business object definition file. It is a structural example of the conventional web application.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Client machine 2 Application server 10 Client layer 11 Web browser 20 Presentation layer 21 Screen input / output control object 22 Calling data transfer object creation processing unit 23 Storage device 24 Business object definition file 25 Mapping class restoration processing unit 26 Form data 27 Mapping class 28 Data Transfer Object 30 Business Layer 31 Business Object 32 Response Data Transfer Object Creation Processing Unit 33 Mapping Class 34 Data Transfer Object 40 Database 101 Web Application 102 Database 103, 104 Application 111 Client Layer 112 Presentation Layer 113 Business Layer 114 Zokuka layer 121 Web browser 131 application server 132 JSF (Java Server Faces)
133 Managed Bean
141 Business Logic Container 142 Business Object 143 Data Access Object (DAO)
144 Mapping class 145 OR mapping 151 Business layer 152 Persistence layer 153 Batch process 154 OR mapping 161 Business layer 162 Persistence layer 163 Batch process 164 OR mapping

Claims (6)

In an application server having a first virtual machine that interfaces with a client and a second virtual machine that executes various business objects,
The first virtual machine is
Definition storage means for storing in advance an identification name of data necessary for processing the business object in association with each business object;
Screen input / output control means for displaying an arbitrary screen on the client and performing arbitrary data input, and receiving a request including form data according to the data;
When calling a business object in response to the request, an identification name of each data required by the calling business object is acquired from the definition storage unit, and among the data included in the form data, the identification name is the Call data transfer control means for transferring only data that matches any of the acquired identification names to the second virtual machine;
An application server comprising: In an application server having a first virtual machine that interfaces with a client and a second virtual machine that executes a business object,
When various response parameters are passed as processing results from the business object, the second virtual machine extracts only data that can be transferred from the object if there is an object of the mapping class in the second virtual machine. Response data transfer means for transferring to one virtual machine,
The application server, wherein the first virtual machine has mapping class restoration processing means for restoring the transferable data transferred by the response data transfer means to restore the shape of a mapping class object.   3. The application server according to claim 2, wherein the data that cannot be transferred in the mapping class object is data that cannot be serialized.   The second virtual machine has a persistence layer that generates a mapping class by accessing a database by an OR mapping technique, and the business object acquires the mapping class. The application server according to claim 2. On the computer,
In the first virtual machine in a web application having a first virtual machine that interfaces with a client and a second virtual machine that executes various business objects,
A definition storage function that stores in advance an identification name of data necessary for processing the business object in association with each business object,
A screen input / output control function for displaying an arbitrary screen on the client and performing arbitrary data input, and receiving a request including form data corresponding thereto; and
When a business object corresponding to the request is called, an identification name of each data required by the calling business object is acquired from the definition storage function, and among the data included in the form data, the identification name is the A call data transfer control function for transferring only data that matches one of the acquired identification names to the second virtual machine. On the computer,
In a web application having a first virtual machine that interfaces with a client and a second virtual machine that executes various business objects,
When various response parameters are passed as processing results from the business object to the second virtual machine, if there is an object of the mapping class in it, only the transferable data is extracted from the object and the second virtual machine is extracted. Realize response data transfer function to transfer to one virtual machine,
A program for causing the first virtual machine to realize a mapping class restoration processing function for restoring the transferable data transferred by the response data transfer function to restore the shape of a mapping class object.

Images