On Thu, Aug 27, 2009 at 11:21 PM, Deepal jayasinghe <deep...@gmail.com>wrote:
> > > > > 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 :-) > Of course you can if the file is there then that is hot-update else it > is un deployment. > > > > > > > > > > > > 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. > Yes, as I mentioned earlier if the file is there then that is > hot-update, else un-deployment. So it should not be a big issues. > > > > Anyway I feel I should go for a synapse deployer :-) > I though you already have deployer for synapse. I mean a new deployer framework implementation, not an deployer.. anyway synapse doesn't have a deployer yet. Thanks, Ruwan -- 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
