> > > Then there's the question of how to do the update - ideal is to let > messages that are already being processed be processed by the still > active version and to direct new messages to the new version. I'm not > sure that's implementable though .. or it would require one to bring > that concept into dispatchers etc. to do the right thing. Ideal is for > it to be burnt into the AxisConfig but that's a *huge* change. It is doable, and in fact I have done that, but did not commit my changes, since it was just for fun :). In AxisService you have a method called activate/inactivate, when you inactive a service system does not take any more request to that service (will throw an exception saying service not found) and will process all the current messages. Then, you need call the deployment engine to update the new service (Deployment engine has a method to load a particular services). Then you back in business.
Thanks, Deepal
