Re: [Dev] [Architecture] WSO2 Message Broker 3.2.0 RC1 Released !!

[Sasikala Kottegoda]

Following test cases fail intermittently:

   -
   
org.wso2.mb.integration.tests.amqp.functional.AMQPSessionRecoverTestCase.performSessionRecoverWithAckTestCase
   

   -
   
org.wso2.mb.integration.tests.amqp.functional.AMQPSessionRecoverTestCase.performSessionRecoverWithoutAckTestCase
   

   -
   
org.wso2.mb.integration.tests.amqp.functional.dtx.DtxStartPositiveTestCase.xaStartJoinQueuePublishTestCase
   


Hence, we will need to release another RC.

Thank you,
Sasikala

On Sat, Apr 8, 2017 at 4:25 AM, Hasitha Hiranya  wrote:

> Hi Devs,
>
> This is the first release candidate of WSO2 Message Broker 3.2.0.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=13656
>
> Known Issues
> https://wso2.org/jira/issues/?filter=13655
>
>
> 
> Please download MB 3.2.0 RC1 and test the functionality and vote. The
> vote will be open for 72 hours or as needed.
>
> Source & binary distribution files:
> https://github.com/wso2/product-mb/releases/tag/v3.2.0-RC1
>
>
> The tag to be voted upon:
> https://github.com/wso2/product-mb/tree/release-3.2.0-RC1
> 
>
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (explain why)
>
> Thanks and Regards
>
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Sasikala Kottegoda
*Software Engineer*
WSO2 Inc., http://wso2.com/
lean. enterprise. middleware
Mobile: +94 774835928

[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC][Siddhi][CEP]: Siddhi Pattern for Absence of Events

[Gobinath]

Hi,

A prototype is implemented and available at [1]. Currently the query
support for absent patterns and two simple pattern identifications (e1 ->
not e2 and not e1 -> e2) are implemented. Please have a look at the unit
test [2] to get the idea. Class names and variable names are subject to
change (will finalize later). I am waiting for your feedback.


Thanks & Regards,
Gobinath


[1] https://github.com/lgobinath/siddhi/tree/feature-absent-event-pattern
[2]
https://github.com/lgobinath/siddhi/blob/feature-absent-event-pattern/modules/siddhi-core/src/test/java/org/wso2/siddhi/core/query/pattern/EveryAbsentPatternTestCase.java


On Fri, Mar 31, 2017 at 6:28 AM, Gobinath  wrote:

> Hi all,
>
> Thanks Suho for your feedback. I have made the changes based on your
> suggestions and submitted the final proposal. Started working on a
> prototype and will update you soon with the results.
>
>
> Thanks & Regards,
> Gobinath
>
> On Thu, Mar 30, 2017 at 12:28 PM, Sriskandarajah Suhothayan  > wrote:
>
>> I have given some feedback on the gsoc site.
>>
>> Suho
>>
>> On Mon, Mar 27, 2017 at 9:03 PM, Gobinath  wrote:
>>
>>> Hi all,
>>>
>>> Thanks. I have shared the draft of my proposal titled "Non-Occurrence of
>>> Events for Siddhi Patterns" with WSO2 through GSoC dashboard and requesting
>>> your feedback on this.
>>>
>>>
>>> Thanks & Regards,
>>> Gobinath
>>>
>>> On Wed, Mar 15, 2017 at 1:30 PM, Sriskandarajah Suhothayan <
>>> s...@wso2.com> wrote:
>>>
 Thanks for the GSoC idea, I hope this will be a good way to improve the
 Siddhi language and make it more powerfull.
 If time permits we can also add other use-cases of patterns & sequences
 and improve it further.

 Since you are still not a commuter I hope these contributions will help
 you be a committer to Siddhi as well :)
 I'll make this as a formal idea, do work on a proposal as well.

 Regards
 Suho


 On Wed, Mar 15, 2017 at 6:09 PM, Gobinath  wrote:

