You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2009/07/16 00:35:14 UTC

[jira] Resolved: (ODE-635) Propagate DeploymentException when SA deployment fails.

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

Alex Boisvert resolved ODE-635.
-------------------------------

    Resolution: Won't Fix

> 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.