[jboss-jira] [JBoss JIRA] Reopened: (JBDEPLOY-225) Create ErrorHandler to DeploymentControllerContext
Ales Justin (JIRA)
jira-events at lists.jboss.org
Tue Dec 15 17:03:30 EST 2009
[ https://jira.jboss.org/jira/browse/JBDEPLOY-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ales Justin reopened JBDEPLOY-225:
----------------------------------
Assignee: Ales Justin (was: Thomas Diesler)
If you found a workaround it doesn't mean this should not be implemented.
> Create ErrorHandler to DeploymentControllerContext
> ---------------------------------------------------
>
> Key: JBDEPLOY-225
> URL: https://jira.jboss.org/jira/browse/JBDEPLOY-225
> Project: JBoss Deployers
> Issue Type: Feature Request
> Reporter: Thomas Diesler
> Assignee: Ales Justin
>
> The MC Framework incorrectly uninstalls the bundle if there is a failure in bundle.start()
> The controller context reached its required stage DESCRIBED after bundle install. A subsequent call to bundle.start() is supposed to transition to stages CLASSLOADER and then INSTALLED, which corresponds to the Bundle states RESOLVED and ACTIVE respectively.
> If the transition to INSTALLED fails, the controller context gets undeployed, which causes the bundle to transition to UNINSTALLED.
> The desired behaviour is:
> * on fail to resolve: remain in state INSTALLED
> * on fail to start: remain in state RESOLVED
> The proposed solution is to add an ErrorHandler to the DeploymentControllerContext
> if it is an OSGi deployment
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list