4 Replies Latest reply on Aug 6, 2009 4:52 AM by johndoe123

    Deployment of WAR slow

      Hi!

      I am developing a web application currently.

      Libraries/Tools:

      Richfaces 3.3.1
      JSF 1.2
      Seam 2.1.2
      JBoss 5.0.1
      Eclipse Ganymed

      Problem:
      Whenever I change some jsf/richfaces xhtml files I need to restart the server for the changes to take effect.

      Hot Deployment won't work. When I change a file and save it, I see the status "Republish" in the Servers tab of eclipse. I need to wait about 30 seconds until it says synchronized again but when I reload the page, it's still the old one. The only way to see the changed xhtml files is to restart the server or do a clean (which does not work every time).

      Isn't there a way to speed up development? It's taking me ages to implement and test minor changes that way.

      Please help!

        • 1. Re: Deployment of WAR slow
          jaikiran

           

          "JohnDoe123" wrote:

          ...
          JBoss 5.0.1

          Problem:
          Whenever I change some jsf/richfaces xhtml files I need to restart the server for the changes to take effect.

          Hot Deployment won't work.


          That was a known issue in JBoss AS 5.0.1. It got fixed in the latest 5.1.0 version. Download it and give it a try.


          • 2. Re: Deployment of WAR slow

            Thanks, but I run into problems using JBoss 5.1.0 GA with Eclipse Galileo.

            The app is deployed without errors, but then, after 10 seconds, it undeploys for no apparent reason:

            Log-excerpt:

            2009-08-06 09:47:33,343 WARN [org.jboss.seam.async.QuartzDispatcher] (HDScanner) No seam.quartz.properties file. Using in-memory job store.
            2009-08-06 09:47:33,343 INFO [org.quartz.simpl.SimpleThreadPool] (HDScanner) Job execution threads will use class loader of thread: HDScanner
            2009-08-06 09:47:33,343 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Quartz Scheduler v.1.5.2 created.
            2009-08-06 09:47:33,343 INFO [org.quartz.simpl.RAMJobStore] (HDScanner) RAMJobStore initialized.
            2009-08-06 09:47:33,343 INFO [org.quartz.impl.StdSchedulerFactory] (HDScanner) Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
            2009-08-06 09:47:33,343 INFO [org.quartz.impl.StdSchedulerFactory] (HDScanner) Quartz scheduler version: 1.5.2
            2009-08-06 09:47:33,343 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
            2009-08-06 09:47:33,343 WARN [org.jboss.seam.security.permission.PersistentPermissionResolver] (HDScanner) no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required.
            2009-08-06 09:47:43,859 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/project
            2009-08-06 09:47:43,859 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
            2009-08-06 09:47:43,859 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
            2009-08-06 09:47:43,859 INFO [org.quartz.core.QuartzScheduler] (HDScanner) Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.


            WHY?

            • 3. Re: Deployment of WAR slow
              jaikiran

              Oh boy!

              I must say that Seam deployments in AS-5.0.x and AS-5.1.0 have (known) issues. As you noticed, 5.0 did not identify the changes to .xhtml and did not redeploy. AS-5.1.0 does the exact opposite, it finds that Seam deployments need to be redeployed (for no valid reason) :) Fortunately there's a workaround. Follow this thread (and other linked threads there) http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159500.

              • 4. Re: Deployment of WAR slow

                THANK!

                I got it working. The 1-sec hot deployment is awesome!