synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Supun Kamburugamuva <>
Subject Re: Deployer implementation for synapse
Date Tue, 25 Aug 2009 06:22:53 GMT
On Mon, Aug 24, 2009 at 3:57 AM, Ruwan Linton <>wrote:

> Folks,
> I was trying to implement the hot deployment and hot update of the synapse
> artifacts as per my proposal the to the list sometime back using the axis2
> deployers. But due to some restrictions and the architecture of the axis2
> deployers we cannot use that for synapse artifact deployment.
> The axis2 deployer hot update functionality has been implemented to call
> the unDeploy() method and then call the deploy method on that artifact. This
> causes an issue for syanpse since synapse has some restrictions on a
> absolute minimal configuration. We cannot let the user undeploy the main and
> fault sequences. But acording to the way the axis2 hot update has been
> implemented we do not have a means of differentiating the hot update
> undeploy call from the actual undeploy call. Actual undeploy call should
> prevent undeploying the main and fault sequences while it should be possible
> to undeploy those for hot updating.
> Also please note that with this approach there is a donwtime of the
> artifacts when doing the hot update which has to be prevented some how.
> Given the above facts it seems like we will have to go with a synapse
> implementation of the deployers.

If we go for a deployment like this, the implementation may require quite a
lot of synchronizations. I'm not sure how the implementation is going to be.
But I just want to bring this up so we can discuss if there is an issue.


> WDYT??
> Thanks,
> Ruwan
> --
> Ruwan Linton
> Technical Lead & Product Manager; WSO2 ESB;
> WSO2 Inc.;
> email:; cell: +94 77 341 3097
> blog:

Software Engineer, WSO2 Inc

View raw message