[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Jiri Peterka updated JBIDE-6389: -------------------------------- Summary: Seam WAR Deployment error with SOA-P 5.0.1 GA and JBDS 3.0.1 (was: Deployment error with SOA-P 5.0.1 GA and JBDS 3.0.1) Description: 1. Start SOA-P 5.0.1 server 2. Create Seam WAR project for SOP-P runtime and it's seam (called for example seam-war-soa) 3. You should see this exception WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "persistence.unit:unitName=#seam-war-soa" is missing the following dependencies: Dependency "jboss.jca:name=seam-war-soaDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=seam-war-soaDatasource,service=DataSourceBinding' **") DEPLOYMENTS IN ERROR: Deployment "jboss.jca:name=seam-war-soaDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=seam-war-soaDatasource,service=DataSourceBinding' ** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:994) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:940) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:378) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:256) 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) Note: Tested with new installation and new workspace was: 1. Start SOA-P 5.0.1 server 2. Create WAR project for SOP-P runtime and it's seam (called for example seam-war-soa) 3. You should see this exception WARN [HDScanner] Failed to process changes org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES: Deployment "persistence.unit:unitName=#seam-war-soa" is missing the following dependencies: Dependency "jboss.jca:name=seam-war-soaDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=seam-war-soaDatasource,service=DataSourceBinding' **") DEPLOYMENTS IN ERROR: Deployment "jboss.jca:name=seam-war-soaDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=seam-war-soaDatasource,service=DataSourceBinding' ** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:994) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:940) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:378) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:256) 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) Note: Tested with new installation and new workspace -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Jiri Peterka commented on JBIDE-6389: ------------------------------------- Seems to be a problem of bundled EAP 5.0.1 and SOA-P 5.0.1. JBT operates all right, deployments and hot deployments are performed alright, but runtime server doesn't react at all until restarted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Dominik Pospisil updated JBIDE-6389: ------------------------------------ Summary: Seam WAR Deployment error with EAP 5.0.1 / SOA-P 5.0.1 GA and JBDS 3.0.1 (was: Seam WAR Deployment error with SOA-P 5.0.1 GA and JBDS 3.0.1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Alexey Kazakov reassigned JBIDE-6389: ------------------------------------- Assignee: Max Rydahl Andersen (was: Alexey Kazakov) I guess the problem is in order of deployment. When you create a Seam project we deploy WAR/EAR first and then -ds.xml. It's ok when Server is not running. But if it's started then WAR is picked up before -ds.xml was deployed. Max, is it problem is important enough to try to deploy -ds.xml before building WAR/EAR'? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on JBIDE-6389: -------------------------------------------- if possibly we should definitely try and deploy -ds.xml before the rest. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen updated JBIDE-6389: --------------------------------------- Fix Version/s: 3.2.0.M2 (was: 3.1.2) (was: 3.2.0.M1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Alexey Kazakov commented on JBIDE-6389: --------------------------------------- See org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(final IProgressMonitor monitor) which calls org.jboss.tools.seam.internal.core.project.facet.DataSourceXmlDeployer Now we still deploy *-ds.xml after projects. I tried to move this action and deploy *-ds.xml before we deploy projects but as I sad it didn't work with AS 5.0.1 (I didn't know that EAP 5.0.1 has JBoss AS 5.1.0). So I didn't committed the changed code. Need to check it with JBoss 5.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Rob Stryker updated JBIDE-6389: ------------------------------- Fix Version/s: 3.2.0.Beta2 (was: 3.2.0.Beta1) Since this has a workaround (republish / restart server) pushing out to beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6389?page=com.atlassian.jira.plugin.s... ] Alexey Kazakov resolved JBIDE-6389. ----------------------------------- Resolution: Done Sorry Rob, I verified it for AS6M5 and it works now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira