[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-users] Maven, Enunciate and debugging...
|
Okay, I switched and installed the latest Eclipse 4.2.1 Juno with all the latest and greatest m2e plugins and connectors. I can build and deploy my enunciate-enabled service and the service endpoints seem to work, but it won't pull up the enunciate-generated documentation at the path "/index.html" nor the JavaMelody monitoring URL at the path "/monitoring".
I have index.html and rest.html listed in <welcome-file-list> as part of my stub web.xml and these settings are merged in the final web.xml but for some reason the app deployed via Eclipse doesn't seem to use the final web.xml.
I'm still assuming an issue with how Eclipse + m2e is handling the web.xml generated by enunciate.
The content of src/main/webapp/WEB-INF/web.xml has only the custom listeners and filters along with the <welcome-file-list>.
In the enunciate.xml is configured to merge the contents of src/main/webapp/WEB-INF/web.xml with the generated settings.
The final web.xml is located in the WAR as well as the target/<warname>/WEB-INF/web.xml and looks correct.
If I deploy the WAR manually, it works fine, including all static resources and service endpoints.
Is there a setting I'm missing in Eclipse or M2E that determines how it handles the web.xml content?