CN104267944A - Spring-based MVC (model view controller) mode optimization system - Google Patents

Abstract

The invention provides a Spring-based MVC pattern optimization system, and with the popularization of Web application, a series of general development patterns are gradually formed by Web development technology, so that Web application developers greatly reduce repetitive workload and improve the development efficiency of application. Among these modes, the MVC mode based on the Model, View, and Controller hierarchical structure has the advantages of low coupling, high portability, layer-by-layer separation, and the like, and is gradually becoming the mainstream mode of Web application development. However, the MVC mode has its disadvantages, mainly two-fold: firstly, the test unit excessively depends on ServeltAPI, so that the difficulty of unit test is greatly increased; second, the Controller caching process in MVC requires invoking a caching mechanism of Servlet, which lacks flexibility. The optimization scheme is mainly provided for the two defects.

Description

A kind of MVC model-based optimization system based on Spring

Technical field

The present invention relates to Computer Applied Technology field, specifically a kind of MVC model-based optimization system based on Spring.Developing rapidly of internet creates tremendous influence to human lives, brings earth-shaking change to society, and no matter being country, government, enterprise or individual, is all like this.People are to the favor of infotech, facilitate the develop rapidly of infotech, computer technology and network technology, new theory, new technology, new ideas, new idea emerge in an endless stream, but along with the continuous growth of people's demand, the complexity of the performance history of software product is also more and more higher.In the face of these problems, people are ceaselessly thinking deeply, groping and then are proposing corresponding solution again, such as the generation of Design Mode theory.

Background technology

In the past few years, along with popularizing of internet, based on the Web application system of B/S mode development, the advantages such as general by means of it, easy-to-use, thin-client achieve and develop rapidly, become the mainstream technology of the application such as e-commerce system, office system gradually, its advantage is more obvious in the system such as portal website, B2B E-commerce website of government or enterprise.

Along with popularizing of Web application, Web development technique also defines a series of general development mode gradually, makes Web application developer greatly reduce repetitive work amount, improves the development efficiency of application.In these patterns, the MVC pattern based on Model, View, Controller hierarchy has the advantages such as advantage such as low coupling, portable high, separation layer by layer and becomes the prevailing model of Web application and development gradually.But MVC pattern also has its weak point, mainly contains two aspects: the first, is too dependent on Servlet API, considerably increase the difficulty of unit testing; Controller caching process in the second, MVC needs the caching mechanism calling Servlet, lacks dirigibility.Prioritization scheme is provided herein mainly for above two kinds of deficiencies.

For Web application developer, shortening the construction cycle, reduce cost of development, improving operational efficiency and strengthen maintainability is the target that it is pursued.The appearance of J2EE platform and widespread use reduce the cost of Web application and development to a certain extent, also reduce the complexity of performance history, but due to the deficiency such as expensive of its self too complicated architecture, the process being difficult to Accurate Prediction application and result and development and maintenance cost process, often make the architectural schemes of J2EE cannot allow people's really satisfaction.For above-mentioned all drawbacks of mentioning and deficiency, many Web application frameworks arise at the historic moment.

Struts framework: Struts is the Web application framework of an old brand, also be use framework the most widely in cash application, it mainly adopts Servlet and JSP technology to realize, and comprises a front-end control assembly, a series of action class, action mapping, the use tool-class of processing XML, the automatic filling of server end JavaBean, the Web list supporting checking and the function and content such as International Support, generation HTML.The major defect of Struts lacks perfect authority setting, and do not have the support of data Layer, and therefore its use must place one's entire reliance upon concrete frame clsss.And in actual applications, domain object can not use as FormBean by Struts, can generate much extra FormBean like this, result in unnecessary repeatability.Meanwhile, its View component is only limitted to support JSP technology, and the view techniques for other does not provide perfect support scheme.

EJB technology: this technology results from March, 1998, then always as the core of J2EE, main object is to simplify enterprise-level application development, and more energy can be devoted on service logic instead of system level issues by developer.

Spring framework: 2002, Rod Johnson sums up the some shortcomings part of framework technology at that time, publish the book of " Expert One-on-One J2EE Design and Development ", summarize some experiences of his project development, analyze the reason etc. that EJB technology causes project failure, the content in this book became the core concept of Spring framework afterwards.

In conjunction with principle of work and the feature of Spring MVC, for the shortcoming that it is depended on Servlet API unduly and is unfavorable for unit testing, by encapsulation business logic processing class and interface, achieve the decoupling zero to Servlet.

Summary of the invention

The object of this invention is to provide a kind of MVC model-based optimization system based on Spring.

The object of the invention is to realize in the following manner, comprising:

1) core classes of Spring MVC framework and interface:

1. DispatcherServlet realizes the Design Mode of front controller, provides the node of central access;

2. request is mapped to processor by HandlerMapping interface, returns a processor and performs chain, comprise processor and multiple blocker;

