5 JRebel features you couldn't do in the JVM

One common comment we hear when talking about JRebel is that class updates should be implemented in the standard JVM (see <a href=&#034;http://www.zeroturnaround.com/jrebel/comparison/&#034;>feature comparison</a> and <a href=&#034;http://www.zeroturnaround.com/blog/reloading_java_classes_401_hotswap_jrebel/&#034;>behind-the-scenes notes</a> to find out more about JRebel and HotSwap). However even if Oracle or IBM would announce tomorrow that they implemented the support for full schema change HotSwap in the next version of the JVM, JRebel would still be a worthwhile investment. Why?<br><br>There are 5 major features that are impossible to support in the JVM:<br><ol><br><li>Adding new classes</li><br><li>Changes to resources</li><br><li>Changes to web resources</li><br><li>Caches</li><br><li>Managed Components (EJBs, Spring beans,...)</li><br></ol><br><br>We solved them like this:<br><a href=&#034;http://www.zeroturnaround.com/blog/5-jrebel-features-you-couldnt-do-in-the-jvm/&#034;><a href=&#034;http://www.zeroturnaround.com/blog/5-jrebel-features-you-couldnt-do-in-the-jvm/&#034; target=&#034;_blank&#034;>http://www.zeroturnaround.com/blog/5-jrebel-features-you-couldnt-do-in-the-jvm/</a></a>").substring(0,300); return _diggURL ; } One common Click Here to read more...