[
https://issues.apache.org/activemq/browse/SM-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56631#action_56631
]
Freeman Fang commented on SM-1920:
----------------------------------
Hi Sergiy,
I don't think this is a bug.
the xbean.xml is also very useful for undeployment as this give us opportunity
to clean up some resources which init from this spring bean.
You can't only remove some xbean.xml from data folder, as this will damage the
integrity of deployed artifact, but you can remove data folder as a whole to
get a clean enviorment.
Freeman
> 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.
