Why is Jetty looking for a JSP instead of a GSP?

I'm testing out my Grails app in Jetty (v.7.0.2). I've created the WAR (grails prod war), and added it to the webapps directory for Jetty. I've removed the "root" folder that was in there. After bringing up my browser, I'm cli开发者_Python百科cking on various links to make sure I can see all of the appropriate pages. However, when I get to the link that starts a webflow, I get an error:

Problem accessing /testapp/WEB-INF/grails-app/views//foo/start/beginHere.jsp. Reason: Not found.

I've got a controller, called FooController, with a webflow named startFlow. The first action that is run is beginHere. I've tested this by running Grails via the command line, so I've seen this work.

Could the double slash be causing a problem? If so, how do I fix that? Why is it looking for a JSP file instead of a GSP?

Found the answer. It turns out that its an issue with Jetty, and how it handles double slashes in the URL (JETTY-386). The reason it works in Tomcat is because Tomcat handles them the way I was expecting them.

Now its just a matter of setting the configuration appropriately...