This is how I work too. It uses the "hot swap" feature of the JVM. It works if you only change method bodies, but if you make changes to the class structure (fields, method signatures, etc.) you have to restart the VM. Apparently jRebel can reload even these kinds of changes.
I'm happy with hot swap, but then again my app only takes ~14 seconds to restart. jk On Sun, May 30, 2010 at 04:22:29PM -0500, Jeremy Thomerson wrote: > On Sun, May 30, 2010 at 12:05 PM, Alex Objelean > <alex.objel...@gmail.com>wrote: > > > > > jRebel allows you to change the java code without restarting the server. > > > > I've not used jRebel, but I commonly run my applications in debug mode in > Eclipse and do not have to restart the server - even with code changes. The > exception is changing a method signature of classes that are already loaded > - but adding methods, classes, or changing 90% of code does not require a > restart. So, what does jRebel add? Does it eliminate restarts even in > these cases where the normal debug mode requires one? > > -- > Jeremy Thomerson > http://www.wickettraining.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
