You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Angel Todorov (JIRA)" <ji...@apache.org> on 2007/02/09 14:01:31 UTC
[jira] Created: (AXIS2-2151) Deployment exceptions should be
propagated up to the caller
Deployment exceptions should be propagated up to the caller
-----------------------------------------------------------
Key: AXIS2-2151
URL: https://issues.apache.org/jira/browse/AXIS2-2151
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: deployment
Affects Versions: 1.1.1
Environment: any
Reporter: Angel Todorov
The methods in the DeploymentEngine doDeploy() and unDeploy() should propagate their exceptions up to the caller, instead of only catching them and logging any possible warnings/errors that may occur during deploy. This is particularly useful for remote deployment.
I have already started working on this and can contribute this feature very soon in the next days. Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2151) Deployment exceptions should be
propagated up to the caller
Posted by "Angel Todorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Angel Todorov resolved AXIS2-2151.
----------------------------------
Resolution: Duplicate
Look at AXIS2-2212
> Deployment exceptions should be propagated up to the caller
> -----------------------------------------------------------
>
> Key: AXIS2-2151
> URL: https://issues.apache.org/jira/browse/AXIS2-2151
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: deployment
> Affects Versions: 1.1.1
> Environment: any
> Reporter: Angel Todorov
>
> The methods in the DeploymentEngine doDeploy() and unDeploy() should propagate their exceptions up to the caller, instead of only catching them and logging any possible warnings/errors that may occur during deploy. This is particularly useful for remote deployment.
> I have already started working on this and can contribute this feature very soon in the next days. Thank you.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org