<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Thinking inside a bigger box - Latest Comments in In-process Web Integration Tests with Jetty and JWebUnit</title><link>http://thinkinginsideabiggerbox.disqus.com/</link><description></description><language>en</language><lastBuildDate>Sat, 13 Jun 2009 12:41:30 -0000</lastBuildDate><item><title>Re: In-process Web Integration Tests with Jetty and JWebUnit</title><link>http://www.brodwall.com/johannes/blog/2006/12/10/in-process-web-integration-tests-with-jetty-and-jwebunit/#comment-10841282</link><description>I am playing around with this code to get it to work. &lt;br&gt;&lt;br&gt;The link to &lt;a href="http://java.net" rel="nofollow"&gt;java.net&lt;/a&gt; was helpfull. I will post any errors I get. &lt;br&gt;&lt;br&gt;I am a noob at this :). So please bare with me.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Web Designer</dc:creator><pubDate>Sat, 13 Jun 2009 12:41:30 -0000</pubDate></item><item><title>Re: In-process Web Integration Tests with Jetty and JWebUnit</title><link>http://www.brodwall.com/johannes/blog/2006/12/10/in-process-web-integration-tests-with-jetty-and-jwebunit/#comment-6805848</link><description>Thanks for your comment. XSD validation would indeed find some of the defects (like invalid syntax in JSPs), but leave others behind (like the wrong spelling of a bean property name).&lt;br&gt;&lt;br&gt;But more importantly: Discovering bugs is just one reasons to write tests. There are others, and more important ones.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jhannes</dc:creator><pubDate>Mon, 02 Mar 2009 18:33:47 -0000</pubDate></item><item><title>Re: In-process Web Integration Tests with Jetty and JWebUnit</title><link>http://www.brodwall.com/johannes/blog/2006/12/10/in-process-web-integration-tests-with-jetty-and-jwebunit/#comment-6781477</link><description>i guess you are using an IDE  which doesn't provide proper XSD validation</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Web Development</dc:creator><pubDate>Mon, 02 Mar 2009 07:55:19 -0000</pubDate></item><item><title>Re: In-process Web Integration Tests with Jetty and JWebUnit</title><link>http://www.brodwall.com/johannes/blog/2006/12/10/in-process-web-integration-tests-with-jetty-and-jwebunit/#comment-1797232</link><description>One thing worth mentioning (at least for IntelliJ users) is that if you implement tests like Johannes describes in the blog and put them into a sub-module in a multi-module Maven2 project, you will have to explicitly specify the working directory for that module when running the integration test(s). If not you will get FileNotFoundExceptions followed by HTTP 503s for whatever resource you try to hit afterwards.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kristoffer</dc:creator><pubDate>Wed, 03 Jan 2007 10:04:51 -0000</pubDate></item><item><title>Re: In-process Web Integration Tests with Jetty and JWebUnit</title><link>http://www.brodwall.com/johannes/blog/2006/12/10/in-process-web-integration-tests-with-jetty-and-jwebunit/#comment-1797233</link><description>I can't get the example up and running from within my favourite IDE(A) after generating the project files with mvn idea:idea because web.xml is not conformant to the Servlet 2.4 specification.&lt;br&gt;&lt;br&gt;Ok, so I know this is a bit childish :) but I guess you've been using some other IDE of which doesn't provide proper XSD validation(?).&lt;br&gt;&lt;br&gt;Anyhow, the following fragment (slightly revised) is valid:&lt;br&gt;&lt;br&gt;&amp;lt;servlet-mapping&amp;gt;&lt;br&gt;  &amp;lt;servlet-name&amp;gt;my&amp;lt;/servlet-name&amp;gt;&lt;br&gt;  &amp;lt;url-pattern&amp;gt;/my/*&amp;lt;/url-pattern&amp;gt;&lt;br&gt;&amp;lt;/servlet-mapping&amp;gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kristoffer</dc:creator><pubDate>Tue, 02 Jan 2007 10:09:03 -0000</pubDate></item></channel></rss>