[jboss-jira] [JBoss JIRA] Issue Comment Edited: (AS7-735) Failed OSGi deployments still show as .deployed in hotdeploy folder
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Thu May 12 03:56:18 EDT 2011
[ https://issues.jboss.org/browse/AS7-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12601574#comment-12601574 ]
Thomas Diesler edited comment on AS7-735 at 5/12/11 3:54 AM:
-------------------------------------------------------------
This would create a notion of correct bundle install order, which the client would have to resolve. For trivial cases like B before A this would be doable. However, we generally want to avoid that sort of ordering requirement. For a complex dependency graph it is nearly certain to fail.
Have a look at AS7-378 and its associated forum entries.
What you are probably looking for is a set of one deployment, with a requirement that all deployments in the set (i.e. just the one) can be started after all deployments in the set have been installed.
was (Author: thomas.diesler):
This would create a notion of correct bundle install order, which the client would have to resolve. For trivial cases like B before A this would be doable. However, we generally want to avoid that sort of ordering requirement.
Have a look at AS7-378 and its associated forum entries.
What you are probably looking for is a set of one deployment, with a requirement that all deployments in the set (i.e. just the one) can be started after all deployments in the set have been installed.
> 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
More information about the jboss-jira
mailing list