On Monday, December 13, 2010 9:27:44 AM UTC, Thomas Broyer wrote:DevMode does support hot-deploy (you have to "trigger" it though, by clicking on the "reload web server" button –yellow spinning double-arrow in Eclipse's Development Mode view–), but it loads the server classes from the webapp's WEB-INF. Doing a "mvn package" will copy all dependencies to WEB-INF/lib and compile your classes to WEB-INF/classes so DevMode will be able to pick them up; but then if you change the server-side code, you have to make sure the WEB-INF is updated (for classes, you can tell Eclipse to compile to WEB-INF/classes, which should be the default with m2eclipse and m2e-wtp integration; but for dependencies, you have to run "mvn war:exploded" again –there might be another, faster, maven goal for that–). DevMode also loads the "web resources" from the webapp, so you have to ensure that changes to made to src/main/webapp are reflected in the webapp; again, "mvn war:exploded" to the rescue. With WTP and m2e-wtp integration, Eclipse WTP takes care of that "synchronization" for you, but then you don't use DevMode's embedded server.
Since last night I've been playing with Jetty WTP and noticed something strange. As you said you're using Jetty WTP, can you tell me if you've encountered this problem: Tell Eclipse to run your application on Jetty. This results in a deployment to 2 places. The first location is WTP related: <eclipse-workspace-dir>\.metadata\.plugins\org.eclipse.wst.server.core\tmp1 (in my case), and the second location is a temporary directory. Here's an extract from the Jetty console: 2010-12-13 12:25:20.053:INFO::Extract C:/jetty-6.1.26/webapps/MyDynWP.war to C:\Users\Pete\AppData\Local\Temp\Jetty_127_0_0_1_8080_MyDynWP.war__MyDynWP__dez1nk\webapp Then I run Development Mode and tell it about the WTP location. The act of starting DevMode creates the folder that has the GWT bits in it (xxx.nocache.js, etc). The problem is when the browser is pointed at http://localhost:8080/MyApp/MyApp.html?gwt.codesvr=127.0.0.1:9997 Jetty serves content from the temporary directory and therefore the GWT-generated bits aren't there! Have you seen this? Thanks, Pete P.S. Thanks for the above explanation about hot-deploy in DevMode and the steps required. I confess to not understanding 100% yet but getting there! -- 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.
