I am pretty sure it is correct. But make sure that you use the latest version of this article: http://www.brodwall.com/johannes/blog/2007/02/0…

The code for this particular bit is here: http://svn.brodwall.com/demo/insanejava/trunk/w…

If you still don't have any success, feel free to post the problem here, or send me an email.

I am pretty sure it is correct. But make sure that you use the latest version of this article: http://www.brodwall.com/johannes/blog/2007/02/04/updated-article-embedded-web-integration-testing-with-jetty/

The code for this particular bit is here: http://svn.brodwall.com/demo/insanejava/trunk/web-demo/src/test/java/no/brodwall/web/integration/JettyTestServer.java

If you still don’t have any success, feel free to post the problem here, or send me an email.

The code which retrieves Springs WebApplicatonContext using the jetty server's servlet context was failing. Specifically, the following code was throwing a ClassCastException:

ApplicationContext appctx = WebApplicationContextUtils
.getRequiredWebApplicationContext(servletContext);

The reason being that the Spring's application context was loaded by Jetty's own classloader, hence cannot be used here.

The work around was to set the parentLoaderPriority to true while creating the Jetty server as described here: http://docs.codehaus.org/display/JETTY/Classloa…

eg:
WebAppContext context = new WebAppContext();
context.setParentLoaderPriority(true);
context.setContextPath(”/”);
context.setWar(”path/to/war/or/exploded/war”);
jettyServer.setHandler(context);

The errors happens didnt happen on a Windows XP box. But while running our CI builds on a Redhat EL4 box, the classcast exception was thrown.

Redhat EL4
JDK 1.5_07-b3
Jetty-6.1.1
Spring-Framework-2.0.2

Hope this might help someone who runs into the same problem.

– suresh –

The code which retrieves Springs WebApplicatonContext using the jetty server’s servlet context was failing. Specifically, the following code was throwing a ClassCastException:

ApplicationContext appctx = WebApplicationContextUtils
.getRequiredWebApplicationContext(servletContext);

The reason being that the Spring’s application context was loaded by Jetty’s own classloader, hence cannot be used here.

The work around was to set the parentLoaderPriority to true while creating the Jetty server as described here: http://docs.codehaus.org/display/JETTY/Classloading

eg:
WebAppContext context = new WebAppContext();
context.setParentLoaderPriority(true);
context.setContextPath(”/”);
context.setWar(”path/to/war/or/exploded/war”);
jettyServer.setHandler(context);

The errors happens didnt happen on a Windows XP box. But while running our CI builds on a Redhat EL4 box, the classcast exception was thrown.

Redhat EL4
JDK 1.5_07-b3
Jetty-6.1.1
Spring-Framework-2.0.2

Hope this might help someone who runs into the same problem.

– suresh –

I was not aware of this issue. Thanks for the heads-up and the good feedback. I will have to work on how to integrate it into the text, but I have updated the source code in SVN.

~Johannes

I was not aware of this issue. Thanks for the heads-up and the good feedback. I will have to work on how to integrate it into the text, but I have updated the source code in SVN.

~Johannes