2 Replies Latest reply on May 1, 2009 11:15 AM by Max Rydahl Andersen

    annoying error : incomplete deployment exception

    William Woodman Master

      had this problem through many releases and dont understand the problem.


      in jboss tools if I do an undeploy and deploy again of my EAR i get an error like this


      15:30:57,765 INFO [SeamFilter] Initializing filter: org.jboss.seam.web.identityFilter
      15:30:57,875 WARN [HDScanner] Failed to process changes
      org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

      *** DEPLOYMENTS MISSING DEPLOYERS: Name

      vfsfile:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/

      at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
      at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:806)
      at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293)
      at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
      at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at java.lang.Thread.run(Thread.java:619)


      what i have to do is undeploy - then run a clean project - then a redeploy,
      and then access the server with the browser.

      This then triggers an internal refresh somehow and it then goes into action and lists


      15:31:46,635 INFO [Contexts] starting up: org.jboss.seam.security.identity
      15:31:46,635 INFO [Contexts] starting up: org.jboss.seam.security.ruleBasedPermissionResolver
      15:31:50,811 INFO [RuleBase] parsing rules: /security.drl
      15:31:52,343 INFO [Contexts] starting up: org.jboss.seam.web.session
      15:34:21,117 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jboss-seam-pdf.jar/META-INF/seam-pdf.taglib.xml
      15:34:21,127 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jboss-seam-mail.jar/META-INF/seam-mail.taglib.xml
      15:34:21,217 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jsf-facelets.jar/META-INF/jsf-core.taglib.xml
      15:34:21,267 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jsf-facelets.jar/META-INF/jsf-html.taglib.xml
      15:34:21,507 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jsf-facelets.jar/META-INF/jsf-ui.taglib.xml
      15:34:21,558 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jsf-facelets.jar/META-INF/jstl-core.taglib.xml
      15:34:21,568 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jsf-facelets.jar/META-INF/jstl-fn.taglib.xml
      15:34:21,658 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jboss-seam-excel.jar/META-INF/seam-excel.taglib.xml
      15:34:21,668 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/jboss-seam-ui.jar/META-INF/s.taglib.xml
      15:34:21,778 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/richfaces-ui.jar/META-INF/a4j.taglib.xml
      15:34:21,788 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/richfaces-ui.jar/META-INF/ajax4jsf.taglib.xml
      15:34:21,788 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/richfaces-ui.jar/META-INF/jsp.taglib.xml
      15:34:22,028 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/richfaces-ui.jar/META-INF/rich.taglib.xml
      15:34:22,038 INFO [compiler] Added Library from: vfszip:/E:/jboss/jboss-5.0.1.GA/server/default/deploy/temp-ear.ear/temp.war/WEB-INF/lib/richfaces-ui.jar/META-INF/richfaces.taglib.xml


      at which point the browser fins the app okay -

      Why cant jboss tools and jboss as work happliy without these silly gotchas - it slows you down working round it?

      i'm running jboss as5.01, seam 2.1.1ga, and jboss tools v3

      looking forward to hearing a reponse on what may be going on here.

      had it as 4.2.2 and early tools drops - never seems to get fixed