On Tue, May 12, 2015 at 12:55 PM, Sajith Ravindra <[email protected]> wrote:
> Hi Suho, > > At Siddhi level we can get the stream name of the fired event. But, can we > get hold to the stream name when it's sent through a output adapter(SOAP, > JMS) from CEP server at the receiving end? > > Yes, its just another stream in Siddhi, so if you have exported that then ya you can, Suho > Thanks > *,Sajith Ravindra* > Senior Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 77 2273550 > blog: http://sajithr.blogspot.com/ > <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> > > On Tue, May 12, 2015 at 1:54 PM, Sriskandarajah Suhothayan <[email protected]> > wrote: > >> >> >> On Tue, May 12, 2015 at 12:15 PM, Sajith Ravindra <[email protected]> >> wrote: >> >>> Will it be worth to add the trigger name also to the event that's being >>> pushed? For an example if a particular execution plan has two triggers, it >>> will be useful for the client to identify which trigger is fired. WDYT? >>> >>> Thats what we are doing here, the event will be published on the stream >> with the same name of the trigger, and having the trigger name as an >> attribute is redundant hence we don't have that. >> >> Suho >> >>> Thanks >>> *,Sajith Ravindra* >>> Senior Software Engineer >>> WSO2 Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 77 2273550 >>> blog: http://sajithr.blogspot.com/ >>> <http://lk.linkedin.com/pub/shani-ranasinghe/34/111/ab> >>> >>> On Tue, May 12, 2015 at 1:20 PM, Sriskandarajah Suhothayan < >>> [email protected]> wrote: >>> >>>> >>>> >>>> On Tue, May 12, 2015 at 11:31 AM, Sachini Jayasekara <[email protected] >>>> > wrote: >>>> >>>>> Hi Suho, >>>>> >>>>> What's the behavior of the 2nd trigger definition? >>>>> >>>>> define trigger fooTriggerStream at '56, *, *, *, 8'; >>>>> >>>>> Does it trigger an event at a specific time? >>>>> >>>> This is suppose to trigger an event based on cron[1] >>>> >>>> Suho >>>> >>>> [1] >>>> http://www.quartz-scheduler.org/documentation/quartz-1.x/tutorials/crontrigger >>>> >>>> >>>>> >>>>> >>>>> Thanks, >>>>> Sachini >>>>> >>>>> >>>>> On Tue, May 12, 2015 at 11:09 AM, Sriskandarajah Suhothayan < >>>>> [email protected]> wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> Currently we don't have out of the box support for triggers in >>>>>> Siddhi, hence we are introducing trigger support as follows, >>>>>> >>>>>> Users can define triggers as follows; >>>>>> >>>>>> define trigger triggerStream at every 5 min; >>>>>> >>>>>> define trigger fooTriggerStream at '56, *, *, *, 8'; >>>>>> >>>>>> define trigger barStream at 'start'; >>>>>> >>>>>> This will implicitly crate a stream with the same name as of the >>>>>> trigger and push events having an attribute 'triggered time' behind the >>>>>> scenes. >>>>>> >>>>>> A stream that will be implicitly generated will look following; >>>>>> >>>>>> define stream fooTriggerStream (triggered_time long); >>>>>> >>>>>> Regards >>>>>> Suho >>>>>> >>>>>> -- >>>>>> >>>>>> *S. Suhothayan* >>>>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>>>> *WSO2 Inc. *http://wso2.com >>>>>> * <http://wso2.com/>* >>>>>> lean . enterprise . middleware >>>>>> >>>>>> >>>>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>>>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | >>>>>> linked-in: >>>>>> http://lk.linkedin.com/in/suhothayan >>>>>> <http://lk.linkedin.com/in/suhothayan>* >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> >>>>> >>>>> *Thanks & Regards,Sachini JayasekaraSoftware Engineer; **WSO2 Inc. * >>>>> >>>>> *lean . enterprise . middleware | http://wso2.com <http://wso2.com> * >>>>> >>>>> Mobile : +94712371165 >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> *S. Suhothayan* >>>> Technical Lead & Team Lead of WSO2 Complex Event Processor >>>> *WSO2 Inc. *http://wso2.com >>>> * <http://wso2.com/>* >>>> lean . enterprise . middleware >>>> >>>> >>>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >>>> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >>>> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >>>> http://lk.linkedin.com/in/suhothayan >>>> <http://lk.linkedin.com/in/suhothayan>* >>>> >>> >>> >> >> >> -- >> >> *S. Suhothayan* >> Technical Lead & Team Lead of WSO2 Complex Event Processor >> *WSO2 Inc. *http://wso2.com >> * <http://wso2.com/>* >> lean . enterprise . middleware >> >> >> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog: >> http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: >> http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: >> http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>* >> > > -- *S. Suhothayan* Technical Lead & Team Lead of WSO2 Complex Event Processor *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ <http://suhothayan.blogspot.com/>twitter: http://twitter.com/suhothayan <http://twitter.com/suhothayan> | linked-in: http://lk.linkedin.com/in/suhothayan <http://lk.linkedin.com/in/suhothayan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
