[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6389) Seam WAR Deployment error with EAP 5.0.1 / SOA-P 5.0.1 GA and JBDS 3.0.1

Seam WAR Deployment error with EAP 5.0.1 / SOA-P 5.0.1 GA and JBDS 3.0.1 ------------------------------------------------------------------------ Key: JBIDE-6389 URL: https://jira.jboss.org/browse/JBIDE-6389 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.1 Environment: jbds-3.0.1 #82 Linux 32, Sun JDK 1.6 Reporter: Jiri Peterka Assignee: Alexey Kazakov Priority: Critical Fix For: 3.1.2, 3.2.0.M1 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