Danushka, It is not the case that everybody uses the UI. In the RegistrySynchronizer case, there is no UI at all and the tenants will subscribe to a portion of their deployment hierarchy.
Also, this model was not only intended for Registry Eventing. This is a way to refer to a resource hierarchy in the registry. Sanjiva pointed out that we can have a powerful XQuery based querying mechanism if we can support such a syntax. Azeez On Tue, Mar 1, 2011 at 11:21 AM, Danushka Menikkumbura <[email protected]>wrote: > Sorry for the late reply ... was on the daily support call. > > So why do we need XPath here?. I thought the requirement was to have a > "Subscribe" button next to each resource that allows users to subscribe to > that particular resource. We can have a "Include descendents" check box to > include everything underneath. Subscribing to corresponding Event topic > should be done behind the scene. > > Thanks, > Danushka > > On Mon, Feb 28, 2011 at 8:56 PM, Afkham Azeez <[email protected]> wrote: > >> During a discussion today, we (Sanjiva, Asanka, Srinath & I) thought that >> it will be a good idea to use XPath-like syntax for selecting how to >> subscribe to Registry resource paths. We could support only some simple >> scenarios, and not the entire XPath syntax. Let me explain with an example. >> >> The RegistrySynchronizer needs to be notified when deployable artifacts >> are changed in the Registry. Let's say these artifacts are stored in >> the _system/config/deployment/*server/* path. Shown below is how the >> HelloService.aar is stored. >> >> /_system/config/deployment/* >> server/service-groups/foo/bar/HelloService.aar* >> >> These are the different way in which we can subscribe to different parts >> of this hierarchy. >> >> 1. /_system/config/deployment/server >> Selects *server* resource only [1] >> >> 2. /_system/config/deployment/server/descendant::* >> Selects descendants of *server* only, does not select *server. *Selected >> elements wil be server, service-groups, foo, bar, and HelloService.aar [1] >> >> 3. /_system/config/deployment/server/descendant-or-self::* >> Selects *server* and descendants. Selected elements wil be server, >> service-groups, foo, bar, and HelloService.aar [1] >> >> So, this standard syntax allows us to simply select a node and its >> descendants in different ways. >> >> Thoughts welcome. >> >> >> [1] XPath reference: http://zvon.org/comp/r/tut-XPath_1.html >> >> -- >> *Afkham Azeez* >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> * >> * >> *Member; Apache Software Foundation; >> **http://www.apache.org/*<http://www.apache.org/> >> * >> email: **[email protected]* <[email protected]>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > -- *Afkham Azeez* Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, * * *Member; Apache Software Foundation; **http://www.apache.org/*<http://www.apache.org/> * email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
