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
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,
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
Gwt plugin runs its applications inside a jetty container: in fact one
of the great usefulness of using the Google GWT eclipse plugin is that
you don't need to have another server runtime installed and launched
in eclipse.
With latest versions of the plugin, you can just create a sample
Sorry, I missed that you were using the GWT Plugin. I've not used it so
I can't help you with that one :(
Edoardo Ceccarelli wrote:
Gwt plugin runs its applications inside a jetty container: in fact one
of the great usefulness of using the Google GWT eclipse plugin is that
you don't need to
I tried in a clean workspace and it works!
it must be related to some old setting in my normal workspace.
Regards
Edoardo
On Aug 12, 2:24 pm, Edoardo Ceccarelli ridl...@gmail.com wrote:
Gwt plugin runs its applications inside a jetty container: in fact one
of the great usefulness of using
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
