On Thu, Aug 27, 2009 at 8:32 PM, Deepal jayasinghe <deep...@gmail.com>wrote:
> > > > Let me first describe how Hot update works in axis2, correct me if I > > am wrong but from what I have figured out so far, axis2 repository > > listener task calls unDeploy method of the deployer implementation > > first and then calls the deploy method again to deploy the artifact > > with the changes. > Yes that is correct. > > > > So this approach has two issues, > > > > 1. There is a considerable downtime of the artifact which is being > > hot updated > > > In Axis2, specially in production hot deployment is not something people > are going to use regularly. So downtown or hot-update is not an big > issues (rather they will turn off both hot-deployment and hot-update) > > > > 1. There is no means of knowing the case where the undeploy method > > being called, for example synapse needs to have a main sequence > > for it to operate properly, so synapse has to force the user to > > not to undeploy the main sequence while it should allow the user > > to hot update it. > > > You can do this with your deployer. No I can't, I guess I have explained why I can't use it as well, because I cannot differentiate the undeployment call for the hot update and real undeployment. Well, what Amila suggested will work though :-) > > > > > I propose adding a update method to the Deployer interface or passing > > the state as an argument, > I would consider undeploy as the update method you can do whatever you > want there, and you can just ignore at when it call deploy method. > (I know in undeploy method you only get the filename, but since your > deployer is domain specific you know what to do with the file name) No, the issue is we need to invoke a different code in the case of hot update. Anyway I feel I should go for a synapse deployer :-) Thanks, Ruwan > > > we could use the DeploymentFileData class to provide the operation, > Thanks, > Deepal > -- Ruwan Linton Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb WSO2 Inc.; http://wso2.org email: ru...@wso2.com; cell: +94 77 341 3097 blog: http://ruwansblog.blogspot.com
