Previous

Spring’s Dispatcher Servlet: test-servlet.xml You can break your xml files as you wish and can import all of them in test-servlet.xml so that during initialization of the application all of them will be loaded by the server as:


<import resource="/service.xml"><br /><br /><import resource= "classpath:/com/test/testproject/spring/admin/xyz.xml">


You have to give the url Mappings for different request types you want to handle by this servlet as:

<bean id="urlMapping1" class= "org.springframework.web.servlet.handler.SimpleUrlHandlerMapping"> <property name="mappings"> <props> <prop key="*Login.do">loginController</prop> </props> </property> </bean>

The above syntax means, whatever request comes containing text Login.do will be handled by the bean loginController. Bean loginController can be defined there as

<bean id="loginController" class= "com.test.testproject.spring.common.LoginController"> <property name="methodNameResolver"> <ref bean="loginMethodNameResolver"> </property> <property name="commonUtil"> <ref bean="commonUtil"> </property> </bean> <bean id="loginMethodNameResolver" class="org.springframework.web.servlet.mvc.multiaction.PropertiesMethodNameResolver"> <property name="mappings"> <props> <prop key="/Login.do">login</prop> <prop key="/LoginSubmit.do">formSubmit</prop> </props> </property> </bean>



In this definition, bean id is the name of the bean which should be unique among all application xml files. Class signifies the location of the actual java file.

There are mainly two types of controllers which can process request in Spring –

SimpleFormController and MultiActionController. SimpleFormControllers are the controllers can handle only one type of request where as MultiActionControllers can handle different types of request.

Here loginController, which extends MultiActionController, is a MultiActionControllers. In a MultiActionController like loginController there are different methods to handle different requests. To map between them a property provided by Spring “methodNameResolver“ is there which tells the Controller which method is to be invoked for a given request. Here that method name resolver bean is “loginMethodNameResolver”.

It tells that if request type is “/Login.do” then go to “login” method in the loginController and for “/LoginSubmit.do” request go to “formSubmit” method.

There are a lot of mappings of this kind which we have placed in other xml files and then all of them are imported in this test-servlet.xml. This type of break up will help in maintaining the changes in these files.

We have discussed mapping required for MultiActionController above. Following is the example of a SimpleFormController mapping:

<bean id="urlMapping5" class= "org.springframework.web.servlet.handler.SimpleUrlHandlerMapping"> <property name="mappings"> <props> <prop key="test/update.do">updateController</prop> </props> </property> </bean>


This controller, which extends SimpleFormController, handles request “test/update.do” only.Below is the example of a Controller, other than SimpleFormController and MultiAction Controller:

<bean id="urlMapping11" class= "org.springframework.web.servlet.handler.SimpleUrlHandlerMapping"> <property name="mappings"> <props> <prop key="ForgotPassword.do"> forgotPasswordController </prop> </props> </property> </bean> <bean id="forgotPasswordController" class= "com.test.testproject.spring.common.ForgotPasswordController"> </bean>


This “forgotPasswordController” handles only one request ”ForgotPassword.do”. This controller, which implements Controller Interface, only redirects the request to another controller or returns a simple model which contains nothing. We will see this Controller class later....

Next