You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Greg Lucas (JIRA)" <ji...@apache.org> on 2009/08/12 22:31:35 UTC

[jira] Updated: (SMX4-321) Component task result from ServiceUnitManager.deploy is ignored

     [ https://issues.apache.org/activemq/browse/SMX4-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Greg Lucas updated SMX4-321:
----------------------------

    Attachment: SMX4-321-02-patch.txt
                SMX4-321-01-patch.txt

Patch to check the component-task-result string and propagate (un)deploy failures. The 01-patch is the basic fix. The 02-patch revises things further to allow component-task-result strings that do not properly declare the namespace. I'm not sure we want to support that, but had done it to test with Ode so I'm providing what I had.

> Component task result from ServiceUnitManager.deploy is ignored
> ---------------------------------------------------------------
>
>                 Key: SMX4-321
>                 URL: https://issues.apache.org/activemq/browse/SMX4-321
>             Project: ServiceMix 4
>          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.