8:26 a.m.
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
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
11:32 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
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
5:48 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-8938:
----------------------------------
Fix Version/s: 3.3.0.M3
(was: 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.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: http://www.atlassian.com/software/jira
7:11 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
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: http://www.atlassian.com/software/jira
5:49 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-8938:
------------------------------------
definitely belongs in the AS plugins since htat's where the single deployable factory
is. I'll do investigation.
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: http://www.atlassian.com/software/jira
11:02 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-8938:
-------------------------------
Fix Version/s: 3.3.0.M4
(was: 3.3.0.M3)
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/Servers, Seam 2
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.M4
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
6:01 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-8938.
--------------------------------
Resolution: Done
In trunk for m4
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/Servers, Seam 2
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.M4
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
5:36 a.m.
New subject: [JBoss JIRA] (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Martin Malina updated JBIDE-8938:
---------------------------------
Fix Version/s: 3.3.0.Beta3
(was: 3.3.0.M4)
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/Servers, Seam 2
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.Beta3
Attachments: Screen Shot 2012-04-05 at 12.34.14.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:36 a.m.
New subject: [JBoss JIRA] (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Martin Malina updated JBIDE-8938:
---------------------------------
Attachment: Screen Shot 2012-04-05 at 12.34.14.png
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/Servers, Seam 2
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.Beta3
Attachments: Screen Shot 2012-04-05 at 12.34.14.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:17 p.m.
New subject: [JBoss JIRA] (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-8938:
-------------------------------
Attachment: JBIDE-8938.ogg
This is a screenshot of me not able to replicate it. I was able to replicate it once,
but, it was not easy to replicate, and also had no effect at all.
Periodically, unused deployables are cleansed, (such as after publishes or after adding a
new module to a server). This is a cosmetic-only issue. It has no effect at all, though
it may confuse users.
I suggest making a new jira and marking it optional or minor. The main topic of this jira
is fixed.
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/Servers, Seam 2
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.Beta3
Attachments: JBIDE-8938.ogg, Screen Shot 2012-04-05 at 12.34.14.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:17 p.m.
New subject: [JBoss JIRA] (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-8938.
--------------------------------
Resolution: Done
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/Servers, Seam 2
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.Beta3
Attachments: JBIDE-8938.ogg, Screen Shot 2012-04-05 at 12.34.14.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:34 a.m.
New subject: [JBoss JIRA] (JBIDE-8938) Renaming a seam project makes the ds.xml undeployable
[
https://issues.jboss.org/browse/JBIDE-8938?page=com.atlassian.jira.plugin...
]
Martin Malina closed JBIDE-8938.
--------------------------------
I can no longer reproduce the issue with two deployable -ds.xml files. It works for me
now. Closing. Verified in JBT nightly 2012-04-29.
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/Servers, Seam 2
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.Beta3
Attachments: JBIDE-8938.ogg, Screen Shot 2012-04-05 at 12.34.14.png
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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5093
days inactive
5447
days old
jbosstools-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Alexey Kazakov (JIRA) -
Martin Malina (JIRA)
-
Rob Stryker (JIRA)