天堂中文在线8,伊人久久av,日韩亚洲视频在线观看

topquan — Wed, 09 Aug 2006 15:25:00 GMT

摘要: This is Part 4 of a step-by-step account of how to develop a web application from scratch using the Spring Framework. In Part 1 (Steps 1 – 12) we configured the environment and set up a basic ap... 阅读全文

topquan 2006-08-09 23:25 发表评论

Developing a Spring Framework MVC application �Q�三�Q?

topquan — Wed, 09 Aug 2006 15:23:00 GMT

This is Part 3 of a step-by-step account of how to develop a web application from scratch using the Spring Framework. In Part 1 (Steps 1 – 19) we configured the environment and set up a basic application that we will build upon. Part 2 (Steps 13-19) improved the application in several ways. We are now going to add some unit tests to the application.

Step 20 – Add unit test for the SpringappController

Before we create any unit tests, we want to prepare Ant and our build script to be able to handle this. Ant has a built in JUnit target, but we need to add junit.jar to Ant's lib directory. I used the one that came with the Spring distribution spring-framework-1.2/lib/junit/junit.jar. Just copy this file to the lib directory in your Ant installation. I also added the following target to our build script.

												    
                    
                           fork="false"
                           haltonfailure="false"
                           failureproperty="tests.failed"
                           showoutput="true">
                        
                        
                        
                            
                                
                            
                        
                    
                    
        tests.failed=${tests.failed}
        ***********************************************************        ***********************************************************        ****  One or more tests failed!  Check the output ...  ****        ***********************************************************        ***********************************************************

Now I add a new sub-directory in the src directory that I name tests. This directory will, as you might have guessed, contain all the unit tests.

After all this, we are ready to start writing the first unit test. The SpringappController depends on both the HttpServletRequest, HttpServletResponse and our application context. Since the controller does not use the request or the response, we can simply pass in null for these objects. If that was not the case, we could create some mock objects using EasyMock that we would pass in during our test. The application context can be loaded outside of a web server environment using a class that will load an application context. There are several available, and for the current task the FileSystemXmlApplicationContext works fine.

springapp/src/tests/TestSpringappController.java

package tests;

import java.util.Map;
import java.util.List;
import java.io.IOException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.ServletException;
import junit.framework.TestCase;
import org.springframework.context.ApplicationContext;
import org.springframework.context.support.FileSystemXmlApplicationContext;
import org.springframework.web.servlet.ModelAndView;
import web.SpringappController;
import bus.ProductManager;
import bus.Product;

public class TestSpringappController extends TestCase {

    private ApplicationContext ac;

    public void setUp() throws IOException {
        ac = new FileSystemXmlApplicationContext("src/tests/WEB-INF/springapp-servlet.xml");
    }

    public void testHandleRequest() throws ServletException, IOException {
        SpringappController sc = (SpringappController) ac.getBean("springappController");
        ModelAndView mav = sc.handleRequest((HttpServletRequest) null, (HttpServletResponse) null);
        Map m = mav.getModel();
        List pl = (List) ((Map) m.get("model")).get("products");
        Product p1 = (Product) pl.get(0);
        assertEquals("Lamp", p1.getDescription());
        Product p2 = (Product) pl.get(1);
        assertEquals("Table", p2.getDescription());
        Product p3 = (Product) pl.get(2);
        assertEquals("Chair", p3.getDescription());
    }

}

The only test is a call to handleRequest, and we check the products that are returned in the model. In the setUp method, we load the application context that I have copied into a WEB-INF directory in the src/tests directory. I create a copy just so this file will work during tests with a small set of beans necessary for running the tests. So, copy springapp/war/WEB-INF/springapp-servlet.xml to springapp/src/tests/WEB-INF directory. You can then remove the “messageSource”, "urlMapping" and "viewResolver" bean entries since they are not needed for this test.

springapp/src/tests/WEB-INF/springapp-servlet.xml








    >                                                                                                                                    Lamp        5.75                Table        75.25                Chair        22.79

When you run this test, you should see a lot of log messages from the loading of the application context.

Step 21 – Add unit test and new functionality for ProductManager

Next I add a test case for the ProductManager, and I also add a test for a new method to increase the prices that I am planning on adding to the ProductManager.

springapp/src/tests/TestProductManager .java

package tests;

import java.util.List;
import java.util.ArrayList;
import junit.framework.TestCase;
import bus.ProductManager;
import bus.Product;

public class TestProductManager extends TestCase {

    private ProductManager pm;

    public void setUp() {
        pm = new ProductManager();
        Product p = new Product();
        p.setDescription("Chair");
        p.setPrice(new Double("20.50"));
        ArrayList al = new ArrayList();
        al.add(p);
        p = new Product();
        p.setDescription("Table");
        p.setPrice(new Double("150.10"));
        al.add(p);
        pm.setProducts(al);
    }

    public void testGetProducs() {
        List l = pm.getProducts();
        Product p1 = (Product) l.get(0);
        assertEquals("Chair", p1.getDescription());
        Product p2 = (Product) l.get(1);
        assertEquals("Table", p2.getDescription());
    }

    public void testIncreasePrice() {
        pm.increasePrice(10);
        List l = pm.getProducts();
        Product p = (Product) l.get(0);
        assertEquals(new Double("22.55"), p.getPrice());
        p = (Product) l.get(1);
        assertEquals(new Double("165.11"), p.getPrice());
    }

}

For this test, there is no need to create an application context. I just create a couple of products in the setUp method and add them to the product manager. I add tests for both getProducts and increasePrice. The increasePrice method is a cross the board increase based on the percentage passed in to the method. I modify the ProductManager class to implement this new method.

springapp/src/bus/ProductManager.java

package bus;

import java.io.Serializable;
import java.util.ListIterator;
            import java.util.List;
            public class ProductManager implements Serializable {
            private List products;
            public void setProducts(List p) {
            products = p;
            }
            public List getProducts() {
            return products;
            }
                public void increasePrice(int pct) {        ListIterator li = products.listIterator();        while (li.hasNext()) {            Product p = (Product) li.next();            double newPrice = p.getPrice().doubleValue() * (100 + pct)/100;            p.setPrice(new Double(newPrice));        }    }
            }

Next I build and run the tests. As you can see, this test is just like any regular test – the business classes don't depend on any of the servlet classes so these classes are very easy to test.

Step 22 – Adding a form

To provide an interface in the web application, I add a form that will allow the user to enter a percentage value. This form uses a tag library named “spring” that is provided with the Spring Framework. We have to copy this file from the Spring distribution spring-framework-1.2/dist/spring.tld to the springapp/war/WEB-INF directory. Now we must also add a entry to web.xml.

springapp/war/WEB-INF/web.xml






      springapp    org.springframework.web.servlet.DispatcherServlet    1        springapp    *.htm              index.jsp            /spring    /WEB-INF/spring.tld

We also have to declare this taglib in a page directive in the jsp file. We declare a form the normal way with a

tag and an text field and a submit button.

springapp/war/WEB-INF/jsp/priceincrease.jsp

<%@ include file="/WEB-INF/jsp/include.jsp" %>
<%@ taglib prefix="spring" uri="/spring" %>


<fmt:message key="title"/>



  



        



          Increase (%):       
          ">
                
          
                  
  

  

  
    Please fix all errors!
  
  


  

">Home

The tag is used to bind an form element to a command object PriceIncrease.java, that is used together with the form. This command object is later passed in to the validator and if it passes validation it is passed on to the controller. The ${status.errorMessage} and ${status.value} are special variables declared by the framework that can be used to display error messages and the current value of the field.

springapp/src/bus/PriceIncrease.java

package bus;

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

public class PriceIncrease {

    /** Logger for this class and subclasses */
    protected final Log logger = LogFactory.getLog(getClass());

    private int percentage;

    public void setPercentage(int i) {
        percentage = i;
        logger.info("Percentage set to " + i);
    }

    public int getPercentage() {
        return percentage;
    }

}

This is a very simple JavaBean class, and in our case there is a single property with a getter and setter. The validator class gets control after the user presses submit. The values entered in the form will be set on the command object by the framework. The method validate is called and the command object and an object to hold any errors are passed in.

springapp/src/bus/PriceIncreaseValidator.java

package bus;

import java.io.Serializable;
import org.springframework.validation.Validator;
import org.springframework.validation.Errors;

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

public class PriceIncreaseValidator implements Validator {
    private int DEFAULT_MIN_PERCENTAGE = 0;
    private int DEFAULT_MAX_PERCENTAGE = 50;
    private int minPercentage = DEFAULT_MIN_PERCENTAGE;
    private int maxPercentage = DEFAULT_MAX_PERCENTAGE;

    /** Logger for this class and subclasses */
    protected final Log logger = LogFactory.getLog(getClass());

    public boolean supports(Class clazz) {
        return clazz.equals(PriceIncrease.class);
    }

    public void validate(Object obj, Errors errors) {
        PriceIncrease pi = (PriceIncrease) obj;
        if (pi == null) {
            errors.rejectValue("percentage", "error.not-specified", null, "Value required.");
        }
        else {
            logger.info("Validating with " + pi + ": " + pi.getPercentage());
            if (pi.getPercentage() > maxPercentage) {
                errors.rejectValue("percentage", "error.too-high",
                    new Object[] {new Integer(maxPercentage)}, "Value too high.");
            }
            if (pi.getPercentage() <= minPercentage) {
                errors.rejectValue("percentage", "error.too-low",
                    new Object[] {new Integer(minPercentage)}, "Value too low.");
            }
        }
    }

    public void setMinPercentage(int i) {
        minPercentage = i;
    }

    public int getMinPercentage() {
        return minPercentage;
    }

    public void setMaxPercentage(int i) {
        maxPercentage = i;
    }

    public int getMaxPercentage() {
        return maxPercentage;
    }

}

Now we need to add an entry in the springapp-servlet.xml file to define the new form and controller. We define properties for command object and validator. We also specify two views, one that is used for the form and one that we will go to after successful form processing. The latter which is called the success view can be of two types. It can be a regular view reference that is forwarded to one of our JSP pages. One disadvantage with this approach is, that if the user refreshes the page, the form data is submitted again, and you would end up with a double priceincrease. An alternative way is to use a redirect, where a response is sent back to the users browser instructing it to redirect to a new url. The url we use in this case can't be one of our JSP pages, since they are hidden from direct access. It has to be a url that is externally reachable. I have choosen to use 'hello.htm' as my redirect url. This url maps to the 'hello.jsp' page, so this should work nicely.

springapp/war/WEB-INF/springapp-servlet.xml


 "http://www.springframework.org/dtd/spring-beans.dtd">





    
            
            
            
            
            
                                true        priceIncrease        bus.PriceIncrease                priceincrease        hello.htm                                
            
            
            
            
            
            
            
            
            
            
            Lamp
            5.75
            
            
            Table
            75.25
            
            
            Chair
            22.79
            
            
            messages
            
            
            
            
            springappController
                            priceIncreaseForm
            
            
            
            
            
            org.springframework.web.servlet.view.JstlView
            
            /WEB-INF/jsp/
            .jsp

Next, let's take a look at the controller for this form. The onSubmit method gets control and does some logging before it calls the increasePrice method on the ProductManager object. It then returns a ModelAndView passing in a new instance of a RedirectView created using the url for the successView.

springapp/src/web/PriceIncreaseFormController.java

package web;

import org.springframework.web.servlet.mvc.SimpleFormController;
import org.springframework.web.servlet.ModelAndView;
import org.springframework.web.servlet.view.RedirectView;

import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import java.io.IOException;
import java.util.Map;
import java.util.HashMap;

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

import bus.Product;
import bus.ProductManager;
import bus.PriceIncrease;

public class PriceIncreaseFormController extends SimpleFormController {

    /** Logger for this class and subclasses */
    protected final Log logger = LogFactory.getLog(getClass());

    private ProductManager prodMan;

    public ModelAndView onSubmit(Object command)
            throws ServletException {

        int increase = ((PriceIncrease) command).getPercentage();
        logger.info("Increasing prices by " + increase + "%.");

        prodMan.increasePrice(increase);

        String now = (new java.util.Date()).toString();
        logger.info("returning from PriceIncreaseForm view to " + getSuccessView();

        return new ModelAndView(new RedirectView(getSuccessView()));
    }

    protected Object formBackingObject(HttpServletRequest request) throws ServletException {

        PriceIncrease priceIncrease = new PriceIncrease();
        priceIncrease.setPercentage(20);

        return priceIncrease;

    }

    public void setProductManager(ProductManager pm) {
        prodMan = pm;
    }

    public ProductManager getProductManager() {
        return prodMan;
    }

}

We are also adding some messages to the messages.properties resource file.

springapp/war/WEB-INF/classes/messages.properties

title=SpringApp
heading=Hello :: SpringApp
greeting=Greetings, it is now
priceincrease.heading=Price Increase :: SpringApperror.not-specified=Percentage not specified!!!error.too-low=You have to specify a percentage higher than {0}!error.too-high=Don't be greedy - you can't raise prices by more than {0}%!required=Entry required.typeMismatch=Invalid data.typeMismatch.percentage=That is not a number!!!

Finally, we have to provide a link to the priceincrease page from the hello.jsp.

springapp/war/WEB-INF/jsp/hello.jsp

<%@ include file="/WEB-INF/jsp/include.jsp" %>


<fmt:message key="title"/>


 

Products


   $




">Increase Prices

Compile and deploy all this and after reloading the application we can test it. This is what the form looks like with errors displayed.

topquan 2006-08-09 23:23 发表评论

topquan — Wed, 09 Aug 2006 15:22:00 GMT

This is Part 2 of a step-by-step account of how to develop a web application from scratch using the Spring Framework. In Part 1 (Steps 1 – 12) we configured the environment and set up a basic application that we will build upon.

This is what we have to start with.

An introduction page index.jsp.
A DispatcherServlet with a corresponding springapp-servlet.xml configuration file.
A controller springappController.java.
A view hello.jsp.

We will now improve on these parts to build a more useful application.

Step 13 – Improve index.jsp

We will make use of JSP Standard Tag Library (JSTL) so I will start by copying the JSTL files we need to our WEB-INF/lib directory. Copy jstl.jar from the 'spring-framework-1.2/lib/j2ee' directory and standard.jar from the 'spring-framework-1.2/lib/jakarta-taglibs' directory to the springapp/war/WEB-INF/lib directory. I am also creating a “header” file that will be included in every JSP page that I'm going to write. This will make development easier and I will be sure that I have the same definitions in all JSPs. I am going to put all JSPs in a directory named jsp under the WEB-INF directory. This will ensure that only the controller has access to the views - it is not possible to get to these pages by entering them directly as a URL in the browser. This strategy might not work in all application servers and if this is the case with the one you are using, just move the jsp directory up a level. You would then use springapp/war/jsp as the directory instead of springapp/war/WEB-INF/jsp in all the code examples that will follow.

springapp/war/WEB-INF/jsp/include.jsp

<%@ page session="false"%>

<%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
<%@ taglib prefix="fmt" uri="http://java.sun.com/jstl/fmt" %>

Now we can change index.jsp to use this include and since we are using JSTL we can use the tag for redirecting to our Controller. This ties the index.jsp into our application framework.

springapp/war/index.jsp

<%@ include file="/WEB-INF/jsp/include.jsp" %>

<%-- Redirected because we can't set the welcome page to a virtual URL. --%>

Step 14 – Improve the view and the controller

I am going to move the view hello.jsp to the WEB-INF/jsp directory. The same include that was added to index.jsp gets added to hello.jsp. I also add the current date and time as output that I will retrieve from the model, passed to the view, using the JSTL tag.

springapp/war/WEB-INF/jsp/hello.jsp

<%@ include file="/WEB-INF/jsp/include.jsp" %>

Hello :: Spring Application

Hello - Spring Application

Greetings, it is now

For SpringappController.java there are a few changes we need to make. Change the view to WEB-INF/jsp/hello.jsp since we moved the file to this new location. Also add a string containing the current data and time as the model.

springapp/src/SpringappController.java

import org.springframework.web.servlet.mvc.Controller;
import org.springframework.web.servlet.ModelAndView;

import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import java.io.IOException;

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

public class SpringappController implements Controller {

    /** Logger for this class and subclasses */
    protected final Log logger = LogFactory.getLog(getClass());

    public ModelAndView handleRequest(HttpServletRequest request, HttpServletResponse response)
            throws ServletException, IOException {

        String now = (new java.util.Date()).toString();         logger.info("returning hello view with " + now);        return new ModelAndView("WEB-INF/jsp/hello.jsp", "now", now);
            }
            }

Now we are ready to try this after we build and deploy this new code. We enter http://localhost:8080/springapp in a browser and that should pull up index.jsp, which should redirect to hello.htm, which in turn gets us to the controller that sends the data and time to the view.

Step 15 – Decouple the view and the controller

Right now the controller specifies the full path of the view, which creates an unnecessary dependency between the controller and the view. Ideally we would like to map to the view using a logical name, allowing us to switch the view without having to change the controller. You can set this mapping in a properties file if you like using a ResourceBundleViewResolver and a SimpleUrlHandlerMapping class. If your mapping needs are simple it is easier to just set a prefix and a suffix on the InternalResourceViewResolver. The latter approach is the one that I will implement now, so I modify the springapp-servlet.xml and include this viewResolver entry. I have elected to use a JstlView which will enable us to use JSTL in combination with message resource bundles and it will also support internationalization.

springapp/war/WEB-INF/springapp-servlet.xml







    

    
        
            
                springappController
            
        
    

            org.springframework.web.servlet.view.JstlView        /WEB-INF/jsp/        .jsp

So now I can remove the prefix and suffix from the view name in the controller.

springapp/src/SpringappController.java

import org.springframework.web.servlet.mvc.Controller;
import org.springframework.web.servlet.ModelAndView;

import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import java.io.IOException;

import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

public class SpringappController implements Controller {

    /** Logger for this class and subclasses */
    protected final Log logger = LogFactory.getLog(getClass());

    public ModelAndView handleRequest(HttpServletRequest request, HttpServletResponse response)
            throws ServletException, IOException {

        String now = (new java.util.Date()).toString();
        logger.info("returning hello view with " + now);

return new ModelAndView("hello", "now", now);
            }
            }

Compile and deploy and the application should still work.

Step 16 – Add some classes for business logic

So far our application is not very useful. I would like to add a little bit of business logic in form of a Product class and a class that will manage all the products. I name this management class ProductManager. In order to separate the web dependent logic from the business logic I will create two separate packages for the Java source – web and bus. If this was an application for a real company I would name the packages something like com.mycompany.web and com.mycompany.bus, but since this is just a demo application I will keep the package names real short. The Product class is implemented as a JavaBean – it has the default constructor (automatically provided if we don't specify any constructors) and getters and setters for the two instance variables description and price. I also make it Serializable, not necessary for our application, but could come in handy later on if we have to pass this class between different application layers.

springapp/src/bus/Product.java

package bus;

import java.io.Serializable;

public class Product implements Serializable {

    private String description;
    private Double price;

    public void setDescription(String s) {
        description = s;
    }

    public String getDescription() {
        return description;
    }

    public void setPrice(Double d) {
        price = d;
    }

    public Double getPrice() {
        return price;
    }

}

The ProductManager holds a List of Products, and again this this class is implemented as a JavaBean.

springapp/src/bus/ProductManager.java

package bus;

import java.io.Serializable;
import java.util.List;

public class ProductManager implements Serializable {

    private List products;

    public void setProducts(List p) {
        products = p;
    }

    public List getProducts() {
        return products;
    }

}

Next, I modify the SpringappController to hold a reference to this ProductManager class. As you can see, it is now in a separate package called web – remember to move the source to this new location. I also add code to have the controller pass some product information to the view. The getModelAndView now returns a Map with both the date and time and the product manager reference.

springapp/src/web/SpringappController.java

package web;

import org.springframework.web.servlet.mvc.Controller;
import org.springframework.web.servlet.ModelAndView;

import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import java.io.IOException;
import java.util.Map;import java.util.HashMap;
            import org.apache.commons.logging.Log;
            import org.apache.commons.logging.LogFactory;
            import bus.Product;import bus.ProductManager;
            public class SpringappController implements Controller {
            /** Logger for this class and subclasses */
            protected final Log logger = LogFactory.getLog(getClass());
                private ProductManager prodMan;
            public ModelAndView handleRequest(HttpServletRequest request, HttpServletResponse response)
            throws ServletException, IOException {
            String now = (new java.util.Date()).toString();
            logger.info("returning hello view with " + now);
                    Map myModel = new HashMap();        myModel.put("now", now);        myModel.put("products", getProductManager().getProducts());        return new ModelAndView("hello", "model", myModel);
            }
                public void setProductManager(ProductManager pm) {        prodMan = pm;    }    public ProductManager getProductManager() {        return prodMan;    }
            }

Step 17 – Modify the view to display business data and add support for message bundle

Using the JSTL tag, I add a section that displays product information. I have also replaced the title, heading and greeting text with a JSTL tag that pulls the text to display from a provided 'message' source – I will show this source in a later step.

springapp/war/WEB-INF/jsp/hello.jsp

<%@ include file="/WEB-INF/jsp/include.jsp" %>


<fmt:message key="title"/>


             

Products   $

Step 18 – Add some test data to automatically populate some business objects

I am not going to add any code to load the business objects from a database just yet. Instead, we can “wire up” a couple of instances using Spring's bean and application context support. I will simply put the data I need as a couple of bean entries in springapp-servlet.xml. I will also add the messageSource entry that will pull in the messages resource bundle ('messages.properties') that I will create in the next step.

springapp/war/WEB-INF/springapp-servlet.xml








    >                                                                                                                                            Lamp        5.75                Table        75.25                Chair        22.79                messages    
            
            
            
            springappController
            
            
            
            
            org.springframework.web.servlet.view.JstlView
            /WEB-INF/jsp/
            .jsp

Step 19 – Add the message bundle and a 'clean' target to build.xml

I create a 'messages.properties' file in the war/WEB-INF/classes directory. This properties bundle so far has three entries matching the keys specified in the tags that we added to the hello.jsp.

springapp/war/WEB-INF/classes/messages.properties

title=SpringApp
heading=Hello :: SpringApp
greeting=Greetings, it is now

Since we moved some source files around, it makes sense to add a 'clean' and an 'undeploy' target to the build scripts. I add the following entries to the build.xml file.

Now stop the Tomcat server, run the clean, undeploy and deploy targets. This should remove all old class files, re-build the application and deploy it. Start up Tomcat again and you should see the following:

topquan 2006-08-09 23:22 发表评论

topquan — Wed, 09 Aug 2006 15:21:00 GMT

This is a step-by-step account of how to develop a web application from scratch using the Spring Framework.

Prerequisites:

Java SDK (I am currently using version 1.4.2)
Ant (using version 1.6.2)
Apache Tomcat (using version 5.0.28)

You should also be reasonably comfortable using the above software.

I am not going to cover a lot of background information or theory in this document -- there are plenty of books available that covers this in depth. Instead we will dive right into developing the application.

Step 1 – development directory

We are going to need a place to keep all the source and other files we will be creating, so I create a directory that I name 'springapp'. You can place this directory in your home folder or in some other location. I created mine in a 'projects' directory that I already had in my home directory so the full path to my directory is '/Users/trisberg/projects/springapp'. Inside this directory I create a 'src' directory to hold all Java source files. Then I create another directory that I name 'war'. This directory will hold everything that should go into the WAR file, that we would use to deploy our application. All source files other than Java source, like JSPs and configuration files, belongs in this directory.

Step 2 – index.jsp

I will start by creating a JSP page named 'index.jsp' in the war directory. This is the entry point for our application.

springapp/war/index.jsp

Example :: Spring Application

Example - Spring Application

This is my test.

Just to have a complete web application, I create a web.xml in a WEB-INF directory that I create under the war directory.

springapp/war/WEB-INF/web.xml

Step 3 – deploying the application to Tomcat

Next, I write an Ant build script that we are going to use throughout this document. There are tasks for building and deploying the application. A separate build script contains the app server specific tasks There are also tasks for controlling the application under Tomcat.

springapp/build.xml




    

    
    
    
    

    
        
            
        
        
        
        
        
        
            
        
        
    

    
        
        
        
        
        
        
        
        
        
        
        
        
        
        
        
    

    
        
                       deprecation="false" optimize="false" failonerror="true">
            
            
        
    

    
        
            
                
            
        
    

    
                     webxml="${web.dir}/WEB-INF/web.xml">
            
                
            
        
        
            
                
            
        
    





    
        
            
        
    
    
        
            
        
    
    
        
            
        
    
    
        
            
        
    
    
        
            
        
    

    
                         username="${tomcat.manager.username}"
                 password="${tomcat.manager.password}"
                 path="/${name}"
                 war="${name}"/>
    

    
                         username="${tomcat.manager.username}"
                 password="${tomcat.manager.password}"
                 path="/${name}"/>
    

    
                         username="${tomcat.manager.username}"
                 password="${tomcat.manager.password}"
                 path="/${name}"/>
    

    
                         username="${tomcat.manager.username}"
                 password="${tomcat.manager.password}"
                 path="/${name}"/>
    

    
                         username="${tomcat.manager.username}"
                 password="${tomcat.manager.password}"/>

This script now contains all the targets that we are going to need to make our development efforts easier. I am not going to cover this script in detail since most if not all of it is pretty much standard Ant and Tomcat stuff. You can just copy the above build file and put it at the root of your development directory tree. We also need a build.properties file that you should customize to match your server installation. This file belongs in the same directory as the build.xml file.

springapp/build.properties

# Ant properties for building the springapp

appserver.home=${user.home}/jakarta-tomcat-5.0.28
deploy.path=${appserver.home}/webapps

tomcat.manager.url=http://localhost:8080/manager
tomcat.manager.username=admin
tomcat.manager.password=tomcat

If you are on a system where you are not the owner of the Tomcat install, then the Tomcat owner must either grant you full access to the webapps directory or the owner must create a new directory named 'springapp' in the 'webapps' directory of the Tomcat installation, and also give you full rights to deploy to this newly created directory. On Linux I run the command chmod a+rwx springapp to give everybody full rights to this directory.

If you are using a different web application server, then you can remove the Tomcat specific tasks at the end of the build script. You will have to rely on your server's hot deploy feature, or you will have to stop and start your application manually.

Now I run Ant to make sure that everything is working OK. You should have your current directory set to the 'springapp' directory.

												[trisberg@localhost springapp]$ ant
            Buildfile: build.xml
            
            
            usage:
            
            
                 [echo] springapp build file
                 [echo] -----------------------------------
            
            
                 [echo] Available targets are:
            
            
                 [echo] build     --> Build the application
                 [echo] deploy    --> Deploy application as directory
                 [echo] deploywar --> Deploy application as a WAR file
                 [echo] install   --> Install application in Tomcat
                 [echo] reload    --> Reload application in Tomcat
                 [echo] start     --> Start Tomcat application
                 [echo] stop      --> Stop Tomcat application
                 [echo] list      --> List Tomcat applications
            
            
            
            
            BUILD SUCCESSFUL
            Total time: 2 seconds

Last action here is to do the actual deployment. Just run Ant and specify 'deploy' or 'deploywar' as the target.

												[trisberg@localhost springapp]$ ant deploy
            Buildfile: build.xml
            
            
            build:
    [mkdir] Created dir: /Users/trisberg/projects/springapp/war/WEB-INF/classes

deploy:
     [copy] Copying 2 files to /Users/trisberg/jakarta-tomcat-5.0.28/webapps/springapp


            BUILD SUCCESSFUL
            Total time: 2 seconds

Step 4 – Test the application

Let's just quickly start Tomcat and make sure that we can access the application. Use the 'list' task from our build file to see if Tomcat has picked up the new application.

												[trisberg@localhost springapp]$ ant list
            Buildfile: build.xml
            
            
            list:
     [list] OK - Listed applications for virtual host localhost

     [list] /admin:running:0:/Users/trisberg/jakarta-tomcat-5.0.28/server/webapps/admin

     [list] /webdav:running:0:/Users/trisberg/jakarta-tomcat-5.0.28/webapps/webdav

     [list] /servlets-examples:running:0:/Users/trisberg/jakarta-tomcat-5.0.28/webapps/servlets-examples

    [list] /springapp:running:0:/Users/trisberg/jakarta-tomcat-5.0.28/webapps/springapp

     [list] /jsp-examples:running:0:/Users/trisberg/jakarta-tomcat-5.0.28/webapps/jsp-examples

     [list] /balancer:running:0:balancer

     [list] /tomcat-docs:running:0:/Users/trisberg/jakarta-tomcat-5.0.28/webapps/tomcat-docs

     [list] /:running:0:/Users/trisberg/jakarta-tomcat-5.0.28/webapps/ROOT

     [list] /manager:running:0:/Users/trisberg/jakarta-tomcat-5.0.28/server/webapps/manager

            
            
            
            
            BUILD SUCCESSFUL
            Total time: 1 second

If it is not listed, use the 'install' task to get the application installed in Tomcat.

												[trisberg@localhost springapp]$ ant install
            Buildfile: build.xml
            
            
            install:
              [install] OK - Installed application at context path /springapp
            
            
            
            
            BUILD SUCCESSFUL
            Total time: 2 seconds

Now open a browser and browse to http://localhost:8080/springapp/index.jsp.

Step 5 – Download Spring distribution

If you have not already downloaded the Spring Framework Release file, now is the time to do so. I am currently using 'spring-framework-1.2-with-dependencies.zip' that can be downloaded from www.springframework.org/download.html. I unzipped this file in my home directory. We are going to use several files from this download later on.

This completes the setup of the environment that is necessary, and now we can start actually developing our Spring Framework MVC application.

Step 6 – Modify web.xml in WEB-INF directory

Go to the 'springapp/war/ WEB-INF' directory. Modify the minimal 'web.xml' file that we created earlier. Now we will modify it to suit our needs. We define a DispatcherServlet that is going to control where all our request are routed based on information we will enter at a later point. It also has a standard servlet-mapping entry that maps to the url patterns that we will be using. I have decided to let any url with an '.htm' extension be routed to the 'springapp' dispatcher.

springapp/war/WEB-INF/web.xml






      springapp    org.springframework.web.servlet.DispatcherServlet    1        springapp    *.htm              index.jsp

Next, create a file called 'springapp-servlet.xml' in the springapp/war/WEB-INF directory (you can copy an example of this file from the Spring distributions sample/skeletons/webapp-minimal directory). This is the file where definitions used by the DispatcherServlet should be entered. It is named based on the servlet-name from web.xml with '-servlet' appended. This is a standard naming convention used in the Spring Framework. Now, add a bean entry named springappController and make the class SpringappController. This defines the controller that our application will be using. We also need to add a url mapping so the DispatcherServlet knows which controller should be invoked for different url:s.

springapp/war/WEB-INF/springapp-servlet.xml







    

    
        
            
                springappController

Step 7 – Copy jars to WEB-INF/lib

First create a 'lib' directory in the 'war/WEB-INF' directory. Then, from the Spring distribution, copy spring.jar (spring-framework-1.2/dist/spring.jar) to the new war/WEB-INF/lib directory. Also copy commons-logging jars to the war/WEB-INF/lib directory (spring-framework-1.2/lib/jakarta-commons/commons-logging.jar). We are also going to need a log4j jar. Copy log4j-1.2.9.jar to the war/WEB-INF/lib directory (spring-framework-1.2/lib/log4j/log4j-1.2.9.jar). These jars will be deployed to the server and they are also used during the build process.

Step 8 – Create your Controller

Create your Controller – I named mine SpringappController.java and placed it in the springapp/src directory.

springapp/src/SpringappController.java

import org.springframework.web.servlet.mvc.Controller;
import org.springframework.web.servlet.ModelAndView;

import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import java.io.IOException;

public class SpringappController implements Controller {

    public ModelAndView handleRequest(HttpServletRequest request, HttpServletResponse response)
            throws ServletException, IOException {
        return new ModelAndView("");
    }
}

This is as basic a Controller as you can use. We will be expanding this later on, and we will also later on extend some provided abstract base implementations. The Controller “handles” the request and returns a ModelAndView. We have not yet defined any Views, so right now there is nothing to do.

Step 9 – Build the Application

Run the 'build' task of the build.xml. Hopefully the code compiles OK.

												[trisberg@localhost springapp]$ ant build
            Buildfile: build.xml
            
            
            build:
                [javac] Compiling 1 source file to /Users/trisberg/projects/springapp/war/WEB-INF/classes
            
            
            BUILD SUCCESSFUL
            Total time: 2 seconds

Step 10 – Copy and modify log4j.properties

The Spring Framework uses log4j for logging so we have to create a configuration file for log4j. Copy the log4j.properties from the sample Petclinic application (spring-framework-1.2/samples/petclinic/war/WEB-INF/log4j.properties) to the war/WEB-INF/classes directory (this directory should have been created in the previous step). Now uncomment or modify the log4j.rootCategory property and change the name and location of the logfile that will be written. I decided to have it written to the same directory as all other Tomcat logs.

springapp/war/WEB-INF/classes/log4j.properties

# For JBoss: Avoid to setup Log4J outside $JBOSS_HOME/server/default/deploy/log4j.xml!
# For all other servers: Comment out the Log4J listener in web.xml to activate Log4J.
log4j.rootLogger=INFO, stdout, logfile

log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d %p [%c] - <%m>%n

log4j.appender.logfile=org.apache.log4j.RollingFileAppender
log4j.appender.logfile.File=/Users/trisberg/jakarta-tomcat-5.0.28/logs/springapp.log
log4j.appender.logfile.MaxFileSize=512KB
# Keep three backup files.
log4j.appender.logfile.MaxBackupIndex=3
# Pattern to output: date priority [category] - message
log4j.appender.logfile.layout=org.apache.log4j.PatternLayout
log4j.appender.logfile.layout.ConversionPattern=%d %p [%c] - %m%n

Step 11 – Deploy Application

Run the 'deploy' task and then the 'stop' and 'start' tasks of the build.xml. This will force a reload of the application. We have to check the Tomcat logs for any deployment errors – there could be typos in the above xml files or there could be missing classes or jar files. This is an example of what it should look like. (/Users/trisberg/jakarta-tomcat-5.0.28/logs/springapp.log)

												2005-04-24 14:58:18,112 INFO [org.springframework.web.servlet.DispatcherServlet] - Initializing servlet 'springapp'
2005-04-24 14:58:18,261 INFO [org.springframework.web.servlet.DispatcherServlet] - FrameworkServlet 'springapp': initialization started
2005-04-24 14:58:18,373 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] - Loading XML bean definitions from ServletContext resource [/WEB-INF/springapp-servlet.xml]
2005-04-24 14:58:18,498 INFO [org.springframework.web.context.support.XmlWebApplicationContext] - Bean factory for application context [WebApplicationContext for namespace 'springapp-servlet']: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [springappController,urlMapping]; root of BeanFactory hierarchy
2005-04-24 14:58:18,505 INFO [org.springframework.web.context.support.XmlWebApplicationContext] - 2 beans defined in application context [WebApplicationContext for namespace 'springapp-servlet']
2005-04-24 14:58:18,523 INFO [org.springframework.core.CollectionFactory] - JDK 1.4+ collections available
2005-04-24 14:58:18,524 INFO [org.springframework.core.CollectionFactory] - Commons Collections 3.x available
2005-04-24 14:58:18,537 INFO [org.springframework.web.context.support.XmlWebApplicationContext] - Unable to locate MessageSource with name 'messageSource': using default [org.springframework.context.support.DelegatingMessageSource@8dacb]
2005-04-24 14:58:18,539 INFO [org.springframework.web.context.support.XmlWebApplicationContext] - Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster@5674a4]
2005-04-24 14:58:18,549 INFO [org.springframework.ui.context.support.UiApplicationContextUtils] - No ThemeSource found for [WebApplicationContext for namespace 'springapp-servlet']: using ResourceBundleThemeSource
2005-04-24 14:58:18,556 INFO [org.springframework.beans.factory.support.DefaultListableBeanFactory] - Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [springappController,urlMapping]; root of BeanFactory hierarchy]
2005-04-24 14:58:18,557 INFO [org.springframework.beans.factory.support.DefaultListableBeanFactory] - Creating shared instance of singleton bean 'springappController'
2005-04-24 14:58:18,603 INFO [org.springframework.beans.factory.support.DefaultListableBeanFactory] - Creating shared instance of singleton bean 'urlMapping'
2005-04-24 14:58:18,667 INFO [org.springframework.web.servlet.DispatcherServlet] - Using context class [org.springframework.web.context.support.XmlWebApplicationContext] for servlet 'springapp'
2005-04-24 14:58:18,668 INFO [org.springframework.web.servlet.DispatcherServlet] - Unable to locate MultipartResolver with name 'multipartResolver': no multipart request handling provided
2005-04-24 14:58:18,670 INFO [org.springframework.web.servlet.DispatcherServlet] - Unable to locate LocaleResolver with name 'localeResolver': using default [org.springframework.web.servlet.i18n.AcceptHeaderLocaleResolver@318309]
2005-04-24 14:58:18,675 INFO [org.springframework.web.servlet.DispatcherServlet] - Unable to locate ThemeResolver with name 'themeResolver': using default [org.springframework.web.servlet.theme.FixedThemeResolver@c11e94]
2005-04-24 14:58:18,681 INFO [org.springframework.web.servlet.DispatcherServlet] - No HandlerAdapters found in servlet 'springapp': using default
2005-04-24 14:58:18,700 INFO [org.springframework.web.servlet.DispatcherServlet] - No ViewResolvers found in servlet 'springapp': using default
2005-04-24 14:58:18,700 INFO [org.springframework.web.servlet.DispatcherServlet] - FrameworkServlet 'springapp': initialization completed in 439 ms
2005-04-24 14:58:18,704 INFO [org.springframework.web.servlet.DispatcherServlet] - Servlet 'springapp' configured successfully

Step 12 – Create a View

Now it is time to create our first view. I will use a JSP page that I decided to name hello.jsp. I'll put it in the war directory to begin with.

springapp/war/hello.jsp

Example :: Spring Application

Hello - Spring Application

Greetings.

Nothing fancy here, but it will do for now. Next we have to modify the SpringappController to forward to this view.

springapp/src/SpringappController.java

import org.springframework.web.servlet.mvc.Controller;
import org.springframework.web.servlet.ModelAndView;

import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;

import java.io.IOException;

import org.apache.commons.logging.Log;import org.apache.commons.logging.LogFactory;
            public class SpringappController implements Controller {
                /** Logger for this class and subclasses */    protected final Log logger = LogFactory.getLog(getClass());
            public ModelAndView handleRequest(HttpServletRequest request, HttpServletResponse response)
            throws ServletException, IOException {
            logger.info("SpringappController - returning hello view");
            return new ModelAndView("hello.jsp");
    }
}

While I was modifying this class, I also added a logger so we can verify that we actually got here. Changes are highlighted in red. The model that this class returns is actually resolved via a ViewResolver. Since we have not specified a specific one, we are going to get a default one that just forwards to a url matching the name of the view specified. We will modify this later on.

Now compile and deploy the application. After instructing Tomcat to stop and then start the application, everything should get reloaded.

