The latest expert opinions, articles, and guides for the Java professional.

JRebel 4.0 Released – Redeploys Beware

It’s hard to believe that it’s been more than 3 years since the JRebel 1.0 release. It seems like it was only  yesterday that we were putting together the first public beta, then opening the first champagne to celebrate when Nathan Hamblen bought the first license a week later. Thanks to him and all of you, our loyal users, today the JRebel team proudly presents the 4.0 release.

The major features are:

  • Full support for reloading changes to EJBs 3.x. Includes adding new components and adding @EJB references on-the-fly, across Weblogic, WebSphere, JBoss and Glassfish.
  • Support for anonymous class reloading. Previously, adding a new anonymous class would cause the other ones to be renamed (Class$3 -> Class$4) and JRebel would complain that a superclass has changed and fail to reload. Never again.
  • Instrumentation/HotSwap integration. Although JRebel always used a -javaagent to bootstrap, it hasn’t actually used the Instrumentation API before. Now, on Java 5 or later, we make use of this functionality to minimize the runtime performance overhead and to further improve the debugging behaviour. This also lays ground for some future improvements.
  • Full Seam 2.x support. Now you can add new components and wire them in on-the-fly. Enjoy!
  • Better integration across the board. Hibernate Validator and Spring Security are the biggest names, but we have severely expanded our test suite with support for 35 frameworks, not counting the server, standard and miscellaneous integrations.

And of course a score of smaller features and fixes as usual that you can find in changelog.

Well, what are you waiting for? Grab it now!

Responses (2)

  1. Avatar  


    June 2, 2011 @ 12:50 pm

    Does it work well with GWT 2.3 and Spring 3.x modules in Tomcat and JBoss?

  2. Avatar  

    Anton Arhipov

    June 2, 2011 @ 4:36 pm

    Haven’t tried it with GWT 2.3 yet, but there isn’t much to handle besides class reloads – the client side is handled/reloaded by GWT itself.
    Which Spring 3.x modules are you interested in?
    Tomcat/JBoss – yes

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.