5 Replies Latest reply on Jan 23, 2008 12:23 PM by Pete Muir

    EJB hot incremental deployment

    Arbi Sookazian Master

      what is the status regarding adding this functionality to Seam? It is not currently available in Seam 2.0.0.GA and would be VERY useful to have (the xhtml hot deploy is great!). Is there a JIRA issue for this?

      Is it going to be targeted for release and coincide with EJB 3.1 release which apparently is going to remove local interface for session beans?

      Any possibility to add hot incremental deployment for JPA entities as well?

      If JBoss Seam dev team could get full incremental hot deployment released in a new version of Seam that supports facelets, java beans, session beans, JPA entities without affecting a current conversation that would be fantastic.

      Is that possible?

      Also, according to the Seam in Action book, when you hot incremental deploy a POJO with Seam, "the best part is that the application experiences minimal disruption. Your HTTP session
      remains intact and therefore you should be able to continue testing the interface without starting over from the
      beginning." -- pg. 61 MEAP eBook

      Does this also mean that the current conversation is not affected as well?

      thx.

        • 1. Re: EJB hot incremental deployment
          Norman Richards Master

          The conversation should still exist, but I don't think instances in the conversation can be updated with the new component definitions. So, if you are updating the classes, you should generally consider the conversation to be dead.

          BTW, Seam in Action is slightly misleading about the HTTP Session going away on redeploy. In JBoss, when you turn on HTTP session replication (even for non-clustered applications) then your session can be maintained between redeployments. When your app is redeployed, the session data is reloaded from the cache and you can keep going with the new code.

          • 2. Re: EJB hot incremental deployment
            Jason Long Master

            Where is this configured?

            • 3. Re: EJB hot incremental deployment
              Arbi Sookazian Master

              perhaps in default\conf\jboss-service.xml??

              <!-- ==================================================================== -->
               <!-- Deployment Scanning -->
               <!-- ==================================================================== -->
              
               <!-- An mbean for hot deployment/undeployment of archives.
               -->
               <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
               name="jboss.deployment:type=DeploymentScanner,flavor=URL">
              
               <!-- Uncomment (and comment/remove version below) to enable usage of the
               DeploymentCache
               <depends optional-attribute-name="Deployer">jboss.deployment:type=DeploymentCache</depends>
               -->
               <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>


              • 4. Re: EJB hot incremental deployment
                Norman Richards Master

                If you are referring to what I wrote, you need to add the clustering service and mark the app as distributable. Here's something I wrote on the topic a few years ago. To the best of my knowledge, nothing has changed.

                http://members.capmac.org/~orb/blog.cgi/tech/java/Redeploy_web_apps_w.html

                • 5. Re: EJB hot incremental deployment
                  Pete Muir Master

                   

                  "asookazian" wrote:
                  what is the status regarding adding this functionality to Seam? It is not currently available in Seam 2.0.0.GA and would be VERY useful to have (the xhtml hot deploy is great!). Is there a JIRA issue for this?


                  I spoke to Andy from EJB3 team about this a few days ago, he was going to try to get it scheduled. Track the issue http://jira.jboss.com/jira/browse/EJBTHREE-1096

                  Is it going to be targeted for release and coincide with EJB 3.1 release which apparently is going to remove local interface for session beans?


                  Unlikely, this is implementation detail, not spec related. Also EJB3.1 is still a while away.

                  Any possibility to add hot incremental deployment for JPA entities as well?


                  Not AFAIK. You would need to ask Emmanuel or Steve on the Hibernate forum (again this is an implementation detail, not specified).

                  If JBoss Seam dev team could get full incremental hot deployment released in a new version of Seam that supports facelets, java beans, session beans, JPA entities without affecting a current conversation that would be fantastic.


                  We've done what we can, the rest has to be done by the respective projects .