Hi, We may have couple of use case to add registry resources from a mediation flow (similar to a DBReport behavior). So we might need a similar mediator which can add content in to the registry. This should use the org.apache.synapse.registry.Registry api and we should not write any carbon specific code in it.
But this is not a good approach to achieve coordinations between tasks. We are planning to have a new scheduled task implementation on top of Hazelcast which can cater all such requirements. On Thu, Jan 2, 2014 at 4:05 PM, Amila Maha Arachchi <[email protected]> wrote: > Hi, > > At the moment, ESB can only get the registry properties. But it seems > useful to put and update properties to the registry too. > > This can be used when coordinating a scheduled task between multiple ESB > nodes. If we have multiple ESB nodes and theres a scheduled task, we dont > have a way to control them running in a single node. We have the pinned > server concept. But it does not have a failover mechanism. So, if we can > use a flag in the registry and if ESB can update it when starting the task > (similar to a lock we use in programming), it can be used to coordinate. > > For the above requirement, ESB needs to support putting and updating > properties to the registry. I think it wont be difficult since get is > already there. > > Regards, > AmilaM. > > -- > *Amila Maharachchi* > Senior Technical Lead > WSO2, Inc.; http://wso2.com > > Blog: http://maharachchi.blogspot.com > Mobile: +94719371446 > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
