You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2009/09/03 20:57:14 UTC
[jira] Moved: (SMX4NMR-142) Component task result from
ServiceUnitManager.deploy is ignored
[ https://issues.apache.org/activemq/browse/SMX4NMR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet moved SMX4-321 to SMX4NMR-142:
----------------------------------------------
Key: SMX4NMR-142 (was: SMX4-321)
Project: ServiceMix NMR (was: ServiceMix 4)
> Component task result from ServiceUnitManager.deploy is ignored
> ---------------------------------------------------------------
>
> Key: SMX4NMR-142
> URL: https://issues.apache.org/activemq/browse/SMX4NMR-142
> Project: ServiceMix NMR
> Issue Type: Bug
> Reporter: Greg Lucas
> Attachments: SMX4-321-01-patch.txt, SMX4-321-02-patch.txt
>
>
> In SMX3 the result from ServiceUnitManager.deploy was examined to determine the task result (SUCCESS or otherwise). As the JBI spec implies, this allows either a DeploymentException or a task-result of FAILED to signal a deployment failure.
> In SMX4 the task result is being ignored and deployment is considered successful unless an exception is thrown.
> See http://issues.apache.org/jira/browse/ODE-635 where this issue was originally raised; the ODE ServiceUnitManager does not throw an exception and so deployment failures are not detected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.