CN103647828A - REST-based JAVA MVC system and data processing method thereof - Google Patents

Abstract

The invention discloses a REST-based JAVA MVC system and a data processing method thereof, including sending a data request conforming to the REST specification from a client to a server; If the match is unsuccessful, the filter will match the path of the data request with the resource path in the server directory. If the match is unsuccessful, an error page will be sent to the client; if the match is successful, the filter will match the resource path in the server directory The resource information is sent to the client; if the match is successful, the filter transmits the data request to the corresponding controller in the MVC framework on the server through the resource path in the routing table matched with the path of the data request; The controller receives the data request and processes it, and finally the server sends the processed result to the client. Therefore, the present invention enables rapid development and simple configuration.

Description

REST-based JAVA MVC system and its data processing method

technical field

The present invention relates to the field of computer technology, in particular to a REST-based JAVA MVC system and a data processing method thereof. the

Background technique

The full name of REST is the abbreviation of REpresentational State Transfer (expressive state transfer). REST refers to a set of architectural constraints and principles, and an application or design that satisfies these constraints and principles is RESTful. REST defines a set of architectural principles by which you can design system resource-centric web services, including how resource states are processed and transmitted over HTTP by clients written in different languages. If you consider the number of web services using REST, REST has become the most dominant web service design pattern in recent years. In fact, REST has a great impact on the Web, because it is quite convenient to use, it has generally replaced the interface design based on SOAP and WSDL. the

The full name of MVC is Model View Controller, which is the abbreviation of model (model)-view (view)-controller (controller). The premise of the method is that if the business logic is aggregated into a component, and the interface and user interaction around the data can be improved and customized without rewriting the business logic, MVC is uniquely developed to map traditional input, Processing and output functions are organized in a logical GUI. the

MVC is a framework pattern that enforces separation of application input, processing, and output. Using MVC applications are divided into three core components: model, view, controller, each of which handles its own tasks. The most typical MVC is the pattern of JSP+Servlet+JavaBean. Common MVC such as: Struts, SpringMVC, etc. But the more functions the MVC framework integrates, the more cumbersome the configuration will be. If you want to quickly develop a small web application, using these frameworks will make the project look bloated. If you are not familiar with the configuration of the framework, you will spend a lot of time on the configuration, which is not worth the candle. the

Contents of the invention

In view of this, the object of the present invention is to propose a REST-based JAVA MVC system and a data processing method thereof, which can realize rapid development and simple configuration. the

A kind of JAVA MVC data processing method based on REST that the present invention provides based on above-mentioned purpose, comprises steps:

S1: The client sends a data request conforming to the REST specification to the server;

S2: The filter on the server intercepts the data request, the filter matches the path of the data request with the resource path in the routing table, if the matching is unsuccessful, proceed to step S3; if the matching is successful, proceed to Step S4;

S3: The filter matches the path of the data request with the resource paths in the server directory, if the matching is unsuccessful, the server sends an error page to the client; if the matching is successful, all the matched Send the resource information under the server directory to the client;

S4: Through the resource path in the routing table matched with the path of the data request, the filter transmits the data request to the corresponding controller in the MVC framework on the server; the controller The data request is received and processed, and finally the server sends the result processed by the controller to the client. the

Optionally, the filter in S2 needs to be initialized before it is used for the first time, and the process is:

start said server;

Initialize the filter;

Initialize the global parameters of the filter according to the web.xml in the server;

registering the mapping of the controller to the routing table of the server;

Registering a listener keeps the filter in a listening state. the

Further, when the controller processes the received data request in S4, the specific implementation process is that the controller sends the data request to the model in the MVC framework on the server; the model performs business logic judgment on the data request , and finally the model returns the processed data request to said controller. the

Further, after the path of the data request in S4 is successfully matched with the resource path in the routing table, and before the filter transmits the data request to the corresponding controller in the MVC framework on the server , to judge whether the data request is configured with a listener; if the data request is configured with a listener, execute the listener first, and then send the data request to the corresponding controller according to the information of the listener; if If no listener is configured for the data request, the data request is directly sent to the corresponding controller. the

Further, after the controller receives the data result processed by the model, and before the processed data result is returned to the client through the server, it judges whether the processed data result is configured with a listener; if configured with a listener If the listener is configured, the listener will be executed first, and then the processed data request will be returned to the client; if no listener is configured, the server will directly return the processed data request to the client after the controller receives the data result processed by the model end. the

Further, when the server sends the processed result to the client, if it needs to be presented to the client in the form of a view, the processed result will be finally processed through the view in the MVC framework on the server. The results are sent to the client as described. the

In addition, the present invention also provides a JAVA MVC system based on REST, including:

The data request sending unit is used for the client to send a data request conforming to the REST specification to the server;

The intercepting matching unit is used for the filter on the server to intercept the data request, the filter matches the path of the data request with the resource path in the routing table, if the matching is unsuccessful, the matching unit and the resource path are intercepted The path matching unit is connected; if the matching is successful, the connection between the matching unit and the data processing unit is intercepted;

The resource path matching unit is used for the filter to match the path of the data request with the resource path under the server directory, if the matching is unsuccessful, the server sends an error page to the client; if the matching is successful Then send the matching resource information under the server directory to the client;

A data processing unit, configured to pass the resource path in the routing table matched with the path of the data request, and the filter transmits the data request to the corresponding controller in the MVC framework on the server; The controller receives and processes the data request, and finally the server sends the result processed by the controller to the client. the

Optionally, after the data processing unit successfully matches the path of the data request with the resource path in the routing table, and after the filter transmits the data request to the MVC framework on the server, the corresponding Before the controller, judge whether the data request is configured with a listener; if the data request is configured with a listener, execute the listener first, and then send the data request to the corresponding Controller; if the data request is not configured with a listener, the data request is directly sent to the corresponding controller. the

Further, after the controller in the data processing unit receives the data result processed by the model and before the processed data result is returned to the client through the server, it is judged whether the processed data result is configured with Listener; if a listener is configured, execute the listener first, and then return the processed data request to the client; if no listener is configured, after the controller receives the data result processed by the model, the server will directly process the The subsequent data request is returned to the client. the

Further, the filter in the intercepting matching unit needs to be initialized before the first use, first start the server, initialize the filter, and then initialize the global parameters of the filter according to the web.xml in the server; After that, register the mapping from the controller to the routing table of the server; finally, register the listener so that the filter is in a listening state. the

As can be seen from the above, the REST-based JAVA MVC system and data processing method thereof provided by the present invention intercept the data request conforming to the REST specification through the filter on the server, and compare the path of the data request with the resource path in the routing table. Matching is performed. If the matching is unsuccessful, the filter will match the path of the data request with the resource path in the server directory. If the matching is successful, the data will be processed. Therefore, the REST-based JAVA MVC system and data processing method thereof of the present invention combine the REST specification with the MVC frame system to form a light-weight system and data processing method. the

Description of drawings

Fig. 1 is the schematic flow sheet of the JAVA MVC data processing method based on REST in the embodiment of the present invention;

Fig. 2 is the schematic flow chart of filter initialization of the embodiment of the present invention;

Fig. 3 is the structural representation of the JAVA MVC system based on REST of the embodiment of the present invention. the

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be described in further detail below in conjunction with specific embodiments and with reference to the accompanying drawings. the

Referring to shown in Fig. 1, be the schematic flow sheet of the JAVA MVC data processing method based on REST in the embodiment of the present invention, described JAVA MVC data processing method based on REST comprises the following steps:

In step 101, the client sends a data request conforming to the REST specification to the server. the

Wherein, the method of the client request may be GET, POST, PUT, DELETE, HEAD and so on. the

Step 102, the filter Filer on the server intercepts the data request, the filter matches the path of the data request with the resource path in the routing table, if the matching is unsuccessful, proceed to step 103; if the matching is successful Then go to step 104 . the

In one embodiment of the present invention, filter Filer needs to be initialized before first use, and its process is:

Step 201: Start the server. the

Step 202: Initialize the filter Filer. the

Step 203: Initialize the global parameters of the filter Filer according to the web.xml in the server. the

