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

JRebel 3.1 — ORM Goodness

With the support for all Java EE standards this release of JRebel will help you reach a new level of productivity. Whatever change you make to your code, whether it’s a class, resource, configuration or a component, you can immediately see it in your application, with no need to build or redeploy. Although we’re still waiting on usage stats to confirm it, we estimate that JRebel 3.1 will eliminate up to 95% of builds/redeploys that you have to do without it on a common Java EE project.

The first thing you’ll notice after downloading the new 3.1 release, is the support for reloading JPA entities and configuration on all containers. Hibernate and OpenJPA plugins are now enabled by default, but for TopLink/EclipseLink we’re waiting for more user feedback, so go ahead and fire it up. JRebel also fully support reloading native entities and configuration for Hibernate and TopLink.

The second is the support for EJB interface changes and JSP scriptlet changes in GlassFish. Changes to EJB interfaces and scriptlets are now reloaded instantly on all major containers. New features include a spanking new iBatis plugin, beta support for the Geronimo container and a host of others.

Download it while it’s hot!

Responses (6)

  1. Avatar  


    June 2, 2010 @ 6:21 pm

    EBean beats JPA.

    You will be surprised. I'm using daily – and jrebel. Can you bring that into the fold?

  2. Avatar  

    Andrei I.

    June 3, 2010 @ 6:46 am

    I would like support for another ORM – Cayenne: and
    especially support for another component based web framework (besides Tapestry), called Click:

    I know that the users could implement them self such support, but me and many like me are not skilled enough for this, so I believe ZeroTrunaround should try to do it (for them it should be a 'piece of cake'): The more projects are supported, the more will be the visibility of JRebel (besides the linking, the buzz, the posts and the reputation)

  3. Avatar  

    Len Bil

    June 9, 2010 @ 4:47 am

    JRebel 3.1 causes passivation error on Seam

  4. Avatar  

    Toomas Römer

    June 9, 2010 @ 4:50 am

    If you have not done it yet, maybe you could report that to support@zeroturnaround or take it to the forum at ?

  5. Avatar  


    July 5, 2010 @ 4:41 pm

    What version of iBatis is supported? 3 is pretty much the standard for new projects now.

  6. Avatar  


    July 5, 2010 @ 8:41 pm

    What version of iBatis is supported? 3 is pretty much the standard for new projects now.

RSS feed for comments on this post.

Sorry, the comment form is closed at this time.