I found a workaround by moving all resources (html and css) to the "webapp" directory. After adjusting the web.xml to locate the application html(<welcome-file>) in the root of the web application it works fine in DevMode and deployed on Tomcat.
The gwt-maven plugin needs to be configured accordingly as well. This means pointing <runTarget> the same way like the <welcome-file> in web.xml AND adding a <module> tag. This way all resource paths are the same in DevMode as deployed on Tomcat and there are no more 404s. However, does anyone know if this setup might conflict with multi module projects? On 16 Mrz., 12:15, andreas <[email protected]> wrote: > Hey everyone, > > we are developing GWT applications using maven, gwt-maven-plugin, > Eclipse 3.5 EE and m2eclipse. We are currently having some problems > setting up a proper run configuration (based on mvn gwt:run goal) that > seem to come from wrong paths to resources. > > Apparently the <runTarget> tag is used to specify the resource to > launch in DevMode. As the documentation says, one can insert the full > module path there appended by the resource ("/Application.html") IF > that resource is located in the modules "public" folder. The plugin > then replaces the module path by the value of the rename-to directive. > > Now GWT compiler creates a folder named like the rename-to directve > value and puts all generated resources in there, namely the generated > js-files and the gwt stuff. > BUT gwt-maven also puts all other resources in there that is your > Application.html which includes the <script> tag and other files like > Application.css for example. > > Now in order to make the application work in Tomcat (our deployment > target) one needs to adjust all resource references starting from the > <welcome-file> in web.xml to all other includes in the > Application.html as ther are the <script> tag and css-includes to > match the location inside the folder named after the rename-to > directive. > > But with this configuration the application can not be run in DevMode > since DevMode prepends the rename-to directive to all GET request > which leads to 404 when requesting the nocache.js (and css and so on, > but missing nocache prevents everything else from happening; only > white empty html). It requests them from "rename-to/rename-to/rename- > to.nocache.js", where rename-to is what you entered in your modules > rename-to directive. The correct path would be "rename-to/rename- > to.nocache.js" > > Now where is the problem? How can I configure the runTarget or the > paths GWT creates to be the same in DevMode as deployed on Tomcat? > > Thanks in advance. > > Andreas > > P.S.: I remember pure GEP-Projects placing the application html in the > root directory of the web application, but gwt-maven does not, maybe > that is one reason it conflicts. In our case it even is a pure GEP > project we converted to a gwt-maven one. gwt-maven also uses > index.html and simply redirects to the application html. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