Let's try it in a browser – enter the url http://localhost:8080/springapp/hello.htm and we should see the following:

We can also check the log – I'm only showing the last entries, but we can see that the controller did get invoked and that it forwarded to the hello view. (/Users/trisberg/jakarta-tomcat-5.0.28/logs/springapp.log)

												2005-04-24 15:01:56,217 INFO [org.springframework.web.servlet.DispatcherServlet] - FrameworkServlet 'springapp': initialization completed in 372 ms
2005-04-24 15:01:56,217 INFO [org.springframework.web.servlet.DispatcherServlet] - Servlet 'springapp' configured successfully
2005-04-24 15:03:57,908 INFO [SpringappController] - SpringappController - returning hello view

Summary

Let's take quick look at the parts of our application that we have created so far.

An introduction page index.jsp that does not do anything useful. It was just used to test our setup. We will later change this to actually provide a link into our application.
A DispatcherServlet with a corresponding springapp-servlet.xml configuration file.
A controller springappController.java with limited functionality – it just forwards a ModelAndView to the ViewResolver. Actually, we only have an empty model so far, but we will fix this later.
A view hello.jsp that again is extremely basic. But the whole setup works and we are now ready to add more functionality.

topquan 2006-08-09 23:21 发表评论

eclipse下struts+spring+hibernate快速入门（二）

topquan — Wed, 09 Aug 2006 15:15:00 GMT

Web层．
创徏Struts Action�Q��ؓ了在一个action中实现CRUD操作�Q�Action�l�承了DispatchAction�Ҏ��参数军_��调用�Ҏ��。在src/com.jandar.web.struts.action下创建UserAction.java
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.apache.struts.action.ActionForm;
import org.apache.struts.action.ActionForward;
import org.apache.struts.action.ActionMapping;
import org.apache.struts.action.ActionMessage;
import org.apache.struts.action.ActionMessages;
import org.apache.struts.action.DynaActionForm;
import org.apache.struts.actions.DispatchAction;
import com.jandar.model.User;
import com.jandar.service.spring.UserManager;
public class UserAction extends DispatchAction {
private static Log log = LogFactory.getLog(UserAction.class);
private UserManager mgr = null;
public void setUserManager(UserManager userManager) {
this.mgr = userManager;
}
public ActionForward delete(ActionMapping mapping, ActionForm form,
HttpServletRequest request,
HttpServletResponse response)
throws Exception {
if (log.isDebugEnabled()) {
log.debug("entering ''delete'' method...");
}
mgr.removeUser(request.getParameter("user.id"));
ActionMessages messages = new ActionMessages();
messages.add(ActionMessages.GLOBAL_MESSAGE,
new ActionMessage("user.deleted"));
saveMessages(request, messages);
return list(mapping, form, request, response);
}
public ActionForward edit(ActionMapping mapping, ActionForm form,
HttpServletRequest request,
HttpServletResponse response)
throws Exception {
if (log.isDebugEnabled()) {
log.debug("entering ''edit'' method...");
}
DynaActionForm userForm = (DynaActionForm) form;
String userId = request.getParameter("id");
// null userId indicates an add
if (userId != null) {
User user = mgr.getUser(userId);
if (user == null) {
ActionErrors errors = new ActionMessages();
errors.add(ActionMessages.GLOBAL_MESSAGE,
new ActionMessage("user.missing"));
saveErrors(request, errors);
return mapping.findForward("list");
}
userForm.set("user", user);
}
return mapping.findForward("edit");
}
public ActionForward list(ActionMapping mapping, ActionForm form,
HttpServletRequest request,
HttpServletResponse response)
throws Exception {
if (log.isDebugEnabled()) {
log.debug("entering ''list'' method...");
}
request.setAttribute("users", mgr.getUsers());
return mapping.findForward("list");
}
public ActionForward save(ActionMapping mapping, ActionForm form,
HttpServletRequest request,
HttpServletResponse response)
throws Exception {
if (log.isDebugEnabled()) {
log.debug("entering ''save'' method...");
}
// run validation rules on this form
ActionErrors errors = form.validate(mapping, request);
if (!errors.isEmpty()) {
saveErrors(request, errors);
return mapping.findForward("edit");
}
DynaActionForm userForm = (DynaActionForm) form;
mgr.saveUser((User)userForm.get("user"));
ActionMessages messages = new ActionMessages();
messages.add(ActionMessages.GLOBAL_MESSAGE,
new ActionMessage("user.saved"));
saveMessages(request, messages);
return list(mapping, form, request, response);
}
public ActionForward unspecified(ActionMapping mapping, ActionForm form,
HttpServletRequest request,
HttpServletResponse response)
throws Exception {
return list(mapping, form, request, response);
}
}
UserAction.java通过UserManger讉K��业务层，UserManager通过依赖注入
2�Q?创徏struts ActionFrom
可以在src/com.jandar.web.struts.form下创��Z��个UserForm.java的struts ActionForm�Q�我们也可以采用已徏好的模型来配�|�form bean即采用动态form
org.apache.struts.validator.DynaValidatorForm 同时指定property �?br>com.jandar.model.User详见struts-config.xml配置文�g.

配置struts-config.xml
1�Q?配置struts-config.xml

"-//Apache Software Foundation//DTD Struts Configuration 1.2//EN"
"

name="userForm" type="org.apache.struts.validator.DynaValidatorForm">

name="userForm" scope="request" parameter="method" validate="false">

2�Q?通过struts-config.xml把struts和spring�l�合��h��
UserAction.java中的UserManager需要通过依赖注入�Q�通过plug-in技术将spring加到struts中，在struts-config.xml中增加一下代�?br>
value="/WEB-INF/applicationContext.xml,
/WEB-INF/action-servlet.xml"/>

让struts启动同时初始化spring�Q�读取spring的配�|�文件applicationContext.xml,�q�且把struts的action也交�l�spring��理�Q�把action配置到action-servlet.xml�?br>新徏action-servlet.xml

"

同时��action映射到org.springframework.web.struts.DelegatingActionProxy即修�?br>name="userForm" scope="request" parameter="method" validate="false">

3�Q?新徏web.xml配置文�g

xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee

action

org.apache.struts.action.ActionServlet

config

/WEB-INF/struts-config.xml

debug

detail

action

*.do

index.jsp

4�Q?新徏index.jsp,userList.jsp,userForm.jsp
index.jsp
<%@ page language="java"%>

<%@ taglib uri="

index.jsp

List all user

userForm.jsp
<%@ page language="java"%>
<%@ taglib uri="

userform.jsp

id:
lastname:

userList.jsp
<%@ page language="java"%>
<%@ taglib uri="
<%@ taglib uri="
<%@ taglib uri="
<%@ taglib uri="
<%@ taglib uri="
<%@ taglib uri="
<%@ taglib uri="

userList.jsp

This a struts page.

id	firstName	lastName
">

topquan 2006-08-09 23:15 发表评论

topquan — Wed, 09 Aug 2006 15:14:00 GMT

本文是开发基于spring的web应用的入门文章，前端采用Struts MVC框架�Q�中间层采用spring�Q�后台采用Hibernate�?
概览
本文包含以下内容�Q?
•配置Hibernate和事�?•装蝲Spring的applicationContext.xml文�g
•建立业务层和DAO之间的依赖关�p?•��Spring应用到Struts�?
�q�个例子是徏立一个简单的web应用�Q�叫MyUsers,完成用户��理操作�Q�包含简单的数据库增�Q�删�Q�查�Q�该即CRUD�Q�新建，讉K��Q�更斎ͼ�删除�Q�操作。这是一个三层的web应用�Q�通过Action�Q�Struts�Q�访问业务层�Q�业务层讉K��DAO。应用的��M��l�构�Q�从web�Q�UserAction�Q�到中间层（UserManager�Q�，再到数据讉K��层（UserDAO�Q�，然后��结果返回�?
Spring层的真正强大在于它的声明型事务处理，帮定和对持久层支持（例如Hiberate和iBATIS�Q?
以下是完成这个例子的步骤�Q?
1�Q�安装Eclipse插�g 2�Q�数据库�� 3�Q�配�|�Hibernate和Spring
4�Q�徏立Hibernate DAO接口的实现类 5�Q�运行测试类�Q�测试DAO的CRUD操作
6�Q�创��Z��个处理类�Q�声明事�?nbsp; 7�Q�创建Struts Action的测试类
8�Q�创建web层的Action和model 9�Q�运行Action的测试类��试CRUD操作
10�Q�创建jsp文�g通过��览器进行CRUD操作 11�Q�通过��览器校验jsp
开发环�?br>Eclipse3.0.1 , MyEclispe 3.8.4, MySQL4.1.8, spring-framework-1.2.6-with-dependencies,Tomcat5.0
   数据库徏�?nbsp; use appfuse;
CREATE TABLE app_user (
id int(11) NOT NULL auto_increment,
firstname varchar(20) NOT NULL,
lastname varchar(20) ,
PRIMARY KEY (id)
);
    新徏��目
新徏一个web project�Q�分别add struts,hibernate capabilities.��spring 包中的dist 文�g夹中的jar文�g拯��到WEB-INF/lib中�?br>创徏持久层O/R mapping
1�Q?在src/com.jandar.model下用hibernate插�g从数据库导出app_user�?hbm.xml文�g改名为User.hbm.xml

                            "-//Hibernate/Hibernate Mapping DTD 2.0//EN"
                            "

2�Q�在com.jandar.model下分别徏 BaseObject.java 和User.java
package com.jandar.model;
import java.io.Serializable;
import org.apache.commons.lang.builder.EqualsBuilder;
import org.apache.commons.lang.builder.HashCodeBuilder;
import org.apache.commons.lang.builder.ToStringBuilder;
import org.apache.commons.lang.builder.ToStringStyle;
public class BaseObject implements Serializable {
public String toString() {
return ToStringBuilder.reflectionToString(this, ToStringStyle.MULTI_LINE_STYLE);
}
public boolean equals(Object o) {
return EqualsBuilder.reflectionEquals(this, o);
}
public int hashCode() {
return HashCodeBuilder.reflectionHashCode(this);
}
}
package com.jandar.model;
public class User extends BaseObject {
private Long id;
private String firstName;
private String lastName;
/**
* @return Returns the id.
*/
public Long getId() {
return id;
}
/**
* @param id The id to set.
*/
public void setId(Long id) {
this.id = id;
}
public void getFirstName() {
return firstName;
}

public void setFirstName(String firstName) {
this.firstName = firstName;
}
public String getLastName() {
return lastName;
}
public void setLastName(String lastName) {
this.lastName = lastName;
}
}
创徏DAO�Q�访问对�?
1�Q?在src/com.jandar.service.dao新徏IDAO.java接口�Q�所有的DAO都��承该接口
package com.jandar.service.dao;
public interface IDAO {
}
2�Q?在src/com.jandar.service.dao下新建IUserDAO.java接口
package com.jandar.service.dao;
import java.util.List;
public interface IUserDAO extends IDAO {
List getUsers();
User getUser(Integer userid);
void saveUser(User user);
void removeUser(Integer id);
}
该接口提供了讉K��对象的方法，
3�Q?在src/com.jandar.service.dao.hibernate下新建UserDAOHiberante.java
package com.jandar.service.dao.hibernate;
import java.util.List;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import org.springframework.orm.hibernate.support.HibernateDaoSupport;
import com.jandar.model.User;
import com.jandar.service.dao.IUserDAO;
public class UserDaoHibernate extends HibernateDaoSupport implements IUserDAO {
private Log log=LogFactory.getLog(UserDaoHibernate.class);
/* �Q�非 Javadoc�Q?
* @see com.jandar.dao.IUserDAO#getUsers()
*/
public List getUsers() {
return getHibernateTemplate().find("from User");
}
/* �Q�非 Javadoc�Q?
* @see com.jandar.dao.IUserDAO#getUser(java.lang.Long)
*/
public User getUser(Integer id) {
// TODO 自动生成�Ҏ��存根
return (User) getHibernateTemplate().get(User.class,id);
}
/* �Q�非 Javadoc�Q?
* @see com.jandar.dao.IUserDAO#saveUser(com.jandar.model.User)
*/
public void saveUser(User user) {
log.debug("xxxxxxx");
System.out.println("yyyy");
getHibernateTemplate().saveOrUpdate(user);
if(log.isDebugEnabled())
{
log.debug("userId set to "+user.getId());
}
}
/* �Q�非 Javadoc�Q?
* @see com.jandar.dao.IUserDAO#removeUser(java.lang.Long)
*/
public void removeUser(Integer id) {
Object user=getHibernateTemplate().load(User.class,id);
getHibernateTemplate().delete(user);
if(log.isDebugEnabled()){
log.debug("del user "+id);
}
}
}
在这个类中实��C��IUserDAO接口的方法，�q�且�l�承了HibernateDAOSupport�c�R��这个类的作用是通过hibernate讉K��、操作对象，�q�而实现对数据库的操作�?
创徏业务层，声明事务
业务层主要处理业务逻辑�Q�提供给web层友好的讉K��接口和实现访问DAO层。用业务层的另一个好处是�Q�可以适应数据讉K��层从Hibernate技术�{�U�d��其他数据讉K��技术�?
1�Q?在src/com.jandar.service下新��Z��个IUserManager接口�Q�该接口有几乎于IUserDAO同样的方法，不同的是处理参数�Q�应为IUserManager是供web层访问的�?
package com.jandar.service;
import java.util.List;
import com.jandar.model.User;
public interface IUserManager {
User getUser(String userid);
List getUsers();
User saveUser(User user);
void removeUser(String userid);
}
2�Q?在src/com.jandar.service.spring下新建IUserManager实现�c�，UserManager.java
package com.jandar.service.spring;
import java.util.List;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
import com.jandar.model.User;
import com.jandar.service.IUserManager;
import com.jandar.service.dao.IUserDAO;
public class UserManager implements IUserManager {
/* �Q�非 Javadoc�Q?
* @see com.jandar.service.IUserManager#getUser(java.lang.String)
*/
private static Log log=LogFactory.getLog(UserManager.class);
public IUserDAO userDao;
/**
* @return �q�回 userDao�?
*/
public IUserDAO getUserDao() {
return userDao;
}
/**
* @param userDao 要设�|�的 userDao�?
*/
public void setUserDao(IUserDAO userDao) {
this.userDao = userDao;
}
public User getUser(String userid) {
User user=userDao.getUser(Integer.valueOf(userid));
if(user==null){
log.warn(" user id "+userid+" not found in database");
}
if(log.isDebugEnabled()){
log.debug("get a user with id "+userid);
}
return user;
}
/* �Q�非 Javadoc�Q?
* @see com.jandar.service.IUserManager#getUsers()
*/
public List getUsers() {
// TODO 自动生成�Ҏ��存根
return userDao.getUsers();
}
/* �Q�非 Javadoc�Q?
* @see com.jandar.service.IUserManager#saveUser(com.jandar.model.User)
*/
public User saveUser(User user) {
// TODO 自动生成�Ҏ��存根
userDao.saveUser(user);
return user;
}
/* �Q�非 Javadoc�Q?
* @see com.jandar.service.IUserManager#removeUser(java.lang.String)
*/
public void removeUser(String userid) {
// TODO 自动生成�Ҏ��存根
userDao.removeUser(Integer.valueOf(userid));
}
}
UserManager.java通过讉K��dao接口实现业务逻辑和数据库操作。同时该�c�M��提供了set�Ҏ��Q�运用了Spring的依赖注入机制。但��未使用spring的AOP和声明事务�?
配置applicationContext.xml
在WEB-INF 下新建applicationContext.xml

class="org.springframework.jdbc.datasource.DriverManagerDataSource">

com.mysql.jdbc.Driver

jdbc:mysql://localhost:3306/appfuse

root

class="org.springframework.orm.hibernate.LocalSessionFactoryBean">

com/jandar/model/User.hbm.xml

net.sf.hibernate.dialect.MySQLDialect

create

class="org.springframework.transaction.interceptor.TransactionProxyFactoryBean">

PROPAGATION_REQUIRED

PROPAGATION_REQUIRED,readOnly

singleton="false">

topquan 2006-08-09 23:14 发表评论

�q�入 Spring MVC

topquan — Wed, 09 Aug 2006 14:26:00 GMT

Spring MVC 框架

　　Spring 框架提供了构�?Web 应用�E�序的全功能 MVC 模块。��?Spring 可插入的 MVC 架构�Q�可以选择是��用内�|�的 Spring Web 框架�q�是 Struts �q�样�?Web 框架。通过�{�略接口�Q�Spring 框架是高度可配置的，而且包含多种视图技术，例如 JavaServer Pages�Q�JSP�Q�技术、Velocity、Tiles、iText �?POI。Spring MVC 框架�q�不知道使用的视图，所以不会强�q�您只��?JSP 技术。Spring MVC 分离了控制器、模型对象、分�z�֙�以及处理�E�序对象的角�Ԍ��q�种分离让它们更�Ҏ��q�行定制�?/p>

　　Spring �?Web MVC 框架是围�l?DispatcherServlet 设计的，它把��h��分派�l�处理程序，同时带有可配�|�的处理�E�序映射、视图解析、本地语�a�、主题解析以及上载文件支持。默认的处理�E�序是非常简单的 Controller 接口�Q�只有一个方�?ModelAndView handleRequest(request, response)。Spring 提供了一个控制器层次�l�构�Q�可以派生子�c�R��如果应用程序需要处理用戯��入表单，那么可以�l�承 AbstractFormController。如果需要把多页输入处理��C��个表单，那么可以�l�承 AbstractWizardFormController�?/p>

　　�C�Z��应用�E�序有助于直观地学习�q�些�Ҏ��。银行应用程序允许用��h��索他们的帐户信息。在构徏银行应用�E�序的过�E�中�Q�可以学到如何配�|?Spring MVC 框架和实现框架的视图层，视图层包�?JSTL 标记�Q�用于显�C��出的数据�Q�和JavaServer Pages 技术�?/p>

　　配置 Spring MVC

　　要开始构建示例应用程序，请配�|?Spring MVC �?DispatcherServlet。请�?web.xml 文�g中注册所有配�|�。清�?1 昄��了如何配�|?sampleBankingServlet�?/p>

清单 1. 配置 Spring MVC DispatcherServlet

   sampleBankingServlet

      org.springframework.we.servlet.DispatcherServlet

   1

　　DispatcherServlet 从一�?XML 文�g装入 Spring 应用�E�序上下文，XML 文�g的名�U�是 servlet 的名�U�后面加�?-servlet 。在�q�个�C�Z��中，DispatcherServlet 会从 sampleBankingServlet-servlet.xml 文�g装入应用�E�序上下文�?

　　配置应用�E�序�?URL

　　下一步是配置惌�� sampleBankingServlet 处理�?URL。同��P��q�是要在 web.xml 中注册所有这些信息�?/p>

清单 2. 配置惌��处理�?URL

sampleBankingServlet
*.jsp

　　装入配置文�g

　　下面�Q�装入配�|�文件。�ؓ了做到这点，请�ؓ Servlet 2.3 规范注册 ContextLoaderListener 或�ؓ Servlet 2.2 及以下的容器注册 ContextLoaderServlet。�ؓ了保障后向兼�Ҏ��，��L�� ContextLoaderServlet。在启动 Web 应用�E�序�Ӟ��ContextLoaderServlet 会装�?Spring 配置文�g。清�?3 注册�?ContextLoaderServlet�?/p>

清单 3. 注册 ContextLoaderServlet

context>servlet-name>

org.springframework.web.context.ContextLoaderServlet

1

　　contextConfigLocation 参数定义了要装入�?Spring 配置文�g�Q�如下面�?servlet 上下文所�C��?/p>

contextConfigLocation
/WEB-INF/sampleBanking-services.xml

　　sampleBanking-services.xml 文�g代表�C�Z��银行应用�E�序服务的配�|�和 bean 配置。如果想装入多个配置文�g�Q�可以在标记中用逗号作分隔符�?/p>

　　Spring MVC �C�Z��

　　�C�Z��银行应用�E�序允许用户�Ҏ��惟一�?ID 和口令查看帐户信息。虽�?Spring MVC 提供了其他选项�Q�但是我��采�?JSP 技术作��N��面。这个简单的应用�E�序包含一个视��N��用于用户输入�Q�ID 和口令）�Q�另一��|��C�用��L��帐户信息�?/p>

　　我从 LoginBankController 开始，它扩展了 Spring MVC �?SimpleFormController。SimpleFormContoller 提供了显�C�Z�� HTTP GET ��h��接收到的表单的功能，以及处理�?HTTP POST 接收到的相同表单数据的功能。LoginBankController �?AuthenticationService �?AccountServices 服务�q�行验证�Q��ƈ执行帐户�z�d��?#8220; 配置视图属�?”一节中的清�?5 描述了如何把 AuthenticationService �?AccountServices �q�接�?LoginBankController�?清单 4 昄��?LoginBankController 的代码�?/p>

清单 4. LoginBankController 扩展 SimpleFormController

public class LoginBankController extends SimpleFormController {

   public LoginBankController(){

   }

   protected ModelAndView onSubmit(Object command) throws Exception{

      LoginCommand loginCommand = (LoginCommand) command;
      authenticationService.authenticate(loginCommand);
      AccountDetail accountdetail = accountServices.getAccountSummary(loginCommand.getUserId());
      return new ModelAndView(getSuccessView(),"accountdetail",accountdetail);
   }

   private AuthenticationService authenticationService;

   private AccountServices accountServices;

   public AccountServices getAccountServices() {
      return accountServices;
   }

   public void setAccountServices(AccountServices accountServices) {
      this.accountServices = accountServices;
   }

   public AuthenticationService getAuthenticationService() {
      return authenticationService;
   }

   public void setAuthenticationService(
         AuthenticationService authenticationService) {
      this.authenticationService = authenticationService;
   }
}

　　配置视图属�?/strong>

　　下面�Q�必��L��册在接收�?HTTP GET ��h��时显�C�的��面。在 Spring 配置中用 formView 属性注册这个页面，如清�?5 所�C�。sucessView 属性代表表单数据提交而且 doSubmitAction() �Ҏ��中的逻辑成功执行之后昄��的页面。formView �?sucessView 属性都代表被定义的视图的逻辑名称�Q�逻辑名称映射到实际的视图��面�?/p>
清单 5. 注册 LoginBankController

            class="springexample.controller.LoginBankController">
      true
   loginCommand

      springexample.commands.LoginCommand









         login


         accountdetail




　　commandClass �?commandName 标记军_��在视图��面中活动的 bean。例如，可以通过 login.jsp ��面讉K�� loginCommand bean�Q�这个页面是应用�E�序的登录页面。一旦用��h��交了��d��面�Q�应用程序就可以�?LoginBankController �?onSubmit() �Ҏ��中的命��o对象��索出表单数据�?/p>
　　视图解析�?/strong>

　　Spring MVC �?视图解析�?把每个逻辑名称解析成实际的资源�Q�即包含帐户信息�?JSP 文�g。我用的�?Spring �?InternalResourceViewResolver�Q�如清单 6 所�C��?/p>
清单 6. InternalResourceViewResolver

      class="org.springframework.web.servlet.view.InternalResourceViewResolver">

      org.springframework.web.servlet.view.JstlView

   /jsp/
   .jsp

　　因�ؓ我在 JSP ��面中��用了 JSTL 标记�Q�所以用��L��d��名称解析成资�?/jsp/login.jsp�Q��?viewClass 成�ؓ JstlView�?/p>
　　验证和帐��h��?/strong>

　　��像前面提到的，LoginBankController 内部�q�接�?Spring �?AccountServices �?AuthenticationService。AuthenticationService �c�d��理银行应用程序的验证。AccountServices �c�d��理典型的银行服务�Q�例如查找交易和甉|��。清�?7 昄��了银行应用程序的验证和帐��h��务的配置�?/p>
清单 7. 配置验证和帐��h��?/p>

         class="springexample.services.AccountServices">


         class="springexample.services.AuthenticationService">


　　以上服务�?sampleBanking-services.xml 中注册，然后装入 web.xml 文�g中，��像前面讨论的那栗��控制器和服务配�|�好后，�q�个��单的应用�E�序��完成了。现在我们来看看部��v和测试它时会发生什�?

　　部��v应用�E�序

　　把示例应用程序部�|�在 Tomcat servlet 容器中。Tomcat �?Java Servlet �?Java ServerPagest 技术的官方参考实��C��使用�?servlet 容器。如果以前没�q�么做过�Q�请下蝲 jakarta-tomcat-5.0.28.exe �q�运行它�?Tomcat 安装到自己喜�Ƣ的��M��位置�Q�例�?c:\tomcat5.0�?/p>
　　接下来，下蝲�C�Z��代码 �q��攑ֈ�驱动器（例如 c:\ �Q�上。创��Z�� Spring ��目的文件夹之后�Q�打开它�ƈ�?spring-banking 子文件夹拯��?c:\tomvat5.0\webapps。spring-banking 文�g�Ҏ��一�?Web 档案�Q�里面包�?Spring MVC �C�Z��应用�E�序。lib 文�g夹包含应用程序需要的 Spring 框架、与Spring 相关�?MVC 库以�?JSTL 标记库和 jar 文�g�?/p>
　　要启�?Tomcat 服务器，请��用以下命令：

　　cd bin C:\Tomcat 5.0\bin> catalina.bat start

　　Tomcat 应当启动�q��|?Spring MVC �C�Z��应用�E�序�?/p>
　　��试应用�E�序

　　要测试应用程序，��h��开 Web ��览器，指向 http://localhost:tomcatport/springbanking �q�用 Tomcat 服务器实际运行的端口替换 tomcatport。应当看到图 1 所�C�的��d��屏幕。输入用�?ID “admin”和口�?#8220;password”�Q��ƈ按下��d��按钮。其他用�?ID 或口令会造成来自验证服务的错误�?/p>

�?1. Spring MVC �C�Z��d��屏幕

　　��d��成功之后�Q�会看到�?2 所�C�的帐户�l�节��面�?/p>

�?2. Spring MVC �C�Z��帐户�l�节��面
Spring MVC框架的高�U�配�|?br>http://dev2dev.bea.com.cn/techdoc/2006068810.html

topquan 2006-08-09 22:26 发表评论

一个Spring�E�序

topquan — Fri, 04 Aug 2006 16:56:00 GMT

Spring通过XML文�g�Q�完成bean配置和bean间依赖关�pȝ��注入�?br>
1.需要用到的包：
spring-core.jar
spring-beans.jar
spring-context.jar
commons-logging.jar

2.Bean文�g
HelloBean.java

package cn.blogjava.hello;

import java.util.Date;

public class HelloBean {

    private String helloWord;
    private String name;
    private Date date;

    public HelloBean() {

    }

    public HelloBean(String helloWord, String name) {
        this.helloWord = helloWord;
        this.name = name;
    }

    public String getHelloWord() {
        return helloWord;
    }

    public void setHelloWord(String helloword) {
        this.helloWord = helloword;
    }

    public String getName() {
        return name;
    }

    public void setName(String name) {
        this.name = name;
    }

    public Date getDate() {
        return date;
    }

    public void setDate(Date date) {
        this.date = date;
    }
}

配置文�g
beans-config.xml

xml version="1.0" encoding="UTF-8"?>
DOCTYPE beans PUBLIC "-//SPRING/DTD BEAN/EN"
    "http://www.springframework.org/dtd/spring-beans.dtd">
<beans>
    <bean id="dateBean" class="java.util.Date"/>
    <bean id="helloBean" class="cn.blogjava.hello.HelloBean" >
        <property name="helloWord">
            <value>Hello!value>
        property>
        <property name="name">
            <value>YYY!value>
        property>
        <property name="date">
            <ref bean="dateBean" />
        property>
    bean>
beans>

3.��试�E�序
SpringDemo.java

package cn.blogjava.hello;

import org.springframework.context.ApplicationContext;
import org.springframework.context.support.FileSystemXmlApplicationContext;

public class SpringDemo {
    public static void main(String[] args) {
        ApplicationContext context =
            new FileSystemXmlApplicationContext("beans-config.xml");
        HelloBean helloBean = (HelloBean)context.getBean("helloBean");
        System.out.print("Name: ");
        System.out.println(helloBean.getName());
        System.out.print("Word: ");
        System.out.println(helloBean.getHelloWord());
        System.out.println(helloBean.getDate());
    }
}

topquan 2006-08-05 00:56 发表评论

Spring:Bean基本��理

topquan — Fri, 04 Aug 2006 16:55:00 GMT
     摘要: 一.从XML文�g中获取Bean的方�?.采用BeanFactory方式         Resource rs = new FileSystemResource("beans-config.xml");      &n...  阅读全文

topquan 2006-08-05 00:55 发表评论

在myeclipse下整合spring和hibernate

topquan — Fri, 04 Aug 2006 16:28:00 GMT

引用 http://www.aygfsteel.com/dyerac/archive/2006/08/04/61805.html

topquan 2006-08-05 00:28 发表评论

Struts+Spring+Hibernate�l�合使用

topquan — Mon, 08 May 2006 14:46:00 GMT
     摘要: 本文是开发基�?spring �?web 应用的入门文章，前端采用 Struts MVC 框架�Q�中间层采用 spring �Q�后台采�?Hibernate�?　　　　本文包含以下内容�Q?　　　　 · 配置 Hibernate 和事�?　　　　 · 装蝲 Spring �?applicationContext.xml 文�g 　　　　 · 建立业务层和 DAO 之间...  阅读全文

topquan 2006-05-08 22:46 发表评论

天堂中文在线8,伊人久久av,日韩亚洲视频在线观看

Developing a Spring Framework MVC application �Q�三�Q?

Products

Hello - Spring Application

Products

Example - Spring Application

Hello - Spring Application

eclipse下struts+spring+hibernate快速入门（二）

�q�入 Spring MVC

一个Spring�E�序

Spring:Bean基本���理

在myeclipse下整合spring和hibernate

Struts+Spring+Hibernate�l�合使用

Spring:Bean基本��理