When you're running the server (i.e. tomcat) from within Eclipse, make sure to start it in debug mode. If you are running it in a distinct process (outside of eclipse), make sure to enable the debug port on it, switch to the debug view in eclipse and start a debugging session on a "Remote Java Application". But otherwise, this is an Eclipse/Java/Tomcat thing and not GWT related. Edoardo Ceccarelli wrote: > Thanks George, > > this is exactly what I was expecting, but I have tried with both Sun > jdk 1.5 and 1.6 and I can't even see a String modification if I don't > make a restart. > I tried the simple provided RPC sample, newest gwt plugin and gwt 1.7 > all running on eclipse 3.5 > > > > On Aug 12, 1:54 pm, George Georgovassilis <[email protected]> > wrote: > >> Hello Edoardo >> >> Not everything, only server-side code. This means servlets, EJBs, >> Spring Beans and DTOs for RPC. When you are running in debugging mode >> then you can replace server code without a restart. Depending on the >> capabilities of your JVM this can be as little as changing method code >> up to replacing entire method signatures and classes. >> >> On Aug 11, 6:36 pm, Eddy <[email protected]> wrote: >> >> >>> Using GWT plugin + GWT 1.7 >>> why there is not hot deployment on server side? every time you change >>> a class you have to restart everything?? >>> >>> any help appreciated >>> Edoardo >>> > > >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
