Re: [Architecture] [Analytics Dashboards] Configuring the visibility of the widget title bar

Hi all, I am also +1 for the second approach. Drawbacks with this approach > >- > >In the approach one, golden layout will take care of hiding the title >header using its ItemConfig options [1]. So supporting other itemConfigs in >future will be straightforward. But in this

[Architecture] [Announce] WSO2 Stream Processor 4.2.0 Released!

*WSO2 Stream Processor 4.2.0 Released!WSO2 Stream Processor team is pleased to announce the release of version 4.2.0 of the WSO2 Stream Processor.WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics platform, of which the real-time, incremental & intelligent data processing

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.2.0 RC2

ave tested the following functionality and found no issues. >> >>- Drag and drop function - From Design to Code view >> >> [+] Stable - go ahead and release >> >> Best Regards, >> Moiz. >> >> >> On Mon, Jun 25, 2018 at 3:31 PM Nis

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.2.0 RC2

>>>>>> On Thu, Jun 21, 2018 at 12:22 PM, Senthuran Ambalavanar < >>>>>>> senthu...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> I have tested the f

[Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.2.0 RC2

Hi all, WSO2 Stream Processor team is pleased to announce the second release candidate of WSO2 Stream Processor 4.2.0. WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics platform, of which the real-time, incremental & intelligent data processing capabilities let digital

Re: [Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.2.0 RC1

Hi all, We are calling off this vote as we found some issues with the rc1. We will do a rc2 and call the vote. Thanks, Nisala On Sat, Jun 16, 2018 at 12:24 PM Nisala Nanayakkara wrote: > Hi all, > > WSO2 Stream Processor team is pleased to announce the first release > candidate of

[Architecture] [Dev] [VOTE] Release of WSO2 Stream Processor 4.2.0 RC1

Hi all, WSO2 Stream Processor team is pleased to announce the first release candidate of WSO2 Stream Processor 4.2.0. *WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics platform, of which the real-time, incremental & intelligent data processing capabilities let digital

[Architecture] [Dev] WSO2 Stream Processor 4.2.0 Beta Released !

*WSO2 Stream Processor 4.2.0 Beta Released!WSO2 Stream Processor team is pleased to announce the release of version 4.2.0 Beta of the WSO2 Stream Processor.WSO2 Stream Processor is an open source embodiment of the WSO2 Analytics platform, of which the real-time, incremental & intelligent data

Re: [Architecture] [Dev] [VOTE] Release WSO2 Stream Processor 4.1.0 RC2

Tested Dashboard App and its basic functionalities. Tested the Status Dashboard. (Adding worker and etc) [+] Stable go ahead and release Thanks, Nisala On Fri, Mar 16, 2018 at 10:21 AM, Anusha Jayasundara wrote: > Tested business rules, template editor, event simulator with

[Architecture] [Dashboard] Message queuing mechanism to prevent losing messages in PubSub

Hi All, Purpose of this mail is to discuss the solution regarding the 'Message queuing mechanism to prevent losing messages in PubSub"*. *Please find the below information in order to get more context regarding the $subject *.* *Problem & C4 solution* Let's consider a situation where there is a

Re: [Architecture] Introducing interface to get widget configuration files in Dashboard Component

to a separate module. So that people can understand the flow very well and define their own implementation by following above mentioned sample. If you any concerns, please feel free to ask. Thanks, Nisala On Fri, Jan 20, 2017 at 12:18 PM, Nisala Nanayakkara <nis...@wso2.com> wrote: > Hi, &

Re: [Architecture] C5 Modifying OSGi bundle deployment logic to support temporary patches (log patches, etc)

Hi Jayanga, +1 for maintaining separate directory for log, pre-QA patches/updates with a proper name. I assume that the pre-QA patches/updates are still valid in C5. So names such as "information-collector" or "log-collector" will not be an option. Because this directory will not only contains

Re: [Architecture] Introducing interface to get widget configuration files in Dashboard Component

gt; Regards > Suho > > On Wed, Jan 18, 2017 at 10:39 AM, Nisala Nanayakkara <nis...@wso2.com> > wrote: > >> Hi, >> >> @CEP team : Appreciate your response about this matter. >> >> Thanks, >> Nisala >> >> On Mon, Jan 16, 2017 at 2

Re: [Architecture] Introducing interface to get widget configuration files in Dashboard Component

Hi, @CEP team : Appreciate your response about this matter. Thanks, Nisala On Mon, Jan 16, 2017 at 2:14 PM, Nisala Nanayakkara <nis...@wso2.com> wrote: > Hi All, > > According to the off-line discussion that we had with Suho, Chandana, > Kishanthan, Udara, Tanya and Tharik o

[Architecture] [Dev] Dashboards (UUF component) 3.0.0-M2 Released

Hi All, We are pleased to announce the 2nd milestone release of Dashboard components, which is based on the WSO2 Carbon Unified Framework(UUF). Features: - Integrated Metadata APIs - Introduced H2 DB support for storing Dashboards - Dashboard Personalization You can use following maven

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

y when all the carbon products move to AS 6.0 based >> platform, we can merge all those into one. >> >> Thanks, >> Sinthuja. >> >> On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara <nis...@wso2.com> >> wrote: >> >>> Hi Kasun, >

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

when running Jaggery apps in vanilla Tomcat/AS6? > > How are you going to manage the codebase for Carbon vs Tomcat Jaggery > support? Better if we can maintain it in the same place. > > On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara <nis...@wso2.com> > wrote: > >>

Re: [Architecture] Access Level Model For WSO2 Dashboard Server

Hi Megala, Yes.we can do it. +1 for the change. Thanks, Nisala On Sun, Jun 12, 2016 at 11:49 PM, Nisala Nanayakkara <nis...@wso2.com> wrote: > Hi Udara, > > Main purpose of separating editing dashboard and changing dashboard > settings, is to give only dashboa

Re: [Architecture] Access Level Model For WSO2 Dashboard Server

> > Mobile: +94766405580 <%2B94766405580> > lean . enterprise . middleware > > > On Sat, Jun 11, 2016 at 7:20 PM, Megala Uthayakumar <meg...@wso2.com> > wrote: > >> Hi Nisala, >> >> Shall we create global level permissions for gadget/layout upload an

Re: [Architecture] Access Level Model For WSO2 Dashboard Server

Hi Sinthuja, Thanks for the feedback. I will proceed with implementation. Thanks, Nisala On Thu, Jun 9, 2016 at 4:26 PM, Sinthuja Ragendran <sinth...@wso2.com> wrote: > Hi Nisala, > > On Thu, Jun 9, 2016 at 8:13 AM, Nisala Nanayakkara <nis...@wso2.com> >

Re: [Architecture] Access Level Model For WSO2 Dashboard Server

t;> 4 * N number of internal roles. >> >> @ IS team : is this approach fine? Or is there any better approach? >> >> Thanks, >> Tanya >> >> On Mon, Jun 6, 2016 at 3:44 PM, Nisala Nanayakkara <nis...@wso2.com> >> wrote: >> >>> adding Johan and

Re: [Architecture] Access Level Model For WSO2 Dashboard Server

adding Johan and Manuranga Thanks, Nisala On Mon, Jun 6, 2016 at 3:41 PM, Nisala Nanayakkara <nis...@wso2.com> wrote: > Hi all, > > I am working on implementing an access levels model for WSO2 Dashboard > Server. Currently global permission model for create/delete/logi

[Architecture] Access Level Model For WSO2 Dashboard Server

Hi all, I am working on implementing an access levels model for WSO2 Dashboard Server. Currently global permission model for create/delete/login is implemented by Megala. Since it does not support to provide per dashboard level access for the users. I am going to extend it and implement a

[Architecture] Pre-populate API Manager with one API which can be used OOTB

I am working on the improvement of 'Pre-populating API Manager with one sample API in APIM'. The decided approach is create a simple API using inline implementation with script mediator in the server startup. For this,apim startup.publisher package will be re-used. There will be some changes in