Beim Testen mit HttpUnit und Spring m\u00fcssen die Servlets und Filter, die \u00fcber Spring konfiguriert werden mit ihrem Context versorgt werden. Nimmt man hierzu den “normalen” Context-Listener von Spring, hat das den Nachteil, dass bei jedem Start des HttpUnit-ServletContainers der Context neugeladen wird, was unter Umst\u00e4nden viel Zeit in Anspruch nimmt.\n<\/p>\n
Das Zwischenspeichern des Context ist erforderlich und \u00e4hnlich wie Spring selbst Basisklassen mit dieser Eigenschaft anbietet, kann auch ein ContextListener geschrieben werden, der den Context speichert und f\u00fcr viele Testruns zu Verf\u00fcgung stellt.<\/p>\n
<\/p>\n
Ein solcher Listener sieht z.B. so aus:<\/p>\n
\n\r\npackage <\/span>com.rinke.solutions.spring.test;\r\n\r\n<\/span>import <\/span>javax.servlet.ServletContext;\r\n<\/span>import <\/span>javax.servlet.ServletContextEvent;\r\n<\/span>import <\/span>javax.servlet.ServletContextListener;\r\n\r\n<\/span>import <\/span>org.springframework.beans.BeansException;\r\n<\/span>import <\/span>org.springframework.context.support.ClassPathXmlApplicationContext;\r\n<\/span>import <\/span>org.springframework.web.context.WebApplicationContext;\r\n\r\n<\/span>\/**\r\n * class that creates and caches an instance of a WebApplicationContext that can act as listener\r\n * in a httpunit test environment. so the context is reused by all tests which is much faster than\r\n * reinstanciate it again and again.\r\n * <\/span>@author <\/span>Stefan Rinke\r\n *\/\r\n<\/span>public class <\/span>CachingApplicationContextServletContextListener <\/span>implements <\/span>ServletContextListener <\/span>{\r\n\r\n <\/span>\/**\r\n * the instance shared by all tests.\r\n *\/\r\n <\/span>private static <\/span>WebApplicationContext ctx;\r\n\r\n <\/span>\/**\r\n * An implemetation of WebApplicationContext that allows the expiclit setting of the servlet\r\n * context (maybe a mocked context).\r\n * <\/span>@author <\/span>ster\r\n *\/\r\n <\/span>public static class <\/span>MyWebApplicationContext <\/span>extends <\/span>ClassPathXmlApplicationContext <\/span>implements <\/span>WebApplicationContext <\/span>{\r\n\r\n <\/span>\/**\r\n * creates the context an loads the context definition from a classpath location.\r\n * <\/span>@param <\/span>loc the class path relative location of the context definition.\r\n * <\/span>@throws <\/span>BeansException if initialization fails\r\n *\/\r\n <\/span>public <\/span>MyWebApplicationContext<\/span>(<\/span>String loc<\/span>) <\/span>throws <\/span>BeansException <\/span>{\r\n <\/span>super<\/span>(<\/span>loc<\/span>)<\/span>;\r\n <\/span>}\r\n\r\n <\/span>\/**\r\n * stores the servlet context instance as a ThreadLocal, so that different thread can share\r\n * the WebApplicationContext and use different servlet contexts.\r\n *\/\r\n <\/span>private <\/span>ThreadLocal servletContext = <\/span>new <\/span>ThreadLocal<\/span>()<\/span>;\r\n\r\n <\/span>\/**\r\n * return my servlet context for this thread.\r\n * <\/span>@see <\/span>org.springframework.web.context.WebApplicationContext#getServletContext()\r\n *\/\r\n <\/span>public <\/span>ServletContext getServletContext<\/span>() {\r\n <\/span>return <\/span>(<\/span>ServletContext<\/span>) <\/span>servletContext.get<\/span>()<\/span>;\r\n <\/span>}\r\n\r\n <\/span>\/**\r\n * set the servlet context, which is presented to all 'clients' of the WebApplicationContext.\r\n * <\/span>@param <\/span>servletContext the context to use\r\n *\/\r\n <\/span>@SuppressWarnings<\/span>(<\/span>"unchecked"<\/span>)\r\n <\/span>public <\/span>void <\/span>setServletContext<\/span>(<\/span>ServletContext servletContext<\/span>) {\r\n <\/span>this<\/span>.servletContext.set<\/span>( <\/span>servletContext <\/span>)<\/span>;\r\n <\/span>}\r\n\r\n }\r\n\r\n <\/span>\/**\r\n * static factory for the singleton WebApplicationContext\r\n * <\/span>@return <\/span>the new or cached context\r\n *\/\r\n <\/span>public synchronized static <\/span>WebApplicationContext getApplicationContext<\/span>() {\r\n <\/span>if<\/span>( <\/span>ctx == <\/span>null <\/span>) {\r\n <\/span>ctx = <\/span>new <\/span>MyWebApplicationContext<\/span>(<\/span>"\/testContext.xml"<\/span>)<\/span>;\r\n <\/span>}\r\n <\/span>return <\/span>ctx;\r\n <\/span>}\r\n\r\n <\/span>\/**\r\n * listener callback. populates the cached context with the new initializing servlet context.\r\n * <\/span>@see <\/span>javax.servlet.ServletContextListener#contextInitialized(javax.servlet.ServletContextEvent)\r\n *\/\r\n <\/span>public <\/span>void <\/span>contextInitialized<\/span>(<\/span>ServletContextEvent evt<\/span>) {\r\n <\/span>MyWebApplicationContext ctx = <\/span>(<\/span>MyWebApplicationContext<\/span>) <\/span>CachingApplicationContextServletContextListener.getApplicationContext<\/span>()<\/span>;\r\n ctx.setServletContext<\/span>(<\/span>evt.getServletContext<\/span>())<\/span>;\r\n evt.getServletContext<\/span>()<\/span>.setAttribute<\/span>( <\/span>WebApplicationContext.ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE,\r\n ctx <\/span>)<\/span>;\r\n <\/span>}\r\n\r\n <\/span>\/**\r\n * does nothing\r\n * <\/span>@see <\/span>javax.servlet.ServletContextListener#contextDestroyed(javax.servlet.ServletContextEvent)\r\n *\/\r\n <\/span>public <\/span>void <\/span>contextDestroyed<\/span>(<\/span>ServletContextEvent arg0<\/span>) {\r\n }\r\n\r\n}<\/span><\/tt>\r\n<\/pre>\n<\/blockquote>\n\nEin weiterer Vorteil des eigenen Listeners: man kann die Context-Definition laden wie man will und ist nicht abh\u00e4ngig, von dem simulierten Verhalten des Servlet-Classloaders von HttpUnit.<\/p>\n","protected":false},"excerpt":{"rendered":"
Beim Testen mit HttpUnit und Spring m\u00fcssen die Servlets und Filter, die \u00fcber Spring konfiguriert werden mit ihrem Context versorgt werden. Nimmt man hierzu den “normalen” Context-Listener von Spring, hat das den Nachteil, dass bei jedem Start des HttpUnit-ServletContainers der … Weiterlesen