[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable

[Alexey Kazakov (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kazakov updated JBIDE-8938:
----------------------------------

    Fix Version/s: 3.3.0.M2


> Renaming a seam project makes the ds.xml undeployable
> -----------------------------------------------------
>
>                 Key: JBIDE-8938
>                 URL: https://issues.jboss.org/browse/JBIDE-8938
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 3.2.1.M1
>         Environment: jbdevstudio-product-eap-macosx-cocoa-4.1.0.v201105091943R-H400-M1.jar
> Mac OS X 10.6 Snow Leopard
>            Reporter: Martin Malina
>            Assignee: Alexey Kazakov
>             Fix For: 3.3.0.M2
>
>
> If you rename a seam project it fails to deploy again because of failed dependencies:
> DEPLOYMENTS MISSING DEPENDENCIES:
>   Deployment "persistence.unit:unitName=#SeamWar" is missing the following dependencies:
>     Dependency "jboss.jca:name=SeamWarDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=SeamWarDatasource,service=DataSourceBinding' **")
> DEPLOYMENTS IN ERROR:
>   Deployment "jboss.jca:name=SeamWarDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=SeamWarDatasource,service=DataSourceBinding' **
> This happens because after the renaming, the ds file becomes undeployable. If you mark it as deployable again, you can then deploy it and also the renamed seam project deploys correctly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira