Hi Hiranya If a user needs to add an Observer implementation, how he can specify that? - There must be a configurable option. If you expect to allow a configurable option as synapse.properties file, then using SynapsePropertiesLoader at any location you want. Then, you can load properties and creates Observers and add. This will be simple and will not need any API changes.
Thanks Indika On Mon, Jul 27, 2009 at 2:11 PM, Hiranya Jayathilaka<[email protected]> wrote: > Hi Folks, > > I have added the SynapseObserver interface and the AbstractSynapseObserver > class to the trunk as well as the 1.3 branch. I was thinking that it would > be great if we can provide a mechanism to register an observer with the > SynapseConfiguration before it gets populated by various entries by the > configuration builder. In other words a mechanism to register an observer > right after a SynapseConfiguration object is constructed using the 'new' > keyword. That way, one can write an observer which monitors the > configuration right from the configuration build time. I had a look at the > existing code and it seems it is not easy to provide such a mechanism with > the current design. So I would like to get some ideas from you all regarding > this. > > I think we'll need to introduce a factory class which constructs > SynapseConfiguration objects with the necessary observers registered. > Configuration builders can use the factory to get a fresh > SynapseConfiguration and start populating it. WDYT? Your ideas are highly > appreciated. > > > Thanks > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