In the embodiment of the present invention, filter is configured in web.xml, and the most basic parameters are set, such as: project annotation type scanning path, control layer class file filtering, project file encoding, page content directory, etc. After the global parameters of the filter Filer are initialized, the class files are automatically scanned according to the parameters. the

Step 204: Register the mapping from the controller to the routing table of the server. the

Among them, the controller implements the mapping in the routing table through annotation programming, and identifies parameters through annotation. the

Step 205: registering a listener so that the filter Filer is in a listening state. the

Step 103, the filter matches the path of the data request with the resource path under the server directory, if the matching is unsuccessful, the server sends a 404 error page to the client; if the matching is successful, it will match the The server sends the resource information under the resource path under the server directory matching the path of the data request to the client. the

In an embodiment, after the path of the data request is matched with the resource path in the server directory, the resource information found may be information in the form of html, jsp, word, pictures, and the like. the

Step 104, through the resource path in the routing table matched with the path of the data request, the filter transmits the data request to the corresponding controller in the MVC framework on the server; the control The controller receives and processes the data request, and finally the server sends the result processed by the controller to the client. the

In the embodiment of the present invention, when the controller processes the received data request, the specific implementation process is that the controller sends the data request to the model Model in the MVC framework on the server. The Model performs business logic judgment on the data request, and may need to extract the database on the server during processing, and finally the Model returns the processed data request to the Controller. Also, the model Model can also store the processed data request into the database on the server. the

As an embodiment of the present invention, after the path of the data request is successfully matched with the resource path in the routing table, and the filter Filer transmits the data request to the corresponding Before the controller is in the controller, it can be judged whether the data request is configured with a listener. If the data request is configured with a listener, the listener is executed first, and then the data request is sent to a corresponding controller according to the information of the listener. If the data request is not configured with a listener, the data request is directly sent to the corresponding controller controller. Wherein, the listener may be provided with applications such as authentication, log, data compression, image conversion, and token. the

As another embodiment of the present invention, after the controller receives the processed result of the model Model, and before the processed data result is returned to the client through the server, it is judged whether the processed data result Configured with listeners. If a listener is configured, execute the listener first, and then return the processed data request to the client. If no listener is configured, the server will directly return the processed data request to the client after the controller receives the processed result of the Model. the

In addition, it is worth noting that the processed data request returned by the server may be data in the form of Json, XML, JSP, Free Mark, and Velocity. In another embodiment of the present invention, when the server sends the processed result to the client, if it needs to be presented to the client in the form of a view, such as JSP, Velocity and Free Mark, etc. data, the processed result is finally sent to the client through the view view in the MVC framework on the server. Wherein, the view view receives the processed data request transmitted by the controller, and then the view view returns the processed data request to the client. Certainly, if it is not necessary to present to the client in the form of a view, the server directly returns the processed data request to the client. the

Referring to shown in Fig. 3, be the structural representation of the JAVA MVC system based on REST of the embodiment of the present invention, described JAVA MVC system based on REST comprises:

The data request sending unit 301 is configured for the client to send a data request conforming to the REST specification to the server. Wherein, the method of the client request may be GET, POST, PUT, DELETE, HEAD and so on. the

The intercepting matching unit 302 is used for the filter Filer on the server to intercept the data request, the filter matches the path of the data request with the resource path in the routing table, if the matching is unsuccessful, the intercepting matching unit 302 is connected to the resource path matching unit 303; if the matching is successful, the intercepting matching unit 302 is connected to the data processing unit 304. the

In one embodiment of the present invention, the filter Filer needs to be initialized before it is used for the first time, and the intercepting matching unit 302 first starts the described server, initializes the filter Filer, and then according to the web.xml in the server Initialize the global parameters of the filter Filer. Among them, filter is configured in web.xml, and the most basic parameters are set, such as: project annotation type scanning path, control layer class file filtering, project file encoding, page content directory, etc. After the global parameters of the filter Filer are initialized, the class files are automatically scanned according to the parameters. After that, register the mapping from the controller to the routing table of the server. Among them, the controller implements the mapping in the routing table through annotation programming, and identifies parameters through annotation. Finally, registering a listener makes the filter Filer in a listening state. the

The resource path matching unit 303 is used for the filter to match the path of the data request with the resource path under the server directory, if the matching is unsuccessful, the server sends a 404 error page to the client; if If the matching is successful, the resource information under the resource path under the server directory matching the path of the data request by the server is sent to the client. the

In an embodiment, after the path of the data request is matched with the resource path in the server directory, the resource information found may be information in the form of html, jsp, word, pictures, and the like. the

The data processing unit 304 can transmit the data request to the corresponding controller in the MVC framework on the server through the resource path in the routing table that matches the path of the data request; The controller receives and processes the data request, and finally the server sends the result processed by the controller to the client. the

In the embodiment of the present invention, when the controller processes the received data request, the specific implementation process is that the controller sends the data request to the model Model in the MVC framework on the server. The model Model judges the business logic of the data request, and may need to extract the database on the server during processing, and finally the model Model returns the processed data request to the controller Controller. Also, the model Model can also store the processed data request into the database on the server. the

As an embodiment of the present invention, after the path of the data request is successfully matched with the resource path in the routing table, and the filter Filer transmits the data request to the corresponding Before the controller is in the controller, it can be judged whether the data request is configured with a listener. If the data request is configured with a listener, the listener is executed first, and then the data request is sent to a corresponding controller according to the information of the listener. If the data request is not configured with a listener, the data request is directly sent to the corresponding controller controller. Wherein, the listener may be provided with applications such as authentication, log, data compression, image conversion, and token. the

As another embodiment of the present invention, after the controller receives the processed result of the model Model, and before the processed data result is returned to the client through the server, it is judged whether the processed data result Configured with listeners. If a listener is configured, execute the listener first, and then return the processed data request to the client. If no listener is configured, the server will directly return the processed data request to the client after the controller receives the processed result of the Model. the

In addition, it is worth noting that the processed data request returned by the server may be data in the form of Json, XML, JSP, Free Mark, and Velocity. In another embodiment of the present invention, when the server sends the processed result to the client, if it needs to be presented to the client in the form of a view, such as JSP, Velocity and Free Mark, etc. data, the processed result is finally sent to the client through the view view in the MVC framework on the server. Wherein, the view view receives the processed data request transmitted by the controller, and then the view view returns the processed data request to the client. Certainly, if it is not necessary to present to the client in the form of a view, the server directly returns the processed data request to the client. the

From this it can be seen that the REST-based JAVA MVC system and data processing method thereof realized by the present invention creatively propose a REST-based specification to establish a JAVA MVC framework, which combines the advantages of REST and JAVA MVC and reduces the cost of third-party packages. Dependence greatly reduces the time for configuring files and reduces the size of the system; moreover, before transmitting the data request to the controller, it is judged whether the data request is configured with a listener. After the listener is configured, the listener can be directly passed The data request is sent to the corresponding controller, so that the data request can be quickly and conveniently found and transmitted to the corresponding controller; the use of the listener before the data request is transmitted to the controller also makes the transmission of the data request more efficient. For safety; Also, before the controller returns the processed data request to the client through the server, the listener is used to monitor the process of the entire client data request; meanwhile, the present invention adopts non-invasive The annotation method is used for development mode, the configuration is simpler, the project development cycle is shorter, and the project volume is greatly reduced, and the development of cross-platform and cross-language is achieved directly; in addition, the maintenance cost is greatly reduced in the later stage, due to the use of Java native low-level code and functions, making the project more stable, safer, and easier to maintain, thereby improving the efficiency of Web development; especially suitable for small and medium-sized projects, fast development, easy configuration; finally, the entire REST-based JAVA MVC system and its data The processing method is simple, compact and easy to realize. the

Those of ordinary skill in the art should understand that: the above descriptions are only specific embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, and improvements made within the spirit and principles of the present invention etc., should be included within the protection scope of the present invention. the

Claims (10)

1. the JAVA MVC data processing method based on REST, is characterized in that, comprises step:

S1: client transmission meets the request of data of REST standard to server;

