Community
Participate
Working Groups
Currently the RWT launch configuration allows to launch from either a given entry point or by providing a web.xml. In the latter case, the servlet path can be specified so that the browser points to the right URL when opened. To ease integration with frameworks (e.g. Spring) that put further artefacts in the web application folder, I suggest to proivde a third way to launch web applications. It should allow to specify a path to a folder within the project that matches the structure of a web application. In case the browser should be opened, the servlet path would also have to be specified. Ideally, it should be validated that the given folder contains the mandatory artefacts for a web application (i.e. has a WEB-INF folder that contains a web.xml).
Extended the launch config with a third option: Run from web-application folder. When choosing this option, a folder from the workspace must be specified that serves as the root of the web application. This folder must at least contain a WEB-INF folder with a valid deployment descriptor (web.xml). Currently the embedded Jetty that serves as the servlet engine is started with a parameter that points directly to the given web application folder. As a consequence, resources to be delivered by the servlet engine are written to this folder. This is less-than-optional as this folder is usually managed by a source code management system and temporary resource files aren't meant to be stored there. To avoid this, we might consider to copy the web application folder to a temporary location before launching the servlet engine. Changes are in CVS HEAD.
The run-jetty-run project [1] already provides the described feature. I will therefore revoke the changes. [1] http://code.google.com/p/run-jetty-run/
