So what if we put a handler there to disable all requests for the service being removed (or already removed)? the handler could be triggered by a "undeploy" action.
I think it is more complicated if we consider the inconsistency among axis2 listener, memory allocated, dynamically loaded libraries, etc. But if hot deployment is provided, it is natural to pair with a hot undeployment, if not 'hot update'. To think more, if we list scenarios that require hot deployment, I think most of them would love to have hot undeployment, too. I'd like to see such a feature available to users, even restrictions need to be applied (e.g., version and library compatibility) Thanks, Yan --- On Thu, 2/12/09, keith chapman <[email protected]> wrote: From: keith chapman <[email protected]> Subject: Re: hot deployment and 'undeployment' To: [email protected], [email protected] Date: Thursday, February 12, 2009, 10:40 AM Yes removing a service at runtime could put request coming to that service in a Zombie state. Thanks, Keith. On Thu, Feb 12, 2009 at 8:34 PM, Yan Liu <[email protected]> wrote: I know about "hot update". My question was: is "hot deployment + hot undeployment = hot update"? Hot update is disabled by default because it might leave axis2 in uncertain state and ongoing service data might be lost. I guess the same thing happens when removing .aar manually. am i right? Thanks, Yan --- On Thu, 2/12/09, Andreas Veithen <[email protected]> wrote: From: Andreas Veithen <[email protected]> Subject: Re: hot deployment and 'undeployment' To: [email protected], [email protected] Date: Thursday, February 12, 2009, 2:59 AM Yan, Hot update/undeployment can be enabled by adding the following line to your axis2.xml: <parameter name="hotupdate">true</parameter> Regards, Andreas On Thu, Feb 12, 2009 at 05:25, Yan Liu <[email protected]> wrote: > Hi, > > Hot deployment feature in Axis2 1.4.1 is great. I'd like to create an > automatic service deployment module for our software system using hot > deployment. I have two questions, though: > 1. is there documentation on programmatic way for hot deployment? I looked > at http://www.ibm.com/developerworks/webservices/library/ws-axis2soap/ , but > prefer a complete example or tutorial > 2. if i delete the .aar in axis2's service repository, does axis2 detect > that the service is gone, then update the list of services? If so, can it be > considered "hot undeployment"? If so, then "hot update" can be done by hot > deployment plus hot undeployment with a predefined interval in axis2 config > > Thanks, > Ian > > -- Keith Chapman Senior Software Engineer WSO2 Inc. Oxygenating the Web Service Platform. http://wso2.org/ blog: http://www.keith-chapman.org