S2: the described request of data of filter interception on described server, this filter mates the path of described request of data with the resource path in routing table, if mate the unsuccessful step S3 that carries out; If the match is successful, carry out step S4;

S3: this filter mates the path of described request of data with the resource path under described server directory, sends the wrong page to described client if mate unsuccessful described server; If the match is successful, the resource information under the described server directory of coupling is sent to described client;

S4: by the resource path in the described routing table of the route matching with described request of data, this filter is sent to described request of data in the MVC framework on described server in corresponding controller; Described controller receives described request of data and processes, and the result after last described server is processed described controller sends to described client.

2. processing method according to claim 1, is characterized in that, at filter described in S2, before using for the first time, is to carry out initialization, and its process is:

Start described server;

Initialization filter;

According to the global parameter of the web.xml initialization filter in described server;

Register described controller to the mapping of the routing table of described server;

Registration monitor makes filter in listening state.

3. processing method according to claim 1 and 2, is characterized in that, when controller described in S4 is processed the described request of data receiving, its concrete implementation process is that controller sends to the model in the MVC framework on server by request of data; This model carries out service logic judgement to request of data, and finally this model returns to described controller by the request of data after processing.

4. processing method according to claim 3, it is characterized in that, at the path of request of data described in S4 and the resource path in routing table after the match is successful, and in this filter is sent to the MVC framework on described server by described request of data in corresponding controller before, carry out the judgement whether this request of data disposes monitor; If this request of data has configured monitor, first carry out this monitor, then according to the information of this monitor, described request of data is sent to corresponding controller; If this request of data does not configure monitor, directly send this request of data to corresponding controller.

5. processing method according to claim 4, it is characterized in that, after described controller receives the data result that model processes, and before the data result after this processing returns to client by server, judge whether the data result after this processing disposes monitor; If dispose monitor, first carry out this monitor, and then the request of data after processing is returned to client; If do not configure monitor, after controller receives the data result of model processing, server directly returns to client by the request of data after processing.

6. processing method according to claim 5, it is characterized in that, described server sends to the result after processing in the process of described client, when if desired presenting to described client with the form of view, by the view in the MVC framework on described server, finally the result after processing is sent to described client.

7. the JAVA MVC system based on REST, is characterized in that, comprising:

Request of data transmitting element, the request of data that meets REST standard for client transmission is to server;

Interception matching unit, for the described request of data of filter interception on described server, this filter mates the path of described request of data with the resource path in routing table, if mate the unsuccessful matching unit of tackling, be connected with resource path matching unit; If the match is successful, tackle matching unit and be connected with data processing unit;

Resource path matching unit, mates the path of described request of data for this filter with the resource path under described server directory, if mate unsuccessful described server, send the wrong page to described client; If the match is successful, the resource information under the described server directory of coupling is sent to described client;

Data processing unit, for the resource path of the described routing table of the route matching by with described request of data, this filter is sent to described request of data in the MVC framework on described server in corresponding controller; Described controller receives described request of data and processes, and the result after last described server is processed described controller sends to described client.

8. system according to claim 7, it is characterized in that, described data processing unit is at the path of described request of data and the resource path in routing table after the match is successful, and in this filter is sent to the MVC framework on described server by described request of data in corresponding controller before, carry out the judgement whether this request of data disposes monitor; If this request of data has configured monitor, first carry out this monitor, then according to the information of this monitor, described request of data is sent to corresponding controller; If this request of data does not configure monitor, directly send this request of data to corresponding controller.

9. system according to claim 8, it is characterized in that, after described controller in described data processing unit receives the data result of model processing, and before the data result after this processing returns to client by server, judge whether the data result after this processing disposes monitor; If dispose monitor, first carry out this monitor, and then the request of data after processing is returned to client; If do not configure monitor, after controller receives the data result of model processing, server directly returns to client by the request of data after processing.

10. according to the system described in claim 7 to 9 any one, it is characterized in that, described interception matching unit middle filtrator is to carry out initialization before using for the first time, first start described server, initialization filter, then according to the global parameter of the web.xml initialization filter in described server; Afterwards, register described controller to the mapping of the routing table of described server; Finally, registration monitor makes filter in listening state.

Images