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 <cigi_yan...@yahoo.com> 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 <andreas.veit...@gmail.com>* wrote: > > From: Andreas Veithen <andreas.veit...@gmail.com> > Subject: Re: hot deployment and 'undeployment' > To: axis-user@ws.apache.org, cigi_yan...@yahoo.com > 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 <cigi_yan...@yahoo.com> 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
