[
https://issues.apache.org/jira/browse/ODE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731606#action_12731606
]
Greg Lucas commented on ODE-635:
--------------------------------
I've filed a ServiceMix 4 issue related to this: SMX4-321
ServiceMix 3 handles either the DeploymentException or the FAILED task-result,
while in SMX4 the task-result is ignored. This looks wrong given that the spec
implies either approach can be used to signal a deployment failure. (See also
<http://forums.sun.com/thread.jspa?threadID=688608> which supports this
interpretation of the spec.)
> Propagate DeploymentException when SA deployment fails.
> -------------------------------------------------------
>
> Key: ODE-635
> URL: https://issues.apache.org/jira/browse/ODE-635
> Project: ODE
> Issue Type: Improvement
> Components: JBI Integration
> Affects Versions: 1.3.2, 1.3.3, 2.0
> Environment: ServiceMix 4
> Reporter: Daniel Dominguez
> Attachments: ODE-635.patch
>
>
> I'm working on deployment tooling for ServiceMix4 / FUSE. The deploy and
> undeploy method in OdeSUManager does not throw a DeploymentException when
> there is a problem with a service assembly (i.e. bad deploy.xml). In
> contrast the start and stop methods both throw DeploymentException when
> appropriate.
> The problem this causes for me is that when I attempt to deploy and start a
> service assembly, the deploy appears to succeed but the start returns an
> unrelated error which is difficult to diagnose.
> I've created a simple patch which will throw the DeploymentException instead
> of an error string which is ignored by smx4.
> Is this a reasonable approach?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
