Hi, I was able to implement the above feature for ES based on the OSGI services available. The registry provides an OSGI service for Subscriptions and Notifications: Eventing Service. The Eventing Service interface exposed as an OSGi Service can be found at [1]. The article at [2] explains the capabilities registry provides under Subscription and Notification.
[1] https://svn.wso2.org/repos/wso2/tags/carbon-platform/2.0.2/carbon-components/registry/org.wso2.carbon.registry.eventing/src/main/java/org/wso2/carbon/registry/eventing/services/EventingService.java [2] http://wso2.com/library/articles/eventing-notifications-wso2-governance-registry/ Thank you, Sameera On Thu, Jul 24, 2014 at 10:01 PM, Sameera Jayaratna <[email protected]> wrote: > Hi, > > I am working on implementing subscription functionality in Enterprise > Store based on Registry features. I have looked into carbon-governance and > carbon-registry. According to my observations > *org.wso2.carbon.registry.info.ui.clients.InfoServiceClient > *provides functionality required for subscribing to a resource or a > collection, such as *subscribe*, *subscribeRest* and *unsubscribe*. > > Is using this client the best way to implement the above functionality or > is there a better approach? > > Thank you, > Sameera > > -- > > > > *Thanks & Regards,Sameera Jayaratna Software Engineer; **WSO2 Inc. * > > *lean . enterprise . middleware | http://wso2.com <http://wso2.com> * > -- *Thanks & Regards,Sameera Jayaratna Software Engineer; **WSO2 Inc. * *lean . enterprise . middleware | http://wso2.com <http://wso2.com> *
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
