On Mon, Aug 16, 2010 at 1:46 PM, Miyuru Wanninayaka <miy...@wso2.com> wrote:
> > > On Mon, Aug 16, 2010 at 11:25 AM, Ruwan Linton <ru...@wso2.com> wrote: > >> On 8/16/10 10:54 AM, Supun Kamburugamuva wrote: >> > There are two ways to implement this. >> > >> > 1. We can simply read the configuration from the file system and them >> > override the current synapse configuration with the sample >> > configuration. This leads to the destruction of current configuration. >> > >> > 2. The second approach is to build the synapse configuration from the >> > beginning. This includes initializing the persistence again to fit the >> > sample etc. This preserves the current ESB configuration. >> > >> > I prefer the second approach. >> +1, actually if we can keep the synapse configurations which are loaded >> at runtime as alternate configurations and have only one configuration >> as active that would be the ideal. >> > This is what we do in test automation FW. Thanks, Samisa... Samisa Abeysinghe VP Engineering WSO2 Inc. http://wso2.com http://wso2.org
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
