Hibernate + Spring + Struts Extension Struts

Introduction: I see many projects, developers have implemented their own MVC frameworks, not because they want to do different things with Struts, but because they don't realize how to extend Struts. Developing your own MVC framework can get all controls, but this also means that many resources are needed to achieve it (human material), in tense schedule, sometimes it is impossible. Struts is more than just a powerful framework, but it is also scalable. You can extend Struts in three ways. 1, Plugin: If you want to do some business logic during Application Startup or ShutDown, create your own Plugin class. 2, RequestProcessor: If you want to do some business logic in the process of being processed, create your own RequestProcessor class. For example, before each request is executed, you can extend the requestProcessor to check if the user logs in and whether he has permission to perform a particular action. 3, ActionServlet: If you want to do some business logic when you apply when Application Startup and ShutDown, you can also expand an ActionServlet class. However, you should use the ActionServlet when Plugin and RequestProcessor don't solve your needs. In this article, we will use an example of a Struts application to demonstrate how to use these three ways to expand Struts. The code for the sample program can be downloaded from http://www.onjava.com/onjava/2004/11/examples/sample1.zip. Two extensions Struts successful examples are the Validation and Tiles frameworks of Struts themselves. We assume that you are more familiar with the struts framework and know how to use it to create a simple application. If you want to know more about Struts, please refer to the official homepage. Plugin Plugin is an interface that you can create a class that implements the interface, do something when Application Startup or Shutdown is. For example, I created a web application using Hibernate as a persistent layer. I want to initialize Hibernate when I am started. So when I am a first request, Hibernate is already configured and usable. At the same time, we want to close hibernate when Application is closed. We can use a Hibernate Plugin to achieve this demand, through the following two steps: 1. Create a class to implement the Plugin interface:

public class HibernatePlugIn implements PlugIn {private String configFile; // This method will be called at application shutdown time public void destroy () {System.out.println ( "Entering HibernatePlugIn.destroy ()"); // Put hibernate cleanup code here System.out.println ( "Exiting HibernatePlugIn.destroy ()");} // This method will be called at application startup time public void init (ActionServlet actionServlet, ModuleConfig config) throws ServletException {System.out.println ( "Entering HibernatePlugIn .init () "); system.out.println (" Value of Init Parameter " getConfigfile ()); System.out.Println (" EXITING HibernatePlugin.init () ");} public string getconfigfile () {Return Name } Public void setconfigfile (String String) {configfile = string;}} The class that implements the PLUGIN interface must complete two methods: init () and destroy (). When the application startup is called, the destroy () method is called when Shutdown is called. Struts also allows you to transfer initialization parameters to your PLUGIN class. In order to pass parameters, you must create a JavaBean setter method for each parameter in the Plugin class. In our hibernatePlugin class, I will pass the CONFIGFILE's Name as the parameters, not the hardcoded to the program. 2, add the following code to Struts-Config.xml to advertise Struts has new Plugin:

... attribute classname is a class that implements the Plugin interface Late limit. For each initialization parameter, you can transfer parameters using the element. In our example, I want to pass the name of the config file, so use a with the configuration file path. The Struts Tiles and Validator frameworks use Plugin to read the configuration file for initialization. The other two plugins can help you do what you do is: · If your Application relies on some configuration files, you can check if they can be used in the plugin class, if you are not available, throw a servletexception, so you can make ActionServlet becomes unavailable. • The init () method of the Plugin interface is that you can change the last chance of ModuleConfig, and ModuleConfig is a set of static configuration information to describe the Struts module. Struts will release ModuleConfig after all PLUGIN processing. Request is how the ActionServlet is the only servlet in the Struts framework, which is responsible for processing all Request. Whenever you receive a request, it will try to find a sub-application for the current request. Once a Sub-Application is found, the ActionServlet creates a requestProcessor object for that sub-application, calls the Process () method of this object and incorporates the HttpServletRequest and HttpservletResponse objects. RequestProcessor.Process () is where most Request is processed. The Process () method uses the Template Method mode implementation, where there are many independent methods to perform each step of request processing, which will be called in turn in the Process method. For example, there will be an independent method to find the ActionForm class corresponding to the current Request, one way to check if the current user has permission to perform an action mapping. These give us great flexibility. A RequestProcessor class is provided in the release Struts package provides the request to process the default implementation of each step. This means you can only rewrite the way you are interested in, others use the default implementation.

For example, by default Struts calls request.isuserinrole () to check if the user has permission to execute current actionMApping; if you want to implement the database, you have to do it is to rewrite the processroles () method, by querying The user has a must-have necessary permissions to return True or False. First we will see how the process () method is implemented by default, then I will explain every method in the default RequestProcessor class so that you can decide which part is what you want to change.

public void process (HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException {// Wrap multipart requests with a special wrapper request = processMultipart (request); // Identify the path component we will // use to select a mapping String path = processPath (Request, Response); if (path == null) {return;}}}}}}}}}}}} {log.debug ("Processing A '" Request.getMethod () "' for path '" PATH " '");} // Select a Locale for the current user if requested processLocale (request, response); // Set the content type and no-caching headers // if requested processContent (request, response); processNoCache (request , response); (! processPreprocess (request, response) // General purpose preprocessing hook if) {return;} // Identify the mapping for this request ActionMapping mapping = processMapping (request, response, path); if (mapping == null ) {RETURN;} // check for any role required to perform this action if (! ProcessRoles (Request, Response , Mapping)) {return;} // Process any ActionForm bean related to this request ActionForm form = processActionForm (request, response, mapping); processPopulate (request, response, form, mapping);! If (processValidate (request, response, form, mapping)) {return;}! // Process a forward or include specified by this mappingif (processForward (request, response, mapping)) {return;}! if (processInclude (request, response, mapping)) {return; } // crete or acquire the action instance to // process this requestaction action = processactioncreate (request, response, mapping); if (action == null) {return;

} // Call the Action instance itselfActionForward forward = processActionPerform (request, response, action, form, mapping); // Process the returned ActionForward instanceprocessForwardConfig (request, response, forward);} 1, processMutipart (): In this method, Struts will read the request to check if the recuestTYPE is Multipart / Form-Data. If so, the request will be parsed and packaged into the httpservletRequest. When you create an HTML Form to submit the data, the Request's ContentType default is Application / X-WWW-form-Urlencoded. But if your Form uses the file type INPUT control allows the user to upload files, you must change ContentType to Multipart / Form-Data. If this is the case, you cannot get the data submitted by getParameter (); you must read the request as an InputStream and parsing it to get the parameter value. 2, ProcessPath (): In this method, Struts will read the REQUEST URI to determine the path element, which is used to get the actionMAppint element. 3, ProcessLocale (): In this method, Struts will get Locale for the current REQUEST. If you are configured, you can save this object as the value of the org.apache.struts.Action.Locale property in httpsession. As the side effects of this method, HttpSession will be created. If you don't want to create, you can set the local property to false in ControllerConfig, as follows: 4, processcontent (): Sets ContentType for Response.SetContentType (). This method first attempts to get ContentType from the struts-config.xml configuration. Text / html is used by default. If you want to override it, you can like this:

5, processnocache (): If the configuration is no-cache, Struts will set the following three headers below for each response :

Requested in struts config.xmlresponse.setheader ("Pragma", "No-cache"); Response.setHeader ("cache-control", "no-cache"); response.setdateHeader ("expires", 1); if you Want to set up no-cache header, add the following information in Struts-Config.xml: 6, processpreprocess (): This method is Pretreatment provides a hook that can overwrite it in the subclass. Its default implementation does not make anything, always returns True. Returns False will terminate the process of current request. 7, ProcessMapping (): This method will get an actionMApping object with the path information. That is, the element in the struts-config.xml file:

ActionMapping element contains the name of the Action class and the ActionForm such as processing requests. It also contains the ActionForWards information that current ActionMapping configuration. 8, ProcessRoles (): Struts web application provides an authorization scheme. That is, once a user logs into the container, the struts's processroles () method will check if he has a necessary role to run a given actionMApping by calling request.isuserinrole ().

Hypothesis You have an AddUseraction and you just want administrator to add new User. What you have to do is adding a role property to your addUseraction element, the value of this property is Administrator. This way, this method ensures that the user has an Administraotr role before running addUseraction. 9, Processctionform (): Each ActionMApping is a corresponding ActionForm class. When Struts processes an actionMApping, it will find the name of the corresponding Actionform class from the Name property of the element.

In our example, it will check if there is an org.apache.struts.Action.DynaActionform class in the Request Scope exists. If it will use this object, if it doesn't have a new object and set it in the Request Scope. 10, ProcessPopulate (): In this method, Struts will be equipped with instance variables of ActionForm with matching request parameters. 11, ProcessValidate (): Struts will call the Validate method for your ActionForm class. If you return ActionerRRORS from validate (), it will redirect the user to the page specified by the INPUT property of the element. 12, ProcessForward () and Process (): In these methods, Struts will check the Forward or Include properties of the element. If it is found, the Forward or Include request is placed into the configuration page.

You can guess their differences from these methods: ProcessForward () Finally call RequestDispatcher.Forward (), and processinclude () calls requestDispatcher.include (). If you configure the Forward and Include properties simultaneously, it will always call forward because forward is first processed. 13, ProcessActionCreate (): This method gets the name of the Action class from the type of element and creates an instance that returns it. In our example, it will create an instance of a COM.SAMPLE.NEWContActAction class. 14, ProcessActionPerform (): This method calls your Action class Excute () method, your business logic is also in the Excute method. 15, ProcessForwardConfig (): The Excute () method of your Action class will return an ActionForward object, which will point out which page is displayed to the user. Therefore, Struts will create a RequestDispatcher for that page and call RequestDispatcher.Forward (). The above list illustrates the default RequestProcessor implementation every step in processing the request, as well as the order of execution. As you can see, RequestProcessor is very flexible, allowing you to configure it by setting the properties of the element. For example, if your application is ready to generate XML content instead of HTML, you can notify Struts by setting the properties of the Controller element. Create your own requestProcessor through the above, we learned how the default implementation of the requestProcessor works. Now we have to demonstrate an example to explain how to customize your own requestProcessor. To display the Creating User-customized RequestProcessor, we will make our examples to implement the following two business needs: • We want to create a ContactImageAction class, which will generate a picture instead of the normal HTML page. · Before each request is handled, we want to determine if the user has already logged in by checking the username attribute in the session. If that property is not found, we will redirect the user to the landing page. We will implement these business needs in two steps. 1. Create your CustomRequestProcessor class, which will inherit from the RequestProcessor class, as follows:

public class CustomRequestProcessorextends RequestProcessor {protected boolean processPreprocess (HttpServletRequest request, HttpServletResponse response) {HttpSession session = request.getSession (false); // If user is trying to access login page // then do not check if (request.getServletPath () . Equals ("/ logininput.do") || request.getServletPath (). Equals ("/ login.do")) Return true; // check if username attribute is there is session. // if So, IT means User has allready logged in if (session = null && session.getAttribute ( "userName") = null!!) return true; else {try {// If no redirect user to login Page request.getRequestDispatcher ( "/ Login.jsp") .forward (request, response);} catch (Exception ex) {}} return false;} protected void processContent (HttpServletRequest request, HttpServletResponse response) {// Check if user is requesting ContactImageAction // if yes then set image / gif as Content Type if (Request.getServletPath (). Equals ("/ ContactImage .do ")) {response.setContentType (" image / gif "); return;} super.processContent (Request, Response);}} In the processpreprocess method for the CustomRequestProcessor class, we check the session username properties, if not found, Redirect the user to the landing page. For the demand for generating pictures as output, we must override the ProcessContent method, first check whether the request is / contactimage path. If so, we will set the contentType to Image / GIF; otherwise set to Text / HTML. 2, add the following text after your Struts-Config.xml file, tell the struts CustomRequestProcessor to be used as the RequestProcessor class:

Please note that when you only have little Action class to generate a non-text / html type output You overwrite the processcontent () method is OK. If you are not like this, you should create a Struts sub-application to process the request to generate an action, and set contentType to Image / GIF for them. The TILES framework for Struts is to use its own requestProcessor to decorate the output of Struts. ActionServlet If you view the web.xml of your struts web app, you will see such text: action = Org. Apache.struts.Action.ActionServlet action *. Do This means that the ActionServlet is responsible for handling all the Struts requests. You can create an ActionServlet subclass, do some specific things when applying start, close, do some specific things when requesting. But before inheriting the ActionServlet class, you should try to create a plugin or requestProcessor to solve your problem. Before servlet1.1, the TILES framework is based on ActionServlet to modify the generated response. But after 1.1, it starts using the TileSRequestProcessor class. Summary Deciding to develop your own MVC framework is a very big decision, you have to consider the time and resources spending the development and maintenance of the frame code. Struts is a very powerful and stable framework that you can modify it to meet the most of your business needs. But on the other hand, it is not necessary to make an expansion of Struts. If you write some performance relatively low code in RequestProcessor, it will execute each time, thus reducing your efficiency of your entire application. And there are still some situations that develop your own MVC framework is better than extended Struts.