part of ongoing struggle with seam and getting a working build
when i deploy to as4.2.3 i get errors about two seam phase listeners which i cant fix and may be related to jsf1.2.10 build you i cant find
If i deploy an a new project to 5.0.0.CR2 i get different errors about the deploy. However in desperation i tried to browse the site and it sort of worked. What does this all mean.
I just want a clean install and publish cycle without errors. I'm still somewhat of a numpty user but this doing my head in.
Whats a viable workable config with basic errors when creating a new out of the box app that i can start on?
i get this error on 5.0.0.cr2
22:32:58,209 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.0.CR2/server/default/deploy/newServerProj-ear.ear/ at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:709) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:661) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:291) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
but if i try and browse the site it seems on install and ai get there
see related different problems with deploying to 4.2.3 on
this getting very silly and i just want a clean start