5 Replies Latest reply on May 17, 2010 8:15 PM by chris.simons

    Seam 2.2 and JRebel - any comments?

      I saw in the 15 gotchas of Seam post that JRebel now supports Seam 2.2 for zero-turn-around.  Has anyone tried it out with Seam and can post their experiences?


      Thanks.

        • 1. Re: Seam 2.2 and JRebel - any comments?
          yahawari

          works like a charm .. can't live without it ! :)

          • 2. Re: Seam 2.2 and JRebel - any comments?

            Thanks for the reply; I just installed it (a breeze) and found that it sure does work (even in WebLogic 10!).  Question, though, can JRebel pick up changes to entity beans?  Thus far, it doesn't seem to - at least for me.  Has that been your experience as well?


            Thanks.

            • 3. Re: Seam 2.2 and JRebel - any comments?
              asookazian

              https://community.jboss.org/wiki/JRebel3withSeam2xtutorial



              JPA — Plugin for OpenJPA that supports changes to entities and configuration. We’re considering this beta for this release and have it disabled by default. Other JPA implementation are on the way.


              Hibernate — Supports changes to entities, annotations and configuration. This rocks, but we’re taking it easy and considering it beta. It’s disabled by default.

              http://www.zeroturnaround.com/news/jrebel-3-0/

              • 4. Re: Seam 2.2 and JRebel - any comments?
                asookazian

                Chris Simons wrote on May 17, 2010 16:34:


                I saw in the 15 gotchas of Seam post that JRebel now supports Seam 2.2 for zero-turn-around.


                This is not quite accurate.  The new feature that's very exciting is the hot redeployment capability of session beans.  JavaBean hot redeployment (regular classes) has been supported for a while by JRebel and it has also been supported by the Seam special classloader as well...

                • 5. Re: Seam 2.2 and JRebel - any comments?

                  Arbi,


                  Thanks, I read the tutorial and your post cleared a few things up; I guess my only question at this point is whether the Hibernate plugin would support Hibernate/JPA (basically Seam default persistence engine)?


                  Also, in the tutorial, it looks like rebel.xml is configured to check exploded-archives/jarname.jar (which I take as the local, staging area for your exploded-archive before it gets shipped to the application server).  I would think it should be setup to look at the actual deployment directory of your favorite application server...what am I missing?


                  Thanks!