[jboss-jira] [JBoss JIRA] Commented: (AS7-735) Failed OSGi deployments still show as .deployed in hotdeploy folder
[
https://issues.jboss.org/browse/AS7-735?page=com.atlassian.jira.plugin.sy...
]
David Bosschaert commented on AS7-735:
--------------------------------------
I think that BundleA should fail its hot-deployment (which also includes starting), unless
BundleB is also present.
I do understand that EJB doesn't have the same states as OSGi, but from a user's
perspective I think if a bundle fails to resolve the deployment should be marked as
failed. This might be hard to do, but from a user's perspective it's consistent
with the behaviour of JavaEE deployments.
Failed OSGi deployments still show as .deployed in hotdeploy folder
-------------------------------------------------------------------
Key: AS7-735
URL: https://issues.jboss.org/browse/AS7-735
Project: Application Server 7
Issue Type: Bug
Components: OSGi
Affects Versions: 7.0.0.CR1
Reporter: David Bosschaert
Assignee: Jason Greene
When deploying a bundle in AS7 in the hotdeploy directory that has missing dependencies
and therefore fails the OSGi resolution process, the deployment still shows up as deployed
successfully (a .deployed file appears).
I think it should be marked as .failed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira