Hi Senaka, Yes existing notifications are used with Registry eventing.
- A new event type is registered as LifecycleNotificationEvent. - Users can subscribe to that event type for a resource. - Resource information's are stored in the newly created table when a lifecycle is attached to a resource or when a lifecycle state change occurs (because there can be multiple checkpoints for a lifecycle state). - Then a schedule task is configure to execute a scheduler which eventually filter the notifications by date from the table. This reduces iterating over all the resources. - If the users have subscribed to the notifications, then the notification service is used to send the notifications. - REG_PATH is stored in the new table to overcome dependencies. - This notifications sending process runs independently without interacting with other database tables. Thanks On Fri, Feb 27, 2015 at 9:54 PM, Senaka Fernando <[email protected]> wrote: > Hi Prasanna, > > Why don't we or can't we use the existing Notifications capabilities > inside the registry and also the Event component in the platform for this > purpose. > > Your solution has issues when it comes to a distributed deployment and > especially when things like mounting etc gets into the picture the REG_PATH > etc will not be easily deducible. > > Thanks, > Senaka. > > On Fri, Feb 27, 2015 at 3:55 PM, Prasanna Dangalla <[email protected]> > wrote: > >> Hi Senaka, >> >> This table contains details needed to send notifications when a lifecycle >> reaches a defined checkpoint in lifecycle configuration. lifecycle >> configuration with checkpoints is attached[1]. [This is a new feature]. A >> schedule task is introduced in registry.xml to send the notifications . >> Data is stored in a new table to reduce iterations over the resources to >> get the resources that need to send the notifications. >> >> At the moment table contains REG_SCH_ID, REG_PATH, REG_LC_NAME, >> REG_LC_CHECKPOINT_ID, REG_LC_NOTIFICATION_DATE, REG_UUID, REG_TENANT_ID >> columns. >> REG_ prefix can be changed to GOV_ if we move this to >> carbon-governance.This table is accessed only from carbon-governance >> components. >> [1] >> lifecycle-configuration.xml >> <https://docs.google.com/a/wso2.com/file/d/0B3yd4olgBhFVTm5hUEduSWxoVW8/edit?usp=drive_web> >> >> >> Thanks >> >> >> >> >> On Fri, Feb 27, 2015 at 8:54 PM, Senaka Fernando <[email protected]> wrote: >> >>> Hi Prasanna, >>> >>> What's this table about and what is that going to contain? >>> >>> Thanks, >>> Senaka. >>> >>> On Fri, Feb 27, 2015 at 2:13 PM, Prasanna Dangalla <[email protected]> >>> wrote: >>> >>>> Hi All, >>>> >>>> I need to introduce a new table which is *only* needed for >>>> carbon-governance. AFAIK currently all the database scripts are in >>>> carbon-kernel [1]. AFAIU new table should be managed separately in >>>> carbon-governance with the introduction of a new prefix like GOV_. >>>> >>>> Feedback on this approach is highly appreciated. >>>> >>>> >>>> [1] - >>>> https://github.com/wso2/carbon4-kernel/tree/master/distribution/kernel/carbon-home/dbscripts >>>> >>>> Thanks >>>> -- >>>> Prasanna Dangalla >>>> Software Engineer, WSO2, Inc.; http://wso2.com/ >>>> lean.enterprise.middleware >>>> >>>> cell: +94 777 55 80 30 | +94 718 11 27 51 >>>> twitter: @prasa77 >>>> >>> >>> >>> >>> -- >>> >>> >>> *[image: http://wso2.com] <http://wso2.com>Senaka Fernando* >>> Solutions Architect; WSO2 Inc.; http://wso2.com >>> >>> >>> >>> *Member; Apache Software Foundation; http://apache.org >>> <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 >>> 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; >>> >>> >>> *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In: >>> http://linkedin.com/in/senakafernando >>> <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware >>> >> >> >> >> -- >> Prasanna Dangalla >> Software Engineer, WSO2, Inc.; http://wso2.com/ >> lean.enterprise.middleware >> >> cell: +94 777 55 80 30 | +94 718 11 27 51 >> twitter: @prasa77 >> > > > > -- > > > *[image: http://wso2.com] <http://wso2.com>Senaka Fernando* > Solutions Architect; WSO2 Inc.; http://wso2.com > > > > *Member; Apache Software Foundation; http://apache.org > <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 > 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; > > > *M: +44 782 741 1966 <%2B44%20782%20741%201966>Linked-In: > http://linkedin.com/in/senakafernando > <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware > -- Prasanna Dangalla Software Engineer, WSO2, Inc.; http://wso2.com/ lean.enterprise.middleware cell: +94 777 55 80 30 | +94 718 11 27 51 twitter: @prasa77
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