> Hi team,
>
> This is Gobinath a former software engineer at WSO2 currently doing
> masters at Western University. This time I plan to do GSoC with WSO2 and
> this is the basic idea of what I have discussed with Suho.
> Based on Suho's suggestion, I come up with a proposal to implement
> detecting non-occurring events using Siddhi patterns. The current Siddhi
> patterns allow identifying the patterns that present.
>
> See an example:
> from every e1=Stream1[price>20] -> e2=Stream2[price>e1.price] within 1
> sec
> select e1.symbol as symbol1, e2.symbol as symbol2
> insert into OutputStream;
>
> Detecting the absence of a pattern is not natively supported by Siddhi
> patterns for the moment. In other words, identifying event_a not followed
> by event_b within 2 minutes is not possible using the current patterns
> implementation (Note that a time frame is required otherwise we have to
> wait for infinite time to say event_b has not arrived). The current
> workaround [1] to detect non-delivered items is shown below:
>
> from arrivals_stream#window.time(2 minutes)
> select *
> insert expired events into overdue_deliveries_stream;
>
> from every arrivalEvent = arrivals_stream ->
> deliveryEvent = deliveries_stream[arrivalEvent.trackingId ==
> trackingId]
> or overdue_delivery = 
> overdue_deliveries_stream[arrivalEvent.trackingId
> == trackingId]
> select arrivalEvent.trackingId as trackingId,
> arrivalEvent.customerName as customerName, arrivalEvent.telephoneNo as
> telephoneNo, deliveryEvent.trackingId as deliveryId
> insert into filter_stream;
>
> from filter_stream [ (deliveryId is null)]
> select trackingId, customerName, telephoneNo
> insert into alert_stream;
>
> This solution requires a time window and it is inefficient if we are
> interested only on one occurrence of such a pattern (In other words same
> query without every keyword). Further, the query is more complex and not
> user-friendly.
>
> If we provide patterns to detect absence of patterns, the above query
> can be rewritten as below:
>
> from every arrivalEvent = arrivals_stream ->  (not
> deliveries_stream[arrivalEvent.trackingId == trackingId] within 2 min
> )
> select arrivalEvent.trackingId as trackingId,
> arrivalEvent.customerName as customerName, arrivalEvent.telephoneNo as
> telephoneNo
> insert into alert_stream;
>
> As you can see, we can use the existing language components like not &
> within. This can be achieved by extending the existing
> StreamPreStateProcessors and StreamPostStateProcessors with an internal
> timer so that they can expire their internal list of events based on the
> time limit. It is somewhat similar to time windows but the 

Re: [Dev] [APIM] Read only source view not allowed to edit single API

[Shazni Nazeer]

May be this is bug.

In addition despite you add the handler via source view or through file
system in API level, and then if you happen to update the API in publisher,
all custom handler (or any property) that you add get vanished as the API
gets updated, the new synapse file overwrite it. So you'll have to add it
once again. So wouldn't it be good if the handler is added to
velocity-tempate.xml file if the handler is applicable to all the API? But
if it's not the case, I'm npt sure how to handle it. is there a way to
handle it it easily without always have to re-edit the API synapse file?

On Sat, Apr 15, 2017 at 8:17 PM, Lakshman Udayakantha 
wrote:

> Hi Folks,
>
> I was trying to add a custom handler to a single API in API Manager.
> According to [1], we can edit the source view of API and add customer
> handler in handler section. Anyway, I can't do that in APIM 2.0.0 because
> source view is read-only. This can be done in earlier versions like 1.10.0.
> Any way we can edit API file from the file system and engage the handler.
> What is the reason for making ESB source view read only? If it should be
> read only then we have to update the documentation and point a way to add
> handlers for single API as well.
>
> [1] https://docs.wso2.com/display/AM200/Writing+Custom+Handlers
>
> --
> Lakshman Udayakantha
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
> Mobile: *0717429601*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Shazni Nazeer

Mob : +94 37331
LinkedIn : http://lk.linkedin.com/in/shazninazeer
Blog : http://shazninazeer.blogspot.com


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev