Changes of Unit Testing with StrutsTestCase and EasyMock from #8 to #9

Inserted lines at line 15

1.1 The Abstract Factory Design Pattern
In order to enable substitution of the service class I have applied the {link:Abstract Factory pattern|url=http://en.wikipedia.org/wiki/Abstract_factory_pattern}. The TestObjectFactory class is a concrete implementation of an abstract ObjectFactory class. At the time of unit testing I can easily insert a stub or mock service, while at runtime the SpringObjectFactory concrete implementation  will provide the actual services from the Spring application context of the web application.
{code}
...
public abstract class ObjectFactory
{
    private static ObjectFactory instance;
    public abstract Object getBean(String beanName, ServletContext servletContext);
    public static synchronized ObjectFactory getInstance()
    {
        if (instance == null)
        {
            instance = new SpringObjectFactory();
        }
        return instance;
    }
    public static synchronized void setInstance(ObjectFactory instance)
    {
        ObjectFactory.instance = instance;
    }
}
...
public class TestObjectFactory extends ObjectFactory
{
    private static HashMap beans = new HashMap();
    public Object getBean(String beanName, ServletContext servletContext)
    {
        return beans.get(beanName);
    }
    public void addBean(String beanName, Object bean)
    {
        beans.put(beanName, bean);
    }
}
...
public class SpringObjectFactory extends ObjectFactory
{
    public Object getBean(String beanName, ServletContext servletContext)
    {
        WebApplicationContext webContext = WebApplicationContextUtils
                .getWebApplicationContext(servletContext);
        return webContext.getBean(beanName);
    }
}
{code}

Changes of Unit Testing with StrutsTestCase and EasyMock from #8 to #9

Professional

Software Development and Process

Music Musings