Re: [Architecture] [PET] Support UniqueBatchWindow(Time, Length) for Siddhi

Hi All, In current UniqueLengthBatchWindow i return the unique events from each Length of events(case 1) but there is another possiblity in the implementation that return the length number of unique events(case 2) from the events. Which one is the right one? please advice on this (we can add

Re: [Architecture] NextGen Tooling - Tool Palette

On Wed, Aug 31, 2016 at 9:31 AM, Chathura Ekanayake wrote: > Hi Susinda / Imesh, > > If positioning information is not stored with the diagram, does it auto > adjust size and positioning of elements based on the length of text > provided as lifeline labels and text on lines

Re: [Architecture] NextGen Tooling - Tool Palette

Hi Susinda / Imesh, If positioning information is not stored with the diagram, does it auto adjust size and positioning of elements based on the length of text provided as lifeline labels and text on lines connecting lifelines? Further, are we allowing users to change the order of lifelines? I

Re: [Architecture] DB event listener for ESB

One hybrid solution would be to have db triggers adding records to a single "monitor" table in which a polling inbound endpoint can periodically look check for changes [1]. Based on the new records, the consequent sequence can decide which actions to execute. [1] -

Re: [Architecture] NextGen Tooling - Tool Palette

Hi Imesh +1 for all other suggestions and comments Multiple groups added only to demonstrate the tool-palette features, not needed for this editor but may be useful for datamapper editor. We need to finalize the icons for the various tools/actions - Hope ESb team can give some input We will have

Re: [Architecture] NextGen Tooling - Tool Palette

Great work Susinda! Few comments below: - I think initially we may not need multiple groups inside the tool palette for sequence diagramming module. - Maybe we can directly use the exact tool palette elements we need; Lifecycles, Mediators, and Arrows. - The term Tool used at

Re: [Architecture] DB event listener for ESB

Hi Malaka, If it is done using triggers, it can be done without us doing anything. I assume trigger can hit a URL in the ESB that trigger processing. Adding a DB listener as an inbound endpoint is OK. I suggest we only do DB listener. --Srinath On Tue, Aug 30, 2016 at 3:13 PM, Malaka Silva

[Architecture] DB event listener for ESB

Hi, ​There are requirements to ​do additional operations when there are changes done to organization data. One way to do this is to create triggers at database level. However there are limitations on actions users can perform using triggers. So if we implement custom inbound endpoint we can

Re: [Architecture] Introduce API Product concept for WSO2 API Manager

Alternatively we could use the term 'API Package' (analogous to a mobile service provider package) to define a group of APIs with their own set of policies. On 30 August 2016 at 13:12, Imesh Gunaratne wrote: > Thanks, Uvindra! I can only see this concept being used at [1]. Do

Re: [Architecture] Introduce API Product concept for WSO2 API Manager

Thanks, Uvindra! I can only see this concept being used at [1]. Do you have any other references? Still, I don't think the product term is well suited for grouping APIs. [1] http://docs.apigee.com/developer-services/content/what-api-product On Tue, Aug 30, 2016 at 11:52 AM, Uvindra Dias

Re: [Architecture] NextGen Tooling - Tool Palette

The same webpage can be seen at here[1] [1] - https://wso2-incubator.github.io/js-tooling-framework/sequence-editor/index.html Thanks Susinda On Tue, Aug 30, 2016 at 11:34 AM, Susinda Perera wrote: > Hi All > > I have started implementing $subject. Figure[1] below is the

Re: [Architecture] OpenID Connect Based SSO valve for WSO2 AS 6.0.0

Ok, so making this a general agent with well defined API's could solve this. We can then write a valve or a filter using this library. We will go ahead with the valve now and later we can include a filter also. @Abilashini, shall we first come up with the API's for this? The requirement here is

Re: [Architecture] [APIM] Modifying test cases to use new REST APIs instead of old Jaggery REST APIs

+1 to what Jo suggested, I have written some classes to already do this but haven't committed the code. @Malintha and Praminda, you can reuse these if you wish. On 29 August 2016 at 12:00, Joseph Fonseka wrote: > How about having the OAuth flow transparent to the test case

[Architecture] NextGen Tooling - Tool Palette

Hi All I have started implementing $subject. Figure[1] below is the screenshot of the current implementation. The implementation pf Tool palette is devided to following models and views (considering extendability) and the js code[2] describes the connectivity of the modules. ToolPalette /