Jetty

I created a basic hack for this issue to get access to /WEB-INF/lib and /WEB-INF/classes for both MyFaces 2 and Mojarra 2. My solution patches the JettyWebAppContext in the plugin itself to access resources in those directories. There might be a fancier solution, but it works for my applications. The patch is for jetty-7.

Additionally, I provided a JSF-based web application for testing. It is Maven-based, so "mvn jetty:run" (for MyFaces) and "mvn jetty:run -P mojarra" (for Mojarra) should start the app with jetty-maven-plugin 7.1.1-SNAPSHOT.

Any update on this? Is there something wrong with the proposed patch?
This affects everyone who attempts to use popular technologies, such as JSF2 (via Mojarra), using Jetty through the jetty:run goal of the jetty-maven-plugin.

Hi Michael (or Ian)

I've used the patch, but I've made a few changes to it. I'd like to use the test webapp you've provided, but can you just verify for me how I confirm that webapp is working? If I hit http://localhost:8080/mygourmet11 is that a good enough test?

thanks,
Jan

Hi Jan,

the start page should also work without the patch. If you click "edit customer" and submit the form there should be exceptions if the managed beans can't be resolved (which is the case without the patch).

Michael

Slightly modified patch checked into jetty-codehaus trunk that works with the provided test app. A bit more testing by others would be appreciated.

I did some further testing with an advanced version of the test webapp including Spring 3, MyFaces Orchestra and Hibernate and it works like a charm.

Thanks for that Michael. I'll close the issue now.

Jan

Seems that field testing is showing that the patch works as expected.

Please make sure this is merged to Jetty 8. This is causing a major pain for us trying to use Freemarker. I believe that every app that uses Freemarker with the maven jetty plugin will run into this issue.