KR20080013324A - Presentation method for web applications and web application development system using the same - Google Patents

Abstract

A presentation method for web applications and a web application development system using the presentation method are provided to respectively manage a handler corresponding to a program source of a web application and a screen corresponding to a design of an image to facilitate the development of new web applications and maintenance of web applications and minimize reload of images to reduce a loading time. A web plus engine executed in a client generates a common document at the request of a web browser(S2). When the web plus engine requests a web server to provide a handler of a corresponding image(S3), the web server provides the handler(S4). When the web plus engine requests the web server to provide a screen used for the handler(S5), the web server provides the screen(S6). The web plus engine responds to the web browser by using the handler and the screen. When an event is generated and data is required(S9), the web plus engine requests the web server to provide data, the web server executes a predetermined business logic and provides data obtained as the execution result as an xml file(S16). The web plus engine provides an html file including data updated by parsing the xml file to the web browser(S18).

Description

PRESENTATION METHOD FOR WEB APPLICATIONS AND WEB APPLICATION DEVELOPMENT SYSTEM USING THE SAME}

1 is a schematic diagram illustrating a presentation concept for a conventional web application;

2 is a schematic diagram illustrating a presentation concept for a web application according to the present invention;

3 is a configuration diagram of a presentation layer shown in FIG. 2;

4 is a flowchart illustrating an operation procedure of the webplus engine shown in FIG. 2;

5 is a flow chart illustrating the overall process delivered between a browser and a server in accordance with the present invention;

6 is a structural example of a common document according to the present invention.

* Explanation of symbols for main parts of the drawings

100: Client 110: Web Browser

120: WebPlus Engine 200: Web Server

210: Presentation tier 211: WebPlus Viewer Manager

212: WebPlus Data Controller 213: Handler

214: Screen 215: Tool part

220: business logic 300: Ministry of Resources

The present invention relates to a web interface technology as a solution for developing a web application, and in particular, to a general user who accesses a web application through a world wide web (WWW). It is a solution that specifies how to present a page. It is a technology for presentation method and web application development system that can express web application at the level of desktop application through connection with solidly constructed business logic.

In general, the Internet has grown rapidly in recent years as computers and networks have spread, and have evolved into a worldwide sophisticated network of computer systems linked together by web pages that collectively constitute the "world wide web" (or WWW). On individual PCs that want to access the WWW, users typically use software known as a "web browser." The web browser makes a connection to another computer known as a web server on the WWW, receives information from the web server, and displays it on the user's computer. The information displayed to the user is composed of pages implemented using a dedicated language, commonly referred to as Hypertext Markup Language (HTML). HTML-enabled web browsers have been made available for almost every computer system on the market, allowing almost anyone with access to the computer and modem to access the WWW. The rapid growth and proliferation of computer users accessing the WWW has inevitably led to the remarkable development of computer hardware and software.

1 is a schematic diagram illustrating a presentation concept for a conventional web application, in which a web browser 11, a web server 20, and a database 30, which are clients 10, are shown.

Referring to FIG. 1, the web server 20 includes at least the presentation layer 21 and the business logic layer 22. In the conventional web model, the presentation layer 21 is a screen design and a program source. It is implemented in the same file without being separated. In the conventional web model, when the browser 11 requests a web document according to the HTTP protocol, the presentation layer 21 of the web server requests the business logic 22 to process the data as necessary, and then receives the data. The web standard document consisting of and CSS was generated and responded to the browser 11, and the browser 11 outputted the screen.

However, as the popularity of WWW is rising and the technology is rapidly developing accordingly, various incidental problems are also growing together. The problems of the current web application are as follows from the user side, web application operator side, and web developer side, respectively.

Problem on the user side

Until now, the structure of a web application is that when a user connects to a specific web application on the WWW and the user requests a specific operation on the web page, the presentation layer 21 of the web server processes the business logic 22 as needed. Output data that can be requested to complete the task, receive the data, and send it to the user's web browser (including static HTML pages that don't change the content of the page, or can be dynamically determined to be inserted into the output data). And send it to the user's web browser, which will interpret it and print it to the user's monitor screen. In other words, when the user's request came, the user had to wait until the web server completed all the processing and sent the output data to the user's web browser.

Therefore, while the user waits, the connection is suddenly disconnected or the user waits for a certain time depending on the variable environment such as the speed of the network or the process of the web server.

In addition, when a change of data of a specific part occurs in a web page that is currently connected at the request of a user, in order to reflect this in a web browser, the entire data such as HTML to be displayed on the screen is not received conventionally only the information of the changed part is received. As it receives the transmission from the web server, it causes a load on the web server and the network, and afterwards, the output data received by the web browser is reconfigured and displayed on the user's monitor, so that a dull and unreliable web application such as flickering on the monitor is displayed. I had to meet.

Due to these limitations, in order to handle more diverse and complex tasks, it was necessary to install and use a desktop application program through a cumbersome task of sometimes installing a new installation process on the user's computer. However, this has a fundamental problem that the connection itself is not possible on a computer without the corresponding desktop application program installed.

Web application operator / company side

As mentioned above, the structure of a web application up to now, which has to receive a large number of user requests through the WWW, process all the requests on a web server, generate output data for it, and respond to each user, is a massive and massive web application system. Was achieved. However, as more and more users connected, the problem of load on the web server was again introduced. In order to solve this problem, various development methodologies and better computer system concepts have been derived from efforts for new development and expansion of another system, and the development of hardware and software has been made accordingly. However, this progressed in different forms of development by hardware, software, computer and platform. These essentially different hardware systems typically use completely different operating systems. Because of these different hardware and software systems, porting a separate web platform to a given web application usually requires a completely new system development effort. This creates and operates web applications with the same content on different hardware and software platforms, resulting in an unproductive situation that results in significant time and high costs.

In the meantime, desktop applications have been developed and managed separately due to the limitations of the traditional web application structure for implementing complex business tasks on the web. As a result, two types of applications, which are divided into web applications and desktop applications, have to be maintained. Therefore, it is difficult to maintain and increase costs.

In addition, since the desktop application was only available through a separate installation process on the user's computer, the connection itself was not possible unless the desktop application program was installed. So, in order to solve this problem, efforts have been made to convert desktop applications to web applications. However, the efforts to date are insufficient to convert all the complex and various functions of desktop applications to web applications. As a result, unsatisfactory transitions are being made to remove some of the functionality of the desktop application and to develop the web application by selecting only the parts that can be converted to the web application.

Web application developer (programmer, web designer) aspect

In the current system environment, where new interfaces are configured for different new web applications, developers must relearn new programming methods and pay extra effort and money to run them. Thus, although many web applications today can be accessed through the World Wide Web, the differentiation of these various web application platforms means that web application developers must spend time learning new platform environments and how to operate them, reducing their motivation to develop. There is a problem that reluctance to introduce new applications.

HTML is a well-known language that can be used by most computer systems on the market. In addition, HTML is a fairly well-controlled and standardized language, so that features of new software applications can be added if they are developed and supported by HTML. However, many web application programs on the WWW rarely construct web pages using simple HTML due to invocation of business logic and connections to databases due to frequent requests for dynamic data information.

As a result, most web applications develop a web application program using a server scripting language suitable for each system platform. Examples include Java Sever Pages (JSP), Active Server Pages (ASP), and Hypertext Preprocessor (PHP).

The server script language as described above has a work structure that adds programming according to the syntax of each server script to express dynamic data of a database in conjunction with business logic on HTML representing static data.

In other words, when a web designer generally constructs a web page in HTML and constructs the content, the programmer takes over and inputs an additional source into the file using each server script to form a connection with the business logic. . This makes it possible to implement a dynamic user interface (UI) with dynamic changes of web pages and various contents, but the web designer can work with the same single file and the programmer can receive it and work on it. There is a problem that it takes a long time to develop because it can not be performed at the same time. In addition, when the development of the primary web application program is completed and the web page configuration is changed again according to the requirements of the new user, the designer receives a file already implemented in the server script language and adds or deletes new HTML. If the design of the server script language is unfamiliar to the designer due to the grammar of the server script language, the programmer must take over and modify the server script language again. Sometimes.

In addition, programmers can write programming to present a response to a web browser in response to a specific request, such as a user's event or action, that occurs within a web page. Several types of script (VB Script, JScript) or server script We had to implement it in a language. As a result, long programming time is required to implement a source for a response according to each request, and when a change in the request occurs, a source for another response must be implemented to maintain a difficult problem. .

As described above, in the conventional web model, since the presentation document's web document is not divided into design and source, it is difficult to reuse or maintain code, and it takes a long time to develop a new web application.

The present invention has been proposed to solve the above problems, and manages the design and the source in a completely independent file of the screen and the handler according to the invention, and the components and properties belonging to the already developed by the invention ( It is easy to develop and maintain by using the feature that the implementation of the function is completed without the direct programming of the developer through the declaration of Attribute, and after the screen is loaded, it is possible to recall and express only the specific part of data that is necessary. It is an object of the present invention to provide a presentation method for a web application and a web application development system using the same, which can minimize reload of a screen and improve response speed.

In order to achieve the above object, the method of the present invention is a method for providing a web application in a client-web server structure, wherein the web plus engine executed in the client is a common document according to a request of a web browser. Generating a first step; A second step of the web server providing the handler when the web plus engine requests the handler of the corresponding screen; A third step of providing the screen by the web server when the web plus engine requests a screen to use for the handler; A fourth step in which the web plus engine responds to a web browser using the handler and the screen; A fifth step in which the web plus engine requests data from the web server when an event is generated and the data is requested, the web server executing predetermined business logic and responding the result data to an xml file; And a sixth step of the web plus engine parsing the xml file to provide an html file including the updated data to the web browser.

In addition, in order to achieve the above object, the system of the present invention, a web environment of a client-server structure, the web browser running on the client; Upon initial access, the server is loaded from the server to the client side, and the server requests a handler and a screen of the screen according to the request of the web browser, and then parses a handler composed of xml and maps the screen with the screen. ) Interprets the information, generates a basic html document to be output to the web browser, outputs it to the web browser, and if new data is needed according to the event, communicates to the server in a synchronous / asynchronous manner, receives xml data, and outputs it to the web browser. a web plus engine for updating html information and outputting the html information to the web browser; A presentation unit which is executed in the server and provides a handler and a screen according to a request of the web plus engine while managing documents divided into handlers and screens; And a data controller running in the server and providing a connection with business logic that processes a specific service and provides a result according to a request of the presentation unit.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

2 is a schematic diagram illustrating a presentation concept for a web application according to the present invention, FIG. 3 is a detailed configuration diagram of the presentation layer shown in FIG. 2, and FIG. 4 is an operation of the webplus engine shown in FIG. A flowchart showing the procedure.

An environment for implementing a web application according to the present invention has a structure of a client 100 and a web server 200, as shown in FIG. The client 100 is composed of a conventional web browser 110 and a web plus engine 120 according to the present invention, and the web server 200 includes a handler 213 corresponding to a program source for a web document according to the present invention. The presentation layer 210 and the normal business logic 220 (business logic, which are divided into screens 214 corresponding to the design of the screens) (the business logic is not the result of the above-described invention, but the conventional business logic already implemented. It means.). The business logic 220 is connected to a database management system (DBMS) 300 or another resource 300 such as CRM / ERP or LDAP according to the nature of the application, processes the service required by the application, and then presents the result. To the layer 210. The web plus engine 120 is automatically loaded initially and executed on the client side when the client 100 accesses the web server 200 to which the present invention is applied.

In addition, the presentation layer 210 according to the present invention includes a web plus viewer manager 211, a web plus data controller 212, and a tool unit 215, as shown in FIG. 3. 211 is composed of a screen 214, which constitutes a screen of a web application, and a handler 213 that connects data and controls a screen as an element of a logic of a web application. The handler 213 is configured to transfer a data set 213-1, a transfer 213-2, a config 213-3, a built-in function 213-4, and an Ajax-based component library 213-5. The webplus data controller 212 is connected to the business logic 220 and relays data to be output to a corresponding web page. Mapping) 212-2. The tool unit 215, which performs an auxiliary function, handles handler automatic completion, logging, and the like.

Referring to FIG. 3, screen 214 inserts an HTML tag for UI presentation, defines an ID with information that is mapped to a handler, and allows the screen to be reused by other handlers. . These screens can accept files in all ServerScript language formats such as html, jsp, asp, php, and so on.

The handler 213 is implemented in XML to define the screen UI component as an element of XML, define ID and XPATH for mapping and data binding with the screen, and Using attributes and built-in functions 213-4, you can reuse the handlers and screens using inheritance and containment relationships. These handlers 213 are Dataset 213-1, Transfer 213-2, Config 213-3, built-in function 213-4, Ajax-based component library 213-5. As the logic of the web application, the screen 214 connects data and controls the screen 214 to perform a practical function. Component library (213-4) includes UI CONTROLS, UI COMPONENT, DATA MANAGE, BEHAVIORS, TOOLS, etc., UI CONTROLS provides organic control properties between UI components, UI COMPONENT provides a rich screen interface, and DATA MANAGE. Provides efficient data synchronization management, asynchronous and data transfer. BEHAVIORS provides optimized reload and simple URL navigation.

For example, when a conventional web page in which a design and a program is not separated as shown in Table 1 is divided into a design and a handler according to the present invention, the handler is as shown in Table 2 below and the screen as shown in Table 3 as follows.

Table 1 below is an example of a web page with no separate design and program.

             Example of design and program not being separated (JSP-Java Server Page) <% @ page import = "common. *, museum. *, java.text. *, java.util. *"%> <% @ page contentType = "text / html; charset = KSC5601"%> <% String sch_value = (request.getParameter ("sch_value")! = null? request.getParameter ("searcsch_valueh_word"): ""); Board free = new Board (); DbSet ds = free.executeCond (search_word); %> <script language = "javascript"> function go_search () {var frm = document.form; if (frm.sch_value.value == "") {alert ("No value found. Please check"); return; } frm.action = "member_list.jsp"; frm.submit (); } </ script> <form name = "form" method = "post"> <table> <tr> <td> search value (ID): <input type = "text" name = "sch_value"> <img src = "/common_img/btn_search_2.gif" onclick = "javascript: go_search ()"> </ td> </ tr> </ table> <table id = "webplus" class = "template" cellpadding = "1" cellspacing = " 1 "width =" 98% "> <tr> <td> ID </ td> <td> Name </ td> <td> Resident Code </ td> <td> Postal Code </ td> <td> Address </ td> <td> E-MAIL </ td> </ tr> <% while (ds.next ()) {%> <a href = "member_update.jsp? ID = <% = ds.getValue (" ID ")%>"> <tr> <td> <% = ds.getValue ("ID")%> </ td> <td> <% = ds.getValue ("name")%> </ td> <td> <% = ds.getValue ("Resident Number")%> </ td> <td> <% = ds.getValue ("Postal Code")%> </ td> <td> <% = ds. getValue ("address")%> </ td> <td> <% = ds.getValue ("EMAIL")%> </ td> </ tr> </a> <%}%> </ table> < / form>

                                     Handler <? xml version = "1.0" encoding = "utf-8"?> <handler id = 'select' title = "member" code = "@ / codes.xml" dataMapping = '/ subji'> <screens> <include target = "contentView" screen = "@ / test.html" parent = "window"> </ include> </ screens> <script> Data.send ('executeCond'); UICtrol.load (Properties.RETRIEVE); </ script> <controls> <control xpath = "condition"> <text id = "sch_value" title = "Search value" size = "10" maxLength = '10 '/> <image id = "bt_search" file = " /common_img/btn_search_2.gif "postXML =" condition "replaceXML =" columnValues "reloadController =" table "> <script event =" onclick "> Data.sendXML ('executeCond'); UICtrol.load (Properties.RETRIEVE); </ script> </ image> </ control> <control xpath = "list: columnValues / columnValue"> <listGrid id = "table" paramName = "ID: ID"> <script event = "onclick"> Link.open ("/ member_update"); </ script> <column id = "ID" title = "ID" align = "center" /> <column id = "NAME" title = "Name" /> <column id = "JUMIN" title = "Resident Number" /> <column id = "ZIPCODE" title = "Postal code" /> <column id = "ADDR" title = "Address" /> <column id = "EMAIL" title = "E-MAIL" /> </ listGrid > </ control> </ controls> </ handler>

                                      screen <meta http-equiv = Content-Type content = "text / html; charset = euc-kr"> <table width = '700' align = 'center' cellpadding = "0" cellspacing = "0"> <tr> < td> search value (number): <w: text id = "sch_value"> &nbsp; <w: image id = "bt_search" /> <br> <br> </ td> </ tr> <tr> <td > <table id = "table" class = "template" cellpadding = "1" cellspacing = "1" width = "98%"> </ td> </ tr> </ table>

The XML Manager 212-1 receives the data configured in the form of xml from the client 100, parses the corresponding xml, and delivers the data to the data mapping unit 212-2, and the data mapping unit. ) 212-2 creates and delivers the data in xml format to the client.

The data mapping unit 212-2 serves as a data interface with the business logic 220 that connects the business logic 220 and transfers the received data to the XML manager 212-1. To perform.

In addition, the web plus engine 120 is implemented in JavaScript to perform a procedure as illustrated in FIG. 4 to call the handler 213 and the screen 214 according to the request of the browser 110, and the handler 213. Parsing) generates and provides an html file of the corresponding object mapped with the screen 214 and ID information. The web server 200 and the connection communication communicate with HTTP and xmlHttpRequest. That is, the web plus engine 120 has a function of configuring one window loading the web plus engine at the request of the web browser 110, and one window includes a popup without having to reload the web plus engine. The ability to load all the screens, the ability to load and parse configuration files that define common elements for implementing screens and functions, to set information such as global variables and sessions, and to configure screens and features The ability to call a handler that you define directly through a file or URL, The ability to call the screen files defined in the handler and draw it at each location of the window that is set, The controller described in the called handler to the data information (XPATH) and Screen classification (ID ) And parsing element and attribute information, controller tags in handlers and screen controllers Ability to create basic information linked with the corresponding screen object by mapping his ID, Automatically implement various screen functions only with the property information declared that the developer has already implemented the function through the controller tag property of the handler, Through the script tag of the handler, the event handler is used.When an event occurs, functions such as data call, screen change, popup, and message notification are provided through the built-in function and user-defined script, and the function, handler and As the screen is completely separated, it handles the function of importing and reusing the screens and functions that are duplicated in the handler, and reloading only the desired data according to the controller tag classification of the handler.

Referring to FIG. 4, when the client 100 attempts an initial connection to a corresponding web application of the web server 200 to which the present invention is applied, the web plus engine 120 from the web server 200 is connected to the client 100. It is loaded in the browser 110 (S401, S402).

Thereafter, the web plus engine 120 generates a common document when there is a request (HTTP request) of the browser 110 (S403). The common document is a basic screen configuration commonly used as a top, a body, and a bottom, as shown in FIG. 6, where the top corresponds to the head portion of the entire screen, and the body corresponds to the main portion. It shows the contents of the screen, and the bottom is the bottom of the full screen.

Subsequently, the start-config.xml and message.xml files are read to set a basic environment to be executed in the web application, and the handler 213 for controlling the screen is called (S404). The start-config.xml file controls the basic environment of the web application, and the message.xml file indicates the contents of an alert window to be shown to the client 100 when the client 100 generates a specific event in the web page. Notices are defined.

Subsequently or in the case of not the initial connection, the information described in the called handler 213 is parsed (S405). At this time, another handler can be imported and reused publicly. Subsequently, the screen 214 file defined in the handler 213 is called to include the screen 214 in the body part of the common document (S406). This allows the screen to be reused.

Subsequently, a tag having the same ID name of the handler tag and the screen tag is mapped to generate a basic html tag of the corresponding object (S407). Looking more closely at this,

a) The web plus engine interprets the id information of the element tag of the handler.

b) The web plus engine finds the same id from the id of the tag on the screen using the id information found in step a).

c) The web plus engine generates the mapping information found through steps a) and b) as the basic tag of html.

d) Go back to step a) to map the handler to the screen.

For example, if id is "sch_value" as shown in Table 3, html basic tag is created as shown in Table 4 from mapping of handler and screen.

    division                             sauce    Handler . . <text id = "sch_value" title = "Search value" size = "10" maxLength = '10 '/>.    screen . . <w: text id = "sch_value">.    htmltag  <input type = "text" id = "sch_value">

Subsequently, the handler 213 analyzes the defined attributes, events, and actions of the elements of the xml to additionally set the attributes, scripts, etc. of the basic html tag generated in the previous step (S408). Looking more closely at this,

1) The WebPlus engine finds the object information related to the event and action of the element tag of the handler or interprets each attribute information described.

2) The WebPlus engine adds the html property of the object with the same id as the handler and the screen based on the property information described in the element tag of the handler, and additionally creates a script related to the event and action based on the information found in step 1. .

3) Repeat step 1) and execute again.

For example, when the html tag is generated as shown in Table 4 above, attributes are assigned from the handler and the screen as shown in Table 5 below.

    division                             sauce    Handler . . <text id = "sch_value" title = "Search value" size = "10" maxLength = '10 '/>.    screen . . <w: text id = "sch_value">.    htmltag  <input type = "text" id = "sch_value" size = "10" maxlength = "10">

The body part of the common document is output to the browser, and the screen corresponding to the top and bottom is called and output to the browser (S409 and S410).

Next, the entire operation procedure between the web browser and the web server in the web application system according to the present invention configured as described above will be described with reference to FIG. 5.

Referring to FIG. 5, when the client 110 requests the browser 110, the web plus engine 120 generates a common document (S1 and S2). As described above, the common document is a basic screen configuration to be commonly used, which consists of a top, a body, and a bottom.

Subsequently, when the web plus engine 120 requests the handler of the corresponding screen to the web server 200 through the xmlHttpRequest, the web server 200 provides the handler 213 and requests the screen to be used for the handler 213. ) (S3 ~ S6). In this case, the presentation layer 210 of the web server is a screen corresponding to a design and a handler 213 corresponding to a program source, rather than a combination of a design and a source in one file according to the previous web application model according to the present invention. It is managed as an independent file separated by (214).

Subsequently, the webplus engine 120 generates HTML output data based on the parsing and mapping information of the handler 213 and the screen 214 and responds to the web browser 110 (S7 and S8).

When an event is generated and data is requested, the web plus engine 120 requests data from the web server's XML manager 212-1 using xmlHttpRequest, and the web server's XML manager 212-1 performs xml parsing. After execution, data in the form of VO (Value Object), Model, and List are transferred to Data Mapping 212-2. Accordingly, Data Mapping 212-2 calls business logic to process the data. Request (S9 ~ S12).

The business logic 220 processes the requirements through a resource 300 such as a database management system according to the nature of the required application, and then transfers the data to the data mapping 212-2, and the data mapping 212. -2) transmits the corresponding data information to the XML Manager 212-1 in the form of a Value Object (VO), a Model, and a List (S13 to S15).

The XML Manager 212-1 generates data in the form of VO (Value Object), Model, and List provided by the Data Mapping 212-2 in xml and then sends it to the web plus engine 120. In response, the web plus engine 120 parses the received xml information and then switches to html information for updating the browser 110 to update a part of the screen of the browser 110 (S16 to S19).

As described above, the web application model according to the present invention receives the request of the browser and delivers the request to the web server, and generates an html file for the browser using the handler and the screen received from the web server. That is, in the present invention, all user interface (UI) operations for creating a screen displayed to the user through a web browser are handled by the client's web plus engine, and the server processes only business logic and data to balance the role between the client and the server. To ensure efficient use of resources.

As described above, according to the present invention, by managing the screen corresponding to the program source of the web application constituting the screen and the screen corresponding to the design of the screen, it is easy to develop a new web application and maintain the maintenance. It is convenient and can reduce the load on the server by handling functions that handle the user interface (UI) on the client side and minimize the reload of the screen by applying the latest web standards such as AJAX. It provides the effect of reducing the screen configuration and load time.

In addition, it adds additional functions to the existing web application model for accessing software applications on the WWW, providing easy and elegant web page configuration and fast response time for general users, and revolutionizing the existing development method for software developers (programmers and designers). It is not dependent on the different development languages for developing web application programs, and provides a separate working environment for programmers and designers by providing complete separation of design and source files, improving development productivity and ease of maintenance.

It also allows software developers to adopt standard access protocols, allowing developers to provide support for any computer system that can use an HTML-aware browser.

In addition, the present invention provides an independent environment that does not depend on different platforms for the development of the web application to the operator and the operating organization of the web application, so that the web application program having the same content as the number of different platforms to different platforms According to the above invention, it can be used for each platform as a web application without any need, and thus, cost and development time can be shortened, so even a small operator and an operating organization can provide an open path to a large market. .

The present invention is not limited to the above-described embodiments, and it is apparent that many modifications are possible by those skilled in the art within the technical spirit to which the present invention belongs.

Claims (8)

