Spring MVC 框架搭建及详解

 现在主流的Web MVC框架除了Struts这个主力 外,其次就是Spring MVC了,因此这也是作为一名程序员需要掌握的主流框架,框架选择多了,应对多变的需求和业务时,可实行的方案自然就多了。不过要想灵活运用Spring MVC来应对大多数的Web开发,就必须要掌握它的配置及原理。

  一、Spring MVC环境搭建:(Spring 2.5.6 + Hibernate 3.2.0)

  1. jar包引入

  Spring 2.5.6:spring.jar、spring-webmvc.jar、commons-logging.jar、cglib-nodep-2.1_3.jar

  Hibernate 3.6.8:hibernate3.jar、hibernate-jpa-2.0-api-1.0.1.Final.jar、antlr-2.7.6.jar、commons-collections-3.1、dom4j-1.6.1.jar、javassist-3.12.0.GA.jar、jta-1.1.jar、slf4j-api-1.6.1.jar、slf4j-nop-1.6.4.jar、相应数据库的驱动jar包

  2. web.xml配置(部分)

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
<!-- Spring MVC配置 -->
<!-- ====================================== -->
< servlet >
     < servlet-name >spring</ servlet-name >
     < servlet-class >org.springframework.web.servlet.DispatcherServlet</ servlet-class >
     <!-- 可以自定义servlet.xml配置文件的位置和名称,默认为WEB-INF目录下,名称为[<servlet-name>]-servlet.xml,如spring-servlet.xml
     <init-param>
         <param-name>contextConfigLocation</param-name>
         <param-value>/WEB-INF/spring-servlet.xml</param-value>  默认
     </init-param>
     -->
     < load-on-startup >1</ load-on-startup >
</ servlet >
 
< servlet-mapping >
     < servlet-name >spring</ servlet-name >
     < url-pattern >*.do</ url-pattern >
</ servlet-mapping >
   
 
 
<!-- Spring配置 -->
<!-- ====================================== -->
< listener >
     < listener-class >org.springframework.web.context.ContextLoaderListener</ listener-class >
</ listener >
   
 
<!-- 指定Spring Bean的配置文件所在目录。默认配置在WEB-INF目录下 -->
< context-param >
     < param-name >contextConfigLocation</ param-name >
     < param-value >classpath:config/applicationContext.xml</ param-value >
</ context-param >

  3. spring-servlet.xml配置

  spring-servlet这个名字是因为上面web.xml中<servlet-name>标签配的值为spring(<servlet-name>spring</servlet-name>),再加上“-servlet”后缀而形成的spring-servlet.xml文件名,如果改为springMVC,对应的文件名则为springMVC-servlet.xml。

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<? xml version = "1.0" encoding = "UTF-8" ?>
< beans xmlns = "http://www.springframework.org/schema/beans"    
        xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns:p = "http://www.springframework.org/schema/p"    
         xmlns:context = "http://www.springframework.org/schema/context"    
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd  
        http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-3.0.xsd  
        http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.0.xsd  
        http://www.springframework.org/schema/context <a  href = "http://www.springframework.org/schema/context/spring-context-3.0.xsd" >http://www.springframework.org/schema/context/spring-context-3.0.xsd</ a >">
 
     <!-- 启用spring mvc 注解 -->
     < context:annotation-config />
 
     <!-- 设置使用注解的类所在的jar包 -->
     < context:component-scan base-package = "controller" ></ context:component-scan >
 
     <!-- 完成请求和注解POJO的映射 -->
     < bean class = "org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter" />
 
     <!-- 对转向页面的路径解析。prefix:前缀, suffix:后缀 -->
     < bean class = "org.springframework.web.servlet.view.InternalResourceViewResolver" p:prefix = "/jsp/" p:suffix = ".jsp" />
