]
Alexey Kazakov updated JBIDE-8938:
----------------------------------
Assignee: Rob Stryker (was: Alexey Kazakov)
Component/s: JBossAS
We could create a new rename participant which will listen to corresponding events and
re-deploy ds resource if its path has been changed.
Not sure we should do it in Seam component. Maybe it's better to handle it in AS
plugin regardless of type of the project/resource.
Rob, Max?
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: JBossAS, 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: Rob Stryker
Fix For: 3.3.0.M3
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: