--- On Thu, 2/12/09, keith chapman keithgchap...@gmail.com wrote:
From: keith chapman keithgchap...@gmail.com
Subject: Re: hot deployment and 'undeployment'
To: axis-user@ws.apache.org, cigi_yan...@yahoo.com
Date: Thursday, February 12, 2009, 10:40 AM
Yes removing a service at runtime could put
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
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
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
restrictions need to be
applied (e.g., version and library compatibility)
Thanks,
Yan
--- On Thu, 2/12/09, keith chapman keithgchap...@gmail.com wrote:
From: keith chapman keithgchap...@gmail.com
Subject: Re: hot deployment and 'undeployment'
To: axis-user@ws.apache.org, cigi_yan...@yahoo.com
be
done by hot deployment plus hot undeployment with a predefined interval
in axis2 config
Thanks,
Ian
