[
https://issues.apache.org/jira/browse/AXIS2-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12476853
]
Angel Todorov commented on AXIS2-2212:
--------------------------------------
Hi Deepal,
What do you mean by "terminate Axis2"? Axis2 is not "terminated" no matter how
faulty services are deployed. This is just a means of not just logging the
errors but reporting them. As you can see, everywhere where deployment calls
are made internally, the exceptions are catched. What is the issue with that ?
Thanks for the feedback.
Best Regards,
Angel
> Deployment patches
> ------------------
>
> Key: AXIS2-2212
> URL: https://issues.apache.org/jira/browse/AXIS2-2212
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
