19. August, 2007
Since my presentation at the Jazoon is only available as a PDF (and it looks horrible, too), I’ve uploaded the source OpenOffice presentation to my own website. It includes all the additional comments which are missing in the PDF. You can find it here.
For all those who couldn’t attend my talk: This document summarizes a few weaknesses of Java which are solved in Python and Groovy and why I think that Java is now at it’s peak. From now on, it’s going down. Not overnight, of course, and there is no need to rush into any kind of action. But in ten years from now, Java will be where C is today: Something you don’t want to build your career on (that’s Java, the language, not Java, the VM).
19. August, 2007
If you’re stuck with some JSPs and need to test them with MockRunner, you’ll eventually run in the problem to test jsp:include. MockRunner doesn’t come with built-in support for this, but this itch can be scratched with a few lines of code:
* Allow to use jsp:include in tests.
public class NestedMockRequestDispatcher extends MockRequestDispatcher
public ServletTestModule servletTestModule;
public HttpServlet servlet;
public NestedMockRequestDispatcher (
this.servletTestModule = servletTestModule;
servlet = servletTestModule.createServlet(servletClass);
public void include (ServletRequest request, ServletResponse response)
throws ServletException, IOException
In your test case, add this method:
public void prepareInclude(Class servletClass, String path)
NestedMockRequestDispatcher rd = new NestedMockRequestDispatcher (createServletTestModule(), servletClass);
The path is absolute but without the servlet context. So if the included JSP is named “foo.jsp” and the context is “/webapp”, then path is "/foo.jsp". If that doesn’t work, print the result of getMockRequest().getRequestDispatcherMap() after the test and you’ll see the paths which are expected.
All that’s left is to call this method in setUp() for all JSPs that you need to test. If you forget one, the jsp:include just won’t do anything (i.e. you won’t get an error). To make sure you don’t miss any includes (especially ones which you lazy co-workers added after you wrote the test), I suggest that you check the map after the test run for entries which aren’t instances of NestedMockRequestDispatcher.