Hi Sameera, With regards to the two new event types that you introduced, I think this is the best workaround possible right now, since the registry events are not easily customizable. There is one possibility though, [1], but that is not the most ideal. But, this is something you were aware of?
[1] https://docs.wso2.com/display/Governance460/Notification+E-mail+Customization+Sample Thanks, Senaka. On Mon, Jul 28, 2014 at 10:16 AM, Sameera Jayaratna <samee...@wso2.com> wrote: > Hi All, > > I have implemented a component for ES to provide the following > functionality, > > 1. *Register custom Event Types* > Currently, Registry provides several events to which users can > subscribe to. i.e. Create LC, Delete LC, Update, Delete etc. By using > custom Event Type registration we can introduce new Event Types (i.e. Asset > Update, New Asset Version Created etc.) > 2. *Subscribe to available Event Types* > Allows subscribing to available event types via the same options > provided by the Registry (i.e. e-mail, role profile, user profile etc.) > 3. *Notify a specific event has been triggered* > Notify the subscribed user of a particular event > > The above functionality is implemented based on the Eventing OSGI Service. > > The registering of new event types is used to introduce event types that > occur in ES. But we have defined *Store Asset Update* which is similar to > *Resource > Update* in registry and *Store LC State Change* which is similar to *Change > LC State. *It is done as a workaround to customize the message sent when > the above events are triggered. > > Any feedback is appreciated. > > Thank you, > Sameera > > > On Fri, Jul 11, 2014 at 5:07 PM, Sameera Jayaratna <samee...@wso2.com> > wrote: > >> Hi All, >> >> According to the requirement in [1], I am working on implementing the >> $subject. >> >> *Requirement* >> >> The requirement is to send an e-mail notification to users with a >> specified role once the lifecycle state of an asset changes. The roles to >> be notified needs to be configured for each state transition. A sample use >> case of the requirement is as follows. >> >> In Connector Store, once a connector is newly added by a developer, it >> can be promoted to 'In-Review' state. Then all the users with the role >> 'reviewer' need to be notified. Once the connector is reviewed and >> transferred to 'Published' state, the developer needs to be notified. >> >> *Approach* >> >> As per the discussions I had with Ruchira and SameeraM, >> >> - the roles to be notified in each state transition could be defined >> in the lifecycle configuration. >> - An executor in ES which will be triggered on lifecycle state change >> can be improved to handle email sending. >> - implement this feature based on eventing feature in registry >> >> *Issues* >> >> We require to send a customized message in the email depending on the >> state transition, asset type etc. Currently, the message body can not be >> customized in registry. >> >> What could be the best approach in implementing the above feature? >> >> [1] https://wso2.org/jira/browse/STORE-457 >> >> 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> * > -- *[image: http://wso2.com] <http://wso2.com> Senaka Fernando* Software 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; ext: 51736*; *M: +44 782 741 1966 Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
