axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal jayasinghe <deep...@gmail.com>
Subject Re: [PROPOSAL] Axis2 Deployer behaviour on hot update
Date Thu, 27 Aug 2009 17:51:45 GMT

>
> 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.

Mime
View raw message