In the article "The Axis2 Deployment model, Part 1"
(http://www-128.ibm.com/developerworks/library/ws-axis2soap/index.html), it
suggests the one not use this feature in production:
"However, it's not advisable to use hot update in a real-time system,
because it could result in the system leading into an unknown state."
Is there an alternative, other than restarting Tomcat? If your production
instance of Axis2 is providing multiple services, it's not great to bring
them down as well.
Well I was talking about the hot-update . Meaning you are trying to
change existing (running) services. If you want to add new services
then there is no problem with that.
Can anyone provide more information on what the drawbacks of hotupdate are?
Say , you have system where a request processing for the service you are
going to update. Then that particular service processing might lead to
an unknown state.
-Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
