[
https://issues.apache.org/activemq/browse/SM-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56641#action_56641
]
Sergiy Mamitko commented on SM-1920:
------------------------------------
Hello, Freeman
Can you take a look at the BaseServiceUnitManager.undeploy() and swap next two
rows
if (serviceUnitRootPath != null) { doUndeploy(su); }
component.getRegistry().unregisterServiceUnit(su);
If it is impossible then can you tell why registering performed after
deployment and unregistering performed after undeployment?
Are resources should not release in vice versa way to initialization process?
Thanks,
Sergiy
> Deployment/Undeployment troubles if one of already deployed SU doesn't
> contain xbean.xml file in serviceUnitRootPath
> --------------------------------------------------------------------------------------------------------------------
>
> Key: SM-1920
> URL: https://issues.apache.org/activemq/browse/SM-1920
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-core
> Affects Versions: 3.3.1
> Reporter: Sergiy Mamitko
> Assignee: Freeman Fang
>
> If for some unknown reasons file xbean.xml was removed from deployed SU (from
> serviceUnitRootPath) then it is impossible to remove a whole SA without
> forther troubles.
> Looking into sources there is Deployer.canDeploy method which is used in
> implementations for doDeploy and for doUndeploy. But if xbean.xml is
> necessary for deployment why it is need for undeployment process.
> Moreover if xbean is absent, then SU will not be unregistered from component
> and it will be impossible to redeploy the same SA.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
