By Dave Booth
via zeroturnaround.com
Published: Sep 09 2009 / 10:11
For those of you who have been keeping up with recent ZeroTurnaround news, even though there are shows like Big Bang Theory to distract you, you’ll know that JavaRebel has been going through a renaming process. Instead of choosing the name ourselves, we opened up the process to anyone who wanted to contribute ideas. For the story, list of humorous suggested names, and other good suggestions, you know what to do :-)
Comments
MCII replied ago:
JavaRebel to JRebel - I'm overwhelmed.
dcortez replied ago:
I fail to realize why people would pay money for a simple classloader about 150 lines of code that they can write themselves or download to reload classes at runtime, and yet they expect their webserver to be free.
Its really amazing the hoax java rebel has perpetrated.
toomasr replied ago:
@dcortez: I presume you have not checked this out :) I'll try to explain a bit.
Java developers do know that dropping a classloader and recreating a new one is the general solution to reloading their code (this is what containers do when doing redeploys or deploying multiple applications). With this approach you have the drawbacks of recreating state, recreating the session and it takes time (from the survey you can check out how much time it takes).
If you happen to have some dangling references then you're also leaking memory (the case of the OOM with 5 redeploys on some modern containers). You can also get ClassCastExceptions, IllegaAccessExceptions.....
JRebel on the other hand reloads classes instantly (measured in ms). Reads the new bytecode and propagates the changes itself. There is no dropping/recreating classloaders or serialization/deserialization happening in the background.
Voters For This Link (32)
Voters Against This Link (2)