axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <>
Subject [jira] Commented: (AXIS2-2212) Deployment patches
Date Thu, 01 Mar 2007 05:38:50 GMT


Deepal Jayasinghe commented on AXIS2-2212:

At the initial development time we thought not to terminate Axis2 if someone deploy a faulty
service. As I can in your patch what you have done is throw the exception if something goes

I am not totally happy with doing that , at least we need to have a parameter to control the
behavior. Something like
<parameter name="terminateOnError">true</terminateOnError>

> Deployment patches
> ------------------
>                 Key: AXIS2-2212
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: deployment
>         Environment: JDK 1.5, Tomcat 5.5.20, Windows XP, Axis 2 HEAD revision.
>            Reporter: Angel Todorov
>         Attachments: diff_Deployer.txt, diff_DeploymentEngine.txt, diff_RepositoryListener.txt,
diff_ServiceDeployer.txt, diff_WSInfoList.txt, svn_diff.txt
> These modifications provide functionality for:
> 1) propagating exceptions up
> 2) remote deployment via the method updateRemote() in the repo listener.
> The remote deployment can be achieved by obtaining the repoListener
> instance from the WarBasedConfigurator in the AxisServlet, and calling
> updateRemote() , after the remotely received file has been copied in
> the services dir. This allows for immediate feedback but must be
> syncronized with the Scheduler that is constantly running for
> hot-deployment.
> Best,
> Angel

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:
For additional commands, e-mail:

View raw message