</ beans >

  4. applicationContext.xml配置

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
<? xml version = "1.0" encoding = "UTF-8" ?>
< beans xmlns = "http://www.springframework.org/schema/beans"
         xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance"
         xmlns:aop = "http://www.springframework.org/schema/aop"
         xmlns:tx = "http://www.springframework.org/schema/tx"
         xsi:schemaLocation="
             http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
             http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop-2.5.xsd
             http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-2.5.xsd">
 
     <!-- 采用hibernate.cfg.xml方式配置数据源 -->
     < bean id = "sessionFactory" class = "org.springframework.orm.hibernate3.LocalSessionFactoryBean" >
         < property name = "configLocation" >
             < value >classpath:config/hibernate.cfg.xml</ value >
         </ property >
     </ bean >
     
     <!-- 将事务与Hibernate关联 -->
     < bean id = "transactionManager" class = "org.springframework.orm.hibernate3.HibernateTransactionManager" >
         < property name = "sessionFactory" >
             < ref local = "sessionFactory" />
         </ property >
     </ bean >
     
     <!-- 事务(注解 )-->
     < tx:annotation-driven transaction-manager = "transactionManager" proxy-target-class = "true" />
 
    <!-- 测试Service -->
    < bean id = "loginService" class = "service.LoginService" ></ bean >
 
     <!-- 测试Dao -->
     < bean id = "hibernateDao" class = "dao.HibernateDao" >
         < property name = "sessionFactory" ref = "sessionFactory" ></ property >
     </ bean >
</ beans >

 

  二、详解

  Spring MVC与Struts从原理上很相似(都是基于MVC架构),都有一个控制页面请求的Servlet,处理完后跳转页面。看如下代码(注解):

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
package controller;
 
import javax.servlet.http.HttpServletRequest;
 
import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestParam;
 
import entity.User;
 
@Controller  //类似Struts的Action
public class TestController {
 
     @RequestMapping ( "test/login.do" )   // 请求url地址映射,类似Struts的action-mapping
     public String testLogin( @RequestParam (value= "username" )String username, String password, HttpServletRequest request) {
         // @RequestParam是指请求url地址映射中必须含有的参数(除非属性required=false)
         // @RequestParam可简写为:@RequestParam("username")
 
         if (! "admin" .equals(username) || ! "admin" .equals(password)) {
             return "loginError" // 跳转页面路径(默认为转发),该路径不需要包含spring-servlet配置文件中配置的前缀和后缀
         }
         return "loginSuccess" ;
     }
 
     @RequestMapping ( "/test/login2.do" )
     public ModelAndView testLogin2(String username, String password,  int age){
         // request和response不必非要出现在方法中,如果用不上的话可以去掉
         // 参数的名称是与页面控件的name相匹配,参数类型会自动被转换
         
         if (! "admin" .equals(username) || ! "admin" .equals(password) || age <  5 ) {
             return new ModelAndView( "loginError" );  // 手动实例化ModelAndView完成跳转页面(转发),效果等同于上面的方法返回字符串
         }
         return new ModelAndView( new RedirectView( "../index.jsp" ));   // 采用重定向方式跳转页面
         // 重定向还有一种简单写法
         // return new ModelAndView("redirect:../index.jsp");
     }
 
     @RequestMapping ( "/test/login3.do" )
     public ModelAndView testLogin3(User user) {
         // 同样支持参数为表单对象,类似于Struts的ActionForm,User不需要任何配置,直接写即可
         String username = user.getUsername();
         String password = user.getPassword();
         int age = user.getAge();
         
         if (! "admin" .equals(username) || ! "admin" .equals(password) || age <  5 ) {
             return new ModelAndView( "loginError" );
         }
         return new ModelAndView( "loginSuccess" );
     }
 
     @Resource (name =  "loginService" )   // 获取applicationContext.xml中bean的id为loginService的,并注入
     private LoginService loginService;   //等价于spring传统注入方式写get和set方法,这样的好处是简洁工整,省去了不必要得代码
 
     @RequestMapping ( "/test/login4.do" )
     public String testLogin4(User user) {
         if (loginService.login(user) ==  false ) {
             return "loginError" ;
         }
         return "loginSuccess" ;
     }
}

  以上4个方法示例,是一个Controller里含有不同的请求url,也可以采用一个url访问,通过url参数来区分访问不同的方法,代码如下:

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
package controller;
 
import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;
 
@Controller
@RequestMapping ( "/test2/login.do" )   // 指定唯一一个*.do请求关联到该Controller
public class TestController2 {
     
     @RequestMapping
     public String testLogin(String username, String password,  int age) {
         // 如果不加任何参数,则在请求/test2/login.do时,便默认执行该方法
         
         if (! "admin" .equals(username) || ! "admin" .equals(password) || age <  5 ) {
             return "loginError" ;
         }
         return "loginSuccess" ;
     }
 
     @RequestMapping (params =  "method=1" , method=RequestMethod.POST)
     public String testLogin2(String username, String password) {
         // 依据params的参数method的值来区分不同的调用方法
         // 可以指定页面请求方式的类型,默认为get请求
         
         if (! "admin" .equals(username) || ! "admin" .equals(password)) {
             return "loginError" ;
         }
         return "loginSuccess" ;
     }
     
     @RequestMapping (params =  "method=2" )
     public String testLogin3(String username, String password,  int age) {
         if (! "admin" .equals(username) || ! "admin" .equals(password) || age <  5 ) {
             return "loginError" ;
         }
         return "loginSuccess" ;
     }
}

  其实RequestMapping在Class上,可看做是父Request请求url,而RequestMapping在方法上的可看做是子Request请求url,父子请求url最终会拼起来与页面请求url进行匹配,因此RequestMapping也可以这么写:

?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
package controller;
 
import org.springframework.stereotype.Controller;
import org.springframework.web.bind.annotation.RequestMapping;
 
@Controller
@RequestMapping ( "/test3/*" )   // 父request请求url
public class TestController3 {
 
     @RequestMapping ( "login.do" )   // 子request请求url,拼接后等价于/test3/login.do
     public String testLogin(String username, String password,  int age) {
         if (! "admin" .equals(username) || ! "admin" .equals(password) || age <  5 ) {
             return "loginError" ;
         }
         return "loginSuccess" ;
     }
}

 

  三、结束语

  掌握以上这些Spring MVC就已经有了很好的基础了,几乎可应对与任何开发,在熟练掌握这些后,便可更深层次的灵活运用的技术,如多种视图技术,例如 Jsp、Velocity、Tiles、iText 和 POI。Spring MVC框架并不知道使用的视图,所以不会强迫您只使用 JSP 技术。

面向对象设计的ACM论文 The concept of cohesion in a class has been the subject of various recent empirical studies and has been measured using many different metrics. In the structured programming paradigm, the software engineering community has adopted an informal yet meaningful and understandable definition of cohesion based on the work of Yourdon and Constantine. The object-oriented (OO) paradigm has formalised various cohesion measures, but the argument over the most meaningful of those metrics continues to be debated.Yet achieving highly cohesive software is fundamental to its comprehension and thus its maintainability. In this article we subject two object-oriented cohesion metrics, CAMC and NHD, to a rigorous mathematical analysis in order to better understand and interpret them. This analysis enables us to offer substantial arguments for preferring the NHD metric toCAMCas a measure of cohesion. Furthermore,we provide a complete understanding of the behaviour of these metrics, enabling us to attach a meaning to the values calculated by the CAMC and NHD metrics. In addition, we introduce a variant of the NHD metric and demonstrate that it has several advantages over CAMCand NHD. While it may be true that a generally accepted formal and informal definition of cohesion continues to elude the OO software engineering community, there seems considerable value in being able to compare, contrast, and interpret metrics which attempt to measure the same features of software.
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值