Comments on: Automatic Java Class Reloading

By: tom blog » ZeroTurnaround.com / JavaRebel

tom blog » ZeroTurnaround.com / JavaRebel — Thu, 18 Oct 2007 08:21:09 +0000

[…] 18, 2007 @ 12:19 am · Filed under Uncategorized Spoke to Seth and he talked about ZeroTurnaround.com > JavaRebel This looks very promising. At my new gig, […]

By: DD

DD — Fri, 12 Oct 2007 14:46:58 +0000

Yet nothing has even come close to the scope at which Javarebel is capable of it, outside specific frameworks.

I mean, sure hotswap has been introduced for a while now… Or other methods.

The catch is, please do compare the amount of limitaitons Javarebel has and the amount of limitations other methods have.
You will find the answers if you do your homework right (and read the original article on theserverside fully).

By: Toomas Römer

Toomas Römer — Fri, 12 Oct 2007 12:47:01 +0000

To Anonymous

You are talking about Java HotSwap. In debug sessions you can modify method bodies. You can’t do anything else (create/delete/change methods, fields, classes). This has nothing to do with application servers. Application servers have to support the JPDA and you get HotSwap basically for free.

JavaRebel does not require to suspend any threads or be in debug mode and you can change almost anything. See JavaRebel features for more details:

http://www.zeroturnaround.com/javarebel/features/

By: Anonymous

Anonymous — Thu, 11 Oct 2007 21:18:17 +0000

This really is not new, application servers have been doing doing this for years now (Tomcat, Websphere, even JRun). As far as a development environment, the Java debugger can alter classes in memory at runtime - in fact runtime AOP uses a similar technique.

Take the IDE Eclipse for example, in a debug session you can alter the code while the application* is running. In certain circumstances, the IDE will detect this and rollback to the previous breakpoint allowing you to reiterate that troublesome loop using the new code.

*Don’t forget a Java web-app server is itself a Java app. You can use change the code in memory there too.

By: Dmitri

Dmitri — Thu, 11 Oct 2007 21:06:29 +0000

Basically, I have seen most of the development on JavaRebel, considering the people next door to me are developing it

We at Webmedia have used JavaRebel extensively in most of our projects, for over half a year now.

I can not recommend it enough, and yes, it does exactly what it is supposed to do.

Changing stuff in Eclipse is like this:
Modify code, save => eclipse automatically builds.
Hit F5 in browser, your view instantly refreshes, no redeployment.

This accounts for about 80% of the cases, and this percentage is increasing.

It works flawlessly on Windows and Linux, also from what I heard, MacOS JVM has no problems with it either