In the solution interface method for developing a web application in a web environment consisting of a client with a web browser and a web server implemented in various server platforms, On the web server, web pages are divided into screens corresponding to designs and handlers corresponding to programs, and implemented as separate files. The web plus engine running on the client side invokes the handler according to the request of the web browser, loads the screen corresponding to the handler, maps the handler and the screen, generates an html tag, and then assigns an attribute. By providing it to the web browser A method of presentation for a web application, characterized in that the design and the program can be simultaneously developed to shorten the development period and to facilitate maintenance, and to be independently developed regardless of the platform of the web server. In the method for providing a web application in a client-web server structure, A first step of the web plus engine running on the client generating a common document according to a request of a web browser; A second step of the web server providing a handler when the web plus engine requests a handler of the screen; A third step of providing the screen by the web server when the web plus engine requests a screen to use for the handler; A fourth step of the web plus engine parsing the handler and generating html to respond to the web browser using a mapping with the screen and outputting the html to the web browser; A fifth step in which the web plus engine requests data from the web server when an event is generated and the data is requested, the web server executing predetermined business logic and responding the result data to an xml file; And And a sixth step of the web plus engine parsing the xml file to provide an html file including the updated data to the web browser. The method of claim 2, wherein the fifth step When the web plus engine requests data from the xml manager of the web server, the xml manager requests the corresponding data through data mapping after parsing the xml, and the data mapping calls business logic to output the xml data. Delivering to the Manager, the xml Manager is a presentation method for a web application, characterized in that for generating the resulting data as an xml file. In a web environment consisting of a client and a web server, Loading a web plus engine from the web server if the client's connection is an initial connection; Generating, by the web plus engine, a common document according to a request of a web browser; Calling, by the web plus engine, a handler which controls a first screen by reading a configuration file; Parsing Element information described in the called handler by the web plus engine; The web plus engine calling a screen file defined in the handler; Parsing a handler by the web plus engine and mapping an id of a handler tag and a screen tag to generate a basic html tag of the object; And And setting, by the web plus engine, an attribute defined in an element of a handler and setting an attribute in a basic html generated in a previous step. In a client-server web environment, A web browser running on the client; During initial access, the server is loaded from the server to the client, requests the handler and the screen of the screen to the server according to the request of the web browser, generates html output data through parsing and mapping, and provides the event to the web browser. If a new data is required according to the web plus engine to communicate to the server in a synchronous / asynchronous manner to receive xml data, add html information to the web browser; And And a presentation unit that is executed in the server and provides a handler and a screen according to the request of the web plus engine while managing documents divided into handlers and screens. The method of claim 5, wherein the presentation unit A web plus viewer manager comprising a screen which is an element forming a screen of a web application, a handler which connects data to the screen as an element forming logic of a web application, and controls the screen; In order to deliver the data requested by the client, the xml information received from the web plus engine is parsed and transmitted to the data mapping unit, and the data received from the data mapping unit is generated as xml information and the client Web application development comprising a Web Plus data controller consisting of an XML Manager (XML Manager) and the data mapping unit for connecting the business logic to find the data and deliver the data to the XML Manager. system. The method of claim 6, wherein the handler is Web application development system, including dataset, Transfer, Config, built-in function, Ajax-based component library. The method of claim 5, wherein the web plus engine Implemented in JavaScript A function of configuring one window loaded with a webplus engine in response to a request of the web browser; The one window function to be made available on all screens including pop-ups without having to reload the webplus engine; A function of loading and parsing an environment configuration file defining common elements for implementing screens and functions to set information such as global variables and sessions; The ability to call handlers that you define directly through configuration files or URLs to implement screens and functionality; A function of calling screen files defined in the handler and drawing each position of the set window; Dividing the controller described in the called handler by data information (XPATH) and screen classification (ID) and parsing elements and property information; A function of mapping the controller tag of the handler and the ID of the screen controller tag and connecting the screen tag with the corresponding screen object to generate basic information; A function of automatically implementing various screen functions only with attribute information declared that the developer has previously implemented a function directly through the controller tag attribute of the handler; A function of using an event handler through a script tag of the handler, and providing a function such as data call, screen change, popup, message notification, and various user addition functions through an embedded function and a user-defined script when an event occurs; A function of importing and reusing a screen and a function that are used in duplicate as the handler and the screen are completely separated from each other; And And reload only desired data according to the controller tag classification of the handler.

Images