3. SimpleUrlHandlerMapping, DefaultAnnotationHandlerMapping class realizes HandlerMapping interface, respectively by configuration file and note, is mapped to by URL on a controller class;

4. ViewResolver resolution logic view name is to specifically attempting to realize;

5. HandlerExceptionResolver resolves the exception run in implementation;

6. request is mapped to processor by DispatcherServlet, comprises and returns a HandlerExecutionChain, and it comprises a processor, multiple blocker;

2) controller

Controller obtains the request of client, and own handwriting supply and demand are changed into data model, carry out Web logical process, finally by suitable view, result is showed user, controller comprises core controller and service controller, core controller is responsible for receiving client's request, and service controller is responsible for the logic business processing request;

3) model and view package module

Model and view package module, encapsulate the handling procedure of model and view, for generation model and the view being illustrated in browser, model and view object are after DispatcherServlet process, be resolved as model and view two parts, then model be loaded in view and return to user;

Client's request processing step is as follows

1. Spring container carries out initialization according to the parameter in configuration file;

2. user sends request, and DispatcherServlet carries out logical process by submitting to core controller after request analysis;

3. model of creation view object, and request result is encapsulated into this object, return to DispatcherServlet;

4. DispatcherServlet analytic model view object, by result feedback to client.

Object beneficial effect of the present invention is: by the way, and the optimizing process of controller is that controller and Servlet API remove coupling completely, and provides the caching function of different stage scope, reaches the object that expection is optimized.

Embodiment

For the shortcoming that it is depended on Servlet API unduly and is unfavorable for unit testing, by encapsulation business logic processing class and interface, achieve the decoupling zero to Servlet.

Concrete steps are as follows:

1. create control unit interface OptimizingContext, statement obtains the method for HttpServletRequest and HttpServletResponse.The realizing class and can realize different functions according to different demands of this interface.Thus make subclass need not depend on the realization of parent.In Java, subclass can realize multiple interface, thus has greatly enriched the method for subclass object.

The code of this interface is as follows:

public interface OptimizingContext{

public HttpServletRequest getServletRequest();

public HttpServletResponse getServletResponse();

}

What create OptimizingContext interface realizes class OptimizingContextImpl, quoting of 4 Map objects is preserved in this type of, be respectively used to preserve page info (pageInfoMap), request msg (requestMap), session data (sessionMap), application data (applicationMap), realizing class is that 4 objects provide assignment and obtaining value method.

public class OptimizingContextImpl implements OptimizingContext{

static ThreadLocal ptimizingContext = new ThreadLocal();

private HttpServletRequest request;

public OptimizingContextImpl(Map<String ,Object> context){

this.context = context;

}

public HttpServletRequest getServletRequest(){

return request;

}

public void setServletRequest(){

this.request = request;

}

}

2. extending controller class

Controller class in Spring MVC framework achieves the control unit interface under spring framework, it provides a method and is used for processing user's request, and return corresponding model view.The controller of Spring definition is not directly realize control unit interface, but inherits extending controller class and realize;

3. controller optimization

Optimize the controller of Spring MVC framework, first the controller class designing oneself is needed, namely extending controller class is inherited, rewrite such handleRequstInternal method, key step is: the abstract classes creating the extension name presell phase, in subclass, create handle function, for the treatment of client's request, the specific implementation of Handle function is completed by abstract classes.

Except the technical characteristic described in instructions, be the known technology of those skilled in the art.

Claims (1)

1., based on a MVC model-based optimization system of Spring, it is characterized in that comprising:

1) core classes of Spring MVC framework and interface:

1. DispatcherServlet realizes the Design Mode of front controller, provides the node of central access;

2. request is mapped to processor by HandlerMapping interface, returns a processor and performs chain, comprise processor and multiple blocker;

3. SimpleUrlHandlerMapping, DefaultAnnotationHandlerMapping class realizes HandlerMapping interface, respectively by configuration file and note, is mapped to by URL on a controller class;

4. ViewResolver resolution logic view name is to specifically attempting to realize;

5. HandlerExceptionResolver resolves the exception run in implementation;

6. request is mapped to processor by DispatcherServlet, comprises and returns a HandlerExecutionChain, and it comprises a processor, multiple blocker;

2) controller

Controller obtains the request of client, and own handwriting supply and demand are changed into data model, carry out Web logical process, finally by suitable view, result is showed user, controller comprises core controller and service controller, core controller is responsible for receiving client's request, and service controller is responsible for the logic business processing request;

3) model and view package module

Model and view package module, encapsulate the handling procedure of model and view, for generation model and the view being illustrated in browser, model and view object are after DispatcherServlet process, be resolved as model and view two parts, then model be loaded in view and return to user;

Client's request processing step is as follows

1. Spring container carries out initialization according to the parameter in configuration file;

2. user sends request, and DispatcherServlet carries out logical process by submitting to core controller after request analysis;

3. model of creation view object, and request result is encapsulated into this object, return to DispatcherServlet;

4. DispatcherServlet analytic model view object, by result feedback to client.