Re: [Dev] Communication Error between Active and Passive nodes.

[Nisala Nanayakkara]

Hi Mohan,

As discussed offline, I will do the improvement to print the error trace
here.

Thanks,
Nisala

On Mon, Sep 24, 2018 at 8:59 PM Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

> Hi Damith/Nisala,
>
> I think, we could improve the error handling bit more. Seems like we are
> not printing the error trace here. Shall we improve that?
>
> Thanks,
> Mohan
>
> On Fri, Sep 21, 2018 at 7:38 PM, Damith Wickramasinghe 
> wrote:
>
>> Hi vasanthan,
>>
>> It seems active node cannot create a tcp connection to passive node.
>> Please make sure above advertisedHost value should be the host of own node.
>> Not the host of other node.  If they are correct then try to telnet to
>> passive node {passive node host} 9893 from active node.  I think you may
>> need a host mapping too.
>>
>> Adding thilina since he did a same setup with new HA.
>>
>>
>> Regards,
>> Damith.
>>
>> On Fri, Sep 21, 2018 at 1:35 PM Vasanthan Sivalingam 
>> wrote:
>>
>>>
>>> Hi Sp team,
>>>
>>> With the latest 4.3.0 release an HA deployment was done with kubernetes.
>>> the deployment configurations has been done as [1] and [2]. It was noticed
>>> that the active node is not communicating with the passive node with the
>>> following logs.
>>>
>>> ...
>>> [2018-09-21 11:54:32,435]  INFO
>>> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
>>> Setting SinksHandlers of TestSiddhiApp to Active
>>> [2018-09-21 11:54:32,436]  INFO
>>> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
>>> Setting RecordTableHandlers of TestSiddhiApp to Active
>>> [2018-09-21 11:54:32,436]  INFO
>>> {org.wso2.carbon.stream.processor.core.internal.StreamProcessorService} -
>>> Siddhi App TestSiddhiApp deployed successfully
>>> [2018-09-21 11:54:32,446]  INFO
>>> {org.wso2.carbon.kernel.internal.CarbonStartupHandler} - WSO2 Stream
>>> Processor started in 6.922 sec
>>> [*2018-09-21 11:54:33,377] ERROR
>>> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
>>> Error in getting a connection to the Passive node. null*
>>> [2018-09-21 11:54:33,379] DEBUG
>>> {org.wso2.carbon.stream.processor.core.ha.HACoordinationSourceHandler} -
>>> Active Node: Saving state of Source Handler with Id TestSiddhiApp-1 with
>>> timestamp 0
>>> [2018-09-21 11:54:33,395] ERROR
>>> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
>>> Error in getting the TCP connection to the passive node. Hence not sending
>>> the control message to the passive node
>>> [2018-09-21 11:55:31,531]  INFO
>>> {org.wso2.carbon.stream.processor.core.persistence.PersistenceManager} -
>>> siddhi Apps are persisted successfully.
>>> ...
>>>
>>> The deployment config was done as below,
>>>
>>> deployment.config:
>>>   type: ha
>>>   eventSyncServer:
>>> host: localhost
>>> port: 9893
>>> advertisedHost: sp-ha-node-1
>>> advertisedPort: 9893
>>> bossThreads: 10
>>> workerThreads: 10
>>>   eventSyncClientPool:
>>> maxActive: 10
>>> maxTotal: 10
>>> maxIdle: 10
>>> maxWait: 6
>>> minEvictableIdleTimeMillis: 12
>>>
>>> Attached the log file.
>>> Can you please suggest a method to make this communication work between
>>> active node and the passive node.
>>>
>>> [1]
>>> https://github.com/sameerawickramasekara/product-sp/blob/master/modules/integration/tests-kubernetes-integration/src/test/resources/artifacts/docker-files/deployment-ha-node-1.yaml
>>> [2]
>>> https://github.com/sameerawickramasekara/product-sp/blob/master/modules/integration/tests-kubernetes-integration/src/test/resources/artifacts/docker-files/deployment-ha-node-2.yaml
>>>
>>> Thanks,
>>> Vasanth
>>>
>>
>>
>> --
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> 
>> lean.enterprise.middleware
>>
>> mobile: *+94728671315*
>>
>>
>
>
> --
> *V. Mohanadarshan*
> *Technical Lead,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: mo...@wso2.com
> phone:(+94) 771117673
>


-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

*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
capabilities let digital businesses create actionable business insights and
data products.You can download this distribution from
https://wso2.com/analytics/install
Online documentation is available at
https://docs.wso2.com/display/SP420/Stream+Processor+Documentation
.How to
Run1. Extract the downloaded zip. 2. Navigate to the /bin
directory ( is the extracted directory).3. Issue one of the
following commands to start the preferred runtime as below,For WSO2 Stream
Processor Studio, - For Windows: editor.bat- For Linux: ./editor.shFor WSO2
Stream Processor Worker Runtime, - For Windows: worker.bat- For Linux:
./worker.shFor WSO2 Stream Processor Manager Runtime, - For Windows:
manager.bat- For Linux: ./manager.shFor WSO2 Stream Processor Dashboard
Runtime, - For Windows: dashboard.bat- For Linux: ./dashboard.s*








*By default, the OSGi console starts with the server.New Features in this
Release - Siddhi App graphical designer in Editor- Siddhi incremental
snapshots - Distributed Monitoring Dashboard- HTTP Analytics Dashboard-
Widget generation wizard improvements to support publisher/subscriber use
cases- Distributed deployment improvements- Improve manager nodes with the
ability to be fronted through a Load Balancer- Improve allocation algorithm
to be based on resource availability- Improve rebalancing algorithm-
Support for all source transport typesPlease find the GitHub issues related
to these improvements and fixes here
Known
IssuesAll the open issues pertaining to WSO2 Stream Processor are reported
at the following location:Stream Processor Issues
How
You Can ContributeMailing ListsJoin our mailing list and correspond with
the developers directly.Developer list : dev@wso2.org  |
Subscribe | Mail Archive User forum
: StackOverflow
Reporting IssuesWe
encourage you to report issues, documentation faults, and feature requests
regarding WSO2 Stream Processor through the public Stream Processor Git
Repo .SupportWe are committed to
ensure your enterprise middleware deployment is completely supported from
evaluation to production. Our unique approach ensures that all support
leverages our open development methodology and is provided by the very same
engineers who build the technology. For more details and to take advantage
of this unique opportunity, visit http://wso2.com/support/
For more information about WSO2 Stream Processor,
please see https://wso2.com/analytics  or visit
the WSO2 Oxygen Tank developer portal for additional resources.Thank you
for your interest in WSO2 Stream Processor.-The WSO2 Stream Processor Team-*

-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [SP] What is our dashboard packaging modal

[Nisala Nanayakkara]

Hi Udara,

Currently, we keep the widgets in the file system and the dashboard JSONs
in the database. So we have to copy/paste the widgets into the file system
and create a DB entry with the dashboard JSON using our REST API.

But AFAIK your requirement is to support dashboard packaging in the build
time. Since we do not have the control over the DB at the build time. We
need to think about an alternative way of achieving your requirement.

@Lasantha Samarakoon  Shall we provide a file system
location to keep the predefined dashboard JSONs? So that we can get an
aggregated value of file system dashboard JSONs and DB dashboard JSONs to
show it in dashboard listing page. WDYT?

Thanks,
Nisala

On Mon, Jul 9, 2018 at 9:48 PM Udara Rathnayake  wrote:

> Similar to what we had earlier in DS do we have an option to package a
> dashboard?
>
> My requirement is to design/develop a custom dashboard with all
> dependencies then deploy in SP programmatically along with a streaming app.
> ​
>
> --
> Regards,
> UdaraR 
>


-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Connect to a RDMBS datastore to retrieve data for a SP dashboard widget

[Nisala Nanayakkara]

Hi,

@Nivethika: +1 for documenting it.
@ Thisaru: If you are using a previous version of SP such as 4.0.0,4.1.0 or
4.2.0-rc1, Please upgrade it to SP 4.2.0-rc2 which is treated as the GA. So
you can use the latest artefacts such as base-widget which will simplify
the widget development.

Thanks,
Nisala

On Mon, Jul 9, 2018 at 11:52 AM Niveathika Rajendran 
wrote:

> Hi Nisala,
>
> Thank you for the explanation, as we have not documented the depended base
> widget version, I thought they should be compatible with all versions of SP.
>
> How about adding a note in SP creating custom widget documentation about
> depended base widget version?
> SP 4.2.0 -> @wso2-dashboards/widget: 1.2.2
> SP 4.1.0 -> @wso2-dashboards/widget: 1.1.0
> SP 4.0.0 -> @wso2-dashboards/widget: 1.1.0
>
> Best Regards,
> *Niveathika Rajendran,*
> *Software Engineer.*
> *Mobile : +94 077 903 7536*
>
>
>
>
>
> On Mon, Jul 9, 2018 at 12:48 AM Nisala Nanayakkara 
> wrote:
>
>> Hi Nivethika,
>>
>> @Damith What Thisaru means is that custom widgets(with a dependency of
>> @wso2-dashboards/widgets:1.2.2) are not backward compatible. It only works
>> in SP 4.2.0
>>
>> AFAIK older widgets which are built for SP 4.0.0/4.1.0, work with SP
>> 4.2.0 release. So the widgets' backward compatibility is preserved. Can you
>> please clarify a bit more about this? As you mentioned earlier,
>> wso2-dashboards/widgets only work with SP 4.2.0 release. Moreover, I think
>> that although there is a requirement to support older widgets with 4.2.0
>> release version, there is no use-case to support widgets which are built
>> for SP 4.2.0 to work with older versions such as SP 4.0.0/4.1.0.
>>
>> Thanks,
>> Nisala
>>
>> On Fri, Jul 6, 2018 at 8:41 PM Niveathika Rajendran 
>> wrote:
>>
>>> @Damith What Thisaru means is that custom widgets(with a dependency of
>>> @wso2-dashboards/widgets:1.2.2) are not backward compatible. It only works
>>> in SP 4.2.0 (SP-4.2.0-rc2 is the successful release candidate, we still
>>> waiting on quarterly release announcement to change the tags). This issue
>>> is only for the getWidgetChannelManager API, other functionalities are
>>> backward compatible. Users essentially need not use the
>>> widgetChannelManager API, as they can create the WebSocket connection
>>> within the custom widget.
>>>
>>> @Nisala & @Lasantha: This is due to a fix made in the latest version, to
>>> reuse WidgetChannelManager passed from the portal app[1]. This makes the
>>> base widget lib dependant upon the portal app. How about a fix such that
>>> base widget will reuse the WidgetChannelManager if passed from the portal
>>> app or will create a new instance of WidgetChannelManger? WDYT?
>>>
>>> [1]
>>> https://github.com/wso2/carbon-dashboards/blob/master/base-widget/src/Widget.jsx#L39
>>>
>>> Best Regards,
>>> *Niveathika Rajendran,*
>>> *Software Engineer.*
>>> *Mobile : +94 077 903 7536*
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jul 6, 2018 at 6:46 PM Damith Wickramasinghe 
>>> wrote:
>>>
>>>> Hi Thisaru,
>>>>
>>>> First thing is we need to use SP 4.2.0-rc2 version in order to use
>>>>> WidgetChannelManager. Otherwise the communication channel will fail
>>>>>
>>>>
>>>> Do u mean in 4.2.0 released version this does not work ?
>>>>
>>>> On Fri, Jul 6, 2018 at 12:47 PM, Thisaru Guruge 
>>>> wrote:
>>>>
>>>>> Hi Nivethika,
>>>>>
>>>>> Thanks for the immense support you gave, Now I am able to create the
>>>>> widget.
>>>>>
>>>>> There were some issues I faced when creating the widget, and thought
>>>>> to share them, and how I resolved them.
>>>>>
>>>>> - First thing is we need to use SP 4.2.0-rc2 version in order to use
>>>>> WidgetChannelManager. Otherwise the communication channel will fail
>>>>> - Next thing is to define the datastore in the widgetConf.json file.
>>>>> In the existing solutions in the GitHub does not have such data.
>>>>>   But after the discussion with Nivethika got to know that we should
>>>>> provide datastore name using "datasourceName": ""
>>>>> under the providerConfig -> config in the widgetConf.json file.
>>>>>
>>>>> Thank you again for the help given i

Re: [Dev] Connect to a RDMBS datastore to retrieve data for a SP dashboard widget

[Nisala Nanayakkara]

Hi Nivethika,

@Damith What Thisaru means is that custom widgets(with a dependency of
@wso2-dashboards/widgets:1.2.2) are not backward compatible. It only works
in SP 4.2.0

AFAIK older widgets which are built for SP 4.0.0/4.1.0, work with SP 4.2.0
release. So the widgets' backward compatibility is preserved. Can you
please clarify a bit more about this? As you mentioned earlier,
wso2-dashboards/widgets only work with SP 4.2.0 release. Moreover, I think
that although there is a requirement to support older widgets with 4.2.0
release version, there is no use-case to support widgets which are built
for SP 4.2.0 to work with older versions such as SP 4.0.0/4.1.0.

Thanks,
Nisala

On Fri, Jul 6, 2018 at 8:41 PM Niveathika Rajendran 
wrote:

> @Damith What Thisaru means is that custom widgets(with a dependency of
> @wso2-dashboards/widgets:1.2.2) are not backward compatible. It only works
> in SP 4.2.0 (SP-4.2.0-rc2 is the successful release candidate, we still
> waiting on quarterly release announcement to change the tags). This issue
> is only for the getWidgetChannelManager API, other functionalities are
> backward compatible. Users essentially need not use the
> widgetChannelManager API, as they can create the WebSocket connection
> within the custom widget.
>
> @Nisala & @Lasantha: This is due to a fix made in the latest version, to
> reuse WidgetChannelManager passed from the portal app[1]. This makes the
> base widget lib dependant upon the portal app. How about a fix such that
> base widget will reuse the WidgetChannelManager if passed from the portal
> app or will create a new instance of WidgetChannelManger? WDYT?
>
> [1]
> https://github.com/wso2/carbon-dashboards/blob/master/base-widget/src/Widget.jsx#L39
>
> Best Regards,
> *Niveathika Rajendran,*
> *Software Engineer.*
> *Mobile : +94 077 903 7536*
>
>
>
>
>
> On Fri, Jul 6, 2018 at 6:46 PM Damith Wickramasinghe 
> wrote:
>
>> Hi Thisaru,
>>
>> First thing is we need to use SP 4.2.0-rc2 version in order to use
>>> WidgetChannelManager. Otherwise the communication channel will fail
>>>
>>
>> Do u mean in 4.2.0 released version this does not work ?
>>
>> On Fri, Jul 6, 2018 at 12:47 PM, Thisaru Guruge  wrote:
>>
>>> Hi Nivethika,
>>>
>>> Thanks for the immense support you gave, Now I am able to create the
>>> widget.
>>>
>>> There were some issues I faced when creating the widget, and thought to
>>> share them, and how I resolved them.
>>>
>>> - First thing is we need to use SP 4.2.0-rc2 version in order to use
>>> WidgetChannelManager. Otherwise the communication channel will fail
>>> - Next thing is to define the datastore in the widgetConf.json file. In
>>> the existing solutions in the GitHub does not have such data.
>>>   But after the discussion with Nivethika got to know that we should
>>> provide datastore name using "datasourceName": ""
>>> under the providerConfig -> config in the widgetConf.json file.
>>>
>>> Thank you again for the help given in resolving the issues I had.
>>>
>>> On Thu, Jul 5, 2018 at 4:05 PM Niveathika Rajendran 
>>> wrote:
>>>
>>>> Hi Thirasu,
>>>>
>>>> The above information is still not added to the docs.
>>>>
>>>> The functionality behind this is to create a WebSocket connection to
>>>> the data-provider endpoint with a required configuration. The
>>>> documentation @Sajith pointed out has the details on various data provider
>>>> endpoints and the configurations.
>>>>
>>>> You have to do the following steps,
>>>> 1. Access data provider configurations in widgetConf.json file [1]
>>>> 2. Use the base widget API to create WebSocket connection. For this,
>>>> you can use the following APIs,
>>>>
>>>>- Subscribe to the endpoint:
>>>>   - syntax :
>>>>   super.getWidgetChannelManager().subscribeWidget(, >>> back
>>>>   method to handle data>, )
>>>>   - Example:
>>>>   -
>>>>
>>>>   super.getWidgetChannelManager()
>>>>   .subscribeWidget(this.props.id, this.handleDataReceived, 
>>>> dataProviderConfigs));
>>>>
>>>>
>>>>
>>>>- Unsubscribe to the endpoint
>>>>   - syntax: super.getWidgetChannelManager().unsubscribeWidget(>>>   ID>);
>>>>   - Example:
>>>>   -
>>>>
>>>>   su

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

[Nisala Nanayakkara]

Hi all,

Thanks for testing WSO2 Stream Processor 4.2.0 RC2.

Since this vote passed with 13 [+1]s and 0 [-1]s, we’re hereby closing this
vote and proceeding with WSO2 Stream Processor 4.2.0 release.

Thanks,
Nisala

On Mon, Jun 25, 2018 at 5:38 PM Sajith Ravindra  wrote:

> Hi all,
>
> I have tested,
>
> - Editor designer view, stream/feed simulation
> - Business rule editor and template editor
> - HTTP analytics dashboard
> - Tracing
>
> [+] - Stable - go ahead and release.
>
> Thanks
> *,Sajith Ravindra*
> Associate Technical Lead
> 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 Mon, Jun 25, 2018 at 4:59 PM, Moiz Mansoor  wrote:
>
>> Hi All,
>>
>> I have 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 Nisala Nanayakkara 
>> wrote:
>>
>>> Hi all,
>>>
>>> I have tested the following functionality and found no issues.
>>>
>>>- Dashboard creation/deletion/modification
>>>- Creating widgets with Dynamic queries
>>>- Tested the editor samples
>>>- Tested the HA setup with DB & File persistence
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Fri, Jun 22, 2018 at 12:32 PM Raveen Rathnayake 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I have tested the following functionality and found no issues.
>>>>
>>>>- Siddhi Editor basic functions
>>>>- Drag and drop function - From Design to Code view
>>>>
>>>> [+] Stable - go ahead and release
>>>>
>>>> Thanks,
>>>> Raveen.
>>>>
>>>> On Fri, Jun 22, 2018 at 10:57 AM Maduranga Siriwardena <
>>>> madura...@wso2.com> wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> I have tested the following functionality,
>>>>>
>>>>>- HTTP source (with/without authentication, with/without ssl)
>>>>>- HTTP request source and response sink (with/without
>>>>>authentication, with/without ssl)
>>>>>- Custom json mapping with json path and trp properties
>>>>>
>>>>> [+] Stable - go ahead and release
>>>>>
>>>>> Thanks,
>>>>> Maduranga.
>>>>>
>>>>>
>>>>> On Fri, Jun 22, 2018 at 9:23 AM Charuka Karunanayake 
>>>>> wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I tested the following
>>>>>>
>>>>>>- Widget generation wizard with Websocket provider
>>>>>>- Dashboard Designer and Viewer
>>>>>>- Mongo DB sample with Mongo db v3.6.5
>>>>>>- Websocket Sink
>>>>>>
>>>>>> [+] Stable - go ahead and release
>>>>>>
>>>>>> Regards,
>>>>>> Charuka
>>>>>>
>>>>>> On Fri, Jun 22, 2018 at 12:48 AM Ramindu De Silva 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I tested the following
>>>>>>>
>>>>>>>- Event simulator - Regular, CSV, Database
>>>>>>>- Dashboard
>>>>>>>- Template Manager
>>>>>>>- Kafka Source and Sink (Hello Kafka Sample) with Kafka version,
>>>>>>>0.11 and 1.1.0
>>>>>>>
>>>>>>> [+] Stable - go ahead and release
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Ramindu.
>>>>>>>
>>>>>>> On Thu, Jun 21, 2018 at 8:12 PM, Chiran Fernando 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I have  tested Fully Distributed Deployment functionality locally
>>>>>>>> and on kubernetes.
>>>>>>>>
>>>>>>>> [+] Stable - go ahead and relea

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

[Nisala Nanayakkara]

Hi all,

I have tested the following functionality and found no issues.

   - Dashboard creation/deletion/modification
   - Creating widgets with Dynamic queries
   - Tested the editor samples
   - Tested the HA setup with DB & File persistence

[+] Stable - go ahead and release

Thanks,
Nisala

On Fri, Jun 22, 2018 at 12:32 PM Raveen Rathnayake  wrote:

> Hi all,
>
> I have tested the following functionality and found no issues.
>
>- Siddhi Editor basic functions
>- Drag and drop function - From Design to Code view
>
> [+] Stable - go ahead and release
>
> Thanks,
> Raveen.
>
> On Fri, Jun 22, 2018 at 10:57 AM Maduranga Siriwardena 
> wrote:
>
>> Hi All,
>>
>> I have tested the following functionality,
>>
>>- HTTP source (with/without authentication, with/without ssl)
>>- HTTP request source and response sink (with/without authentication, 
>> with/without
>>ssl)
>>- Custom json mapping with json path and trp properties
>>
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Maduranga.
>>
>>
>> On Fri, Jun 22, 2018 at 9:23 AM Charuka Karunanayake 
>> wrote:
>>
>>> Hi all,
>>>
>>> I tested the following
>>>
>>>- Widget generation wizard with Websocket provider
>>>- Dashboard Designer and Viewer
>>>- Mongo DB sample with Mongo db v3.6.5
>>>- Websocket Sink
>>>
>>> [+] Stable - go ahead and release
>>>
>>> Regards,
>>> Charuka
>>>
>>> On Fri, Jun 22, 2018 at 12:48 AM Ramindu De Silva 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I tested the following
>>>>
>>>>- Event simulator - Regular, CSV, Database
>>>>- Dashboard
>>>>- Template Manager
>>>>- Kafka Source and Sink (Hello Kafka Sample) with Kafka version,
>>>>0.11 and 1.1.0
>>>>
>>>> [+] Stable - go ahead and release
>>>>
>>>> Best Regards,
>>>> Ramindu.
>>>>
>>>> On Thu, Jun 21, 2018 at 8:12 PM, Chiran Fernando 
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I have  tested Fully Distributed Deployment functionality locally and
>>>>> on kubernetes.
>>>>>
>>>>> [+] Stable - go ahead and release
>>>>>
>>>>> On Thu, Jun 21, 2018 at 5:00 PM Eranga Liyanage 
>>>>> wrote:
>>>>>
>>>>>> Hi All
>>>>>>
>>>>>> I have tested the basic functionality of the following on Windows 10.
>>>>>>
>>>>>>- Editor simulator/debug/drag & drop
>>>>>>- Dashboard
>>>>>>- Portal
>>>>>>
>>>>>> [+] Stable - go ahead and release
>>>>>>
>>>>>> Best regards
>>>>>> Eranga
>>>>>>
>>>>>> On Thu, Jun 21, 2018 at 2:43 PM Gowthamy Vaseekaran <
>>>>>> gowth...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> I have tested the following and found no issues,
>>>>>>>
>>>>>>>1. Monitoring Dashboard
>>>>>>>   1. Distributed Deployment
>>>>>>>   2. Single Node Deployment
>>>>>>>   3. HA Deployment
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> [+] Stable - go ahead and release
>>>>>>>
>>>>>>> Regards,
>>>>>>> Gowthamy
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Jun 21, 2018 at 12:22 PM, Senthuran Ambalavanar <
>>>>>>> senthu...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I have tested the following, and have not found any issues.
>>>>>>>> 1. Business Rules Manager
>>>>>>>> 2. Siddhi Drag & Drop Editor - Code to Design view
>>>>>>>> 3. Widgets Generation Wizard - Creating a widget with RDBMS Batch
>>>>>>>> Data Provider
>>>>>>>>
>>>>>>>> [+] Stable - go ahead and release
>>>>>>>>
>>>>>

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

[Nisala Nanayakkara]

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 businesses create actionable business insights and
data products.

Please find the improvements and fixes related to this release here

.

You can find the source and distribution here


The tag to be voted upon:
https://github.com/wso2/product-sp/releases/tag/v4.2.0-rc2

Please download, test the product and vote.

[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

Thanks,
*- WSO2 Stream Processor Team -*


-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

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 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 businesses create actionable business insights and
> data products.*
>
> Please find the improvements and fixes related to this release here
> <https://github.com/wso2/product-sp/issues?page=1=is%3Aissue+closed%3A2018-03-16..2018-06-15=%E2%9C%93>
> .
>
> You can find the source and distribution here
> <https://github.com/wso2/product-sp/releases/tag/v4.2.0-rc1>
>
> The tag to be voted upon:
> https://github.com/wso2/product-sp/tree/v4.2.0-rc1
> <https://github.com/wso2/analytics-apim/releases/tag/v2.5.0-rc1>
> Please download, test the product and vote.
>
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> *- WSO2 Stream Processor Team -*
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Senior Software Engineer
> Mobile | +94 717600022
> WSO2 Inc | http://wso2.com/
>


-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

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 businesses create actionable business insights and
data products.*

Please find the improvements and fixes related to this release here

.

You can find the source and distribution here


The tag to be voted upon: https://github.com/wso2/product-sp/tree/v4.2.0-rc1

Please download, test the product and vote.

[+] Stable - go ahead and release
[-] Broken - do not release (explain why)

Thanks,
*- WSO2 Stream Processor Team -*


-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

*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
processing capabilities let digital businesses create actionable business
insights and data products.You can download the distribution from here

New
Features / Improvements in the Release*

   - Siddhi App graphical designer in Editor
   - Siddhi incremental snapshots
   - Distributed Monitoring Dashboard
   - HTTP Analytics Dashboard
   - Support for Redis Store
   - Widget generation wizard improvements to support publisher/subscriber
   use cases
   - Distributed deployment improvements
  - Improve manager nodes with the ability to be fronted through a Load
  Balancer
  - Improve allocation algorithm to be based on resource availability
  - Improve rebalancing algorithm
  - Support for all source transport types

Please find the GitHub issues related to these improvements and fixes here





*Known IssuesAll the open issues pertaining to WSO2 Stream Processor are
reported at the following location:Stream Processor Issues
How You Can ContributeMailing
ListsJoin our mailing list and correspond with the developers
directly.Developer list: dev@wso2.org  | Subscribe | Mail
Archive User forum: StackOverflow
Reporting IssuesWe
encourage you to report issues, documentation faults and feature requests
regarding WSO2 Stream Processor or in the Carbon base framework through the
public WSO2 Stream Processor JIRA.SupportWe are committed to ensure your
enterprise middleware deployment is completely supported from evaluation to
production. Our unique approach ensures that all support leverages our open
development methodology and is provided by the very same engineers who
build the technology. For more details and to take advantage of this unique
opportunity, visit http://wso2.com/support/ For
more information about WSO2 Stream Processor, please see
https://wso2.com/analytics  or visit the WSO2
Oxygen Tank developer portal for additional resources.Thank you for your
interest in WSO2 Stream Processor.- The WSO2 Stream Processor Team -*

-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Stream Processor 4.2.0 Alpha Released!

[Nisala Nanayakkara]

*WSO2 Stream Processor 4.2.0 Alpha Released!WSO2 Stream Processor team is
pleased to announce the release of version 4.2.0 Alpha 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 capabilities let digital businesses create actionable business
insights and data products.You can download this distribution from
https://github.com/wso2/product-sp/releases/download/v4.2.0-alpha/wso2sp-4.2.0-alpha.zip

New Features in this Release*

   - Siddhi incremental snapshots support
   - Editor with drag and drop design support
   - Siddhi App graphical view in the editor
   - Distributed Monitoring Dashboard
   - HTTP Analytics Dashboard
   - Support for Redis Store




*Known IssuesAll the open issues pertaining to WSO2 Stream Processor are
reported at the following location:Stream Processor Issues
How You Can ContributeMailing
ListsJoin our mailing list and correspond with the developers
directly.Developer list : dev@wso2.org  | Subscribe | Mail
Archive User forum : StackOverflow
Reporting IssuesWe
encourage you to report issues, documentation faults and feature requests
regarding WSO2 Stream Processor or in the Carbon base framework through the
public WSO2 Stream Processor JIRA.SupportWe are committed to ensure your
enterprise middleware deployment is completely supported from evaluation to
production. Our unique approach ensures that all support leverages our open
development methodology and is provided by the very same engineers who
build the technology. For more details and to take advantage of this unique
opportunity, visit http://wso2.com/support/ For
more information about WSO2 Stream Processor, please see
https://wso2.com/analytics  or visit the WSO2
Oxygen Tank developer portal for additional resources.Thank you for your
interest in WSO2 Stream Processor.-The WSO2 Stream Processor Team-*


-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

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
> single simulation and feed simulation.
>
> [+] Stable go ahead and release.
>
>
> On Fri, Mar 16, 2018 at 7:48 AM, Mathuriga Thavarajah 
> wrote:
>
>> Hi All,
>>
>> I have tested following,
>>
>>1. Quick Start Guide
>>2. Single Simulation
>>3. Feed Simulation using Random values (Primitive and Regex)
>>4. Feed Simulation using a CSV File.
>>5. Delete Siddhi Application.
>>
>> [+] Stable go ahead and release.
>>
>> Thanks.
>>
>> Regards,
>> Mathuriga
>>
>>
>> On Fri, Mar 16, 2018 at 4:38 AM, Sajith Ravindra 
>> wrote:
>>
>>> [-architecture-team, + architecture]
>>>
>>> Thanks
>>> *,Sajith Ravindra*
>>> Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 77 2273550
>>> blog: http://sajithr.blogspot.com/
>>> 
>>>
>>> On Fri, Mar 16, 2018 at 4:35 AM, Sajith Ravindra 
>>> wrote:
>>>
 Hi Devs,

 We are pleased to announce the release candidate of WSO2 Stream
 Processor 4.1.0.

 This is the Release Candidate version 2 of the WSO2 Stream Processor
 4.1.0.

 Please download, test the product and vote. The vote will be open for
 72 hours or as needed.

 *Known issues*: https://github.com/wso2/product-sp/issues
 
 *Source and binary distribution files*: https://github.com/wso2
 /product-sp/releases/tag/v4.1.0-RC2

 *The tag to be voted upon:* https://github.com/wso2/
 product-sp/tree/v4.1.0-RC2

 Please vote as follows.
 [+] Stable - go ahead and release
 [-] Broken - do not release (explain why)

 ~ The WSO2 Analytics Team ~

 Thanks
 *,Sajith Ravindra*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: +94 77 2273550
 blog: http://sajithr.blogspot.com/
 

>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> *Mathuriga Thavarajah*
>> Software Engineer
>> WSO2 Inc. - http ://wso2.com
>>
>> Email : mathur...@wso2.com
>> Mobile  : +94778191300 <+94%2077%20819%201300>
>>
>>
>>
>> *[image: http://wso2.com/signature] *
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Anusha Jayasundara*
> Software Engineer | WSO2
>
> Email : anus...@wso2.com
> Mobile : +94772601160 <+94%2077%20260%201160>
> Web : http://wso2.com
> Lean.Enterprise.Middleware
> 
>



-- 
*Nisala Niroshana Nanayakkara,*
Senior Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Avoid loading multiple copies of React

[Nisala Nanayakkara]

Hi Sajith,

We need to document this (putting React as an external dependency and using
> global.React). Is there any docs ATM?
>

No. We do not add this to document yet. We need to improve the documents
related "Creating Custom Widgets"[1] with this change.

[1] - https://docs.wso2.com/display/SP400/Creating+Custom+Widgets

Thanks,
Nisala

On Tue, Feb 20, 2018 at 10:14 AM, SajithAR Ariyarathna <sajit...@wso2.com>
wrote:

>
>
> On Tue, Feb 20, 2018 at 9:47 AM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi Sajith,
>>
>> No. I think what we are going to do here is to refer the 'React' which is
>> initialized by the dashboard parent app from the widget level. So setting
>> the React in global context(global.React = React) should be done in the
>> Dashboard parent app.
>>
> +1, even better
>
>
>> So that we can refer it from widgets by using 'externals' in the webpack
>> config.
>>
> We need to document this (putting React as an external dependency and
> using global.React). Is there any docs ATM?
>
>
>> Thanks,
>> Nisala
>>
>> On Tue, Feb 20, 2018 at 9:09 AM, SajithAR Ariyarathna <sajit...@wso2.com>
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> global.React = React
>>>>
>>> Can we do above in the parent Widget (https://www.npmjs.com/package
>>> /@wso2-dashboards/widget)? So that the some widget author doesn't need
>>> React as a dependency.
>>>
>>>
>>> On Thu, Feb 15, 2018 at 1:22 PM, Nisala Nanayakkara <nis...@wso2.com>
>>> wrote:
>>>
>>>> Hi Aruna,
>>>>
>>>> +1 for the approach. We have faced a similar issue in Product SP and
>>>> tested the above-mentioned fix in our local environment. It is working 
>>>> fine.
>>>>
>>>> Thanks,
>>>> Nisala
>>>>
>>>> On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath <aru...@wso2.com> wrote:
>>>>
>>>>> Loading multiple copies of React in the same page creates problems
>>>>> <https://reactjs.org/warnings/refs-must-have-owner.html#multiple-copies-of-react>,
>>>>> such as errors with discriptions like "Element ref was specified as a
>>>>> string (myRefName) but no owner was set. You may have multiple copies of
>>>>> React loaded."
>>>>>
>>>>> In our dashboards, we have widgets that can be added by dragging and
>>>>> dropping. Since it should be possible to add widgets without building the
>>>>> whole app, widgets are bundled separate to the parent app. How ever this
>>>>> means react is bundled with both the widget and the parent app.
>>>>>
>>>>> Adding react as a peerDep doesn't resolve this, as peerDeps only makes
>>>>> sense if we add the widget as a dependency of the parent app and build the
>>>>> parent app only.
>>>>>
>>>>> To resolve this something we can do is to export React to the global
>>>>> scope and allow widgets to use this global reference to React. So we don't
>>>>> have to bundle React with widgets.
>>>>>
>>>>> To put React into global context in the parent dashboard app we can do,
>>>>>
>>>>> import React from 'react'
>>>>> global.React = React
>>>>>
>>>>> in the widget to use this global React ref instead of bundling use
>>>>> webpack externals <https://webpack.js.org/configuration/externals/>.
>>>>>
>>>>> webpack config should be,
>>>>>
>>>>> externals: {
>>>>>   react: 'React'
>>>>> }
>>>>>
>>>>> Instead of the variable name 'React' we can even use some other name
>>>>> like 'CarbonDashboardReactGlobalRef' to avoid  possible conflicts.
>>>>>
>>>>> --
>>>>> Aruna Herath
>>>>> Senior Software Engineer | WSO2
>>>>> Mobile: 0711 051 799 | 0774 569 555
>>>>>
>>>>> <http://wso2.com/signature>
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *Nisala Niroshana Nanayakkara,*
>>>> Software Engineer
>>>> Mobile | +94 717600022
>>>> WSO2 Inc | http://wso2.com/
>>>>
>>>> ___
>>>> Dev mailing list
>>>> Dev@wso2.org
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Sajith Janaprasad Ariyarathna
>>> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
>>> <https://wso2.com/signature>
>>>
>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile | +94 717600022
>> WSO2 Inc | http://wso2.com/
>>
>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> <https://wso2.com/signature>
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Avoid loading multiple copies of React

[Nisala Nanayakkara]

Hi Sajith,

No. I think what we are going to do here is to refer the 'React' which is
initialized by the dashboard parent app from the widget level. So setting
the React in global context(global.React = React) should be done in the
Dashboard parent app. So that we can refer it from widgets by using
'externals' in the webpack config.

Thanks,
Nisala

On Tue, Feb 20, 2018 at 9:09 AM, SajithAR Ariyarathna <sajit...@wso2.com>
wrote:

> Hi Nisala,
>
> global.React = React
>>
> Can we do above in the parent Widget (https://www.npmjs.com/
> package/@wso2-dashboards/widget)? So that the some widget author doesn't
> need React as a dependency.
>
>
> On Thu, Feb 15, 2018 at 1:22 PM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi Aruna,
>>
>> +1 for the approach. We have faced a similar issue in Product SP and
>> tested the above-mentioned fix in our local environment. It is working fine.
>>
>> Thanks,
>> Nisala
>>
>> On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath <aru...@wso2.com> wrote:
>>
>>> Loading multiple copies of React in the same page creates problems
>>> <https://reactjs.org/warnings/refs-must-have-owner.html#multiple-copies-of-react>,
>>> such as errors with discriptions like "Element ref was specified as a
>>> string (myRefName) but no owner was set. You may have multiple copies of
>>> React loaded."
>>>
>>> In our dashboards, we have widgets that can be added by dragging and
>>> dropping. Since it should be possible to add widgets without building the
>>> whole app, widgets are bundled separate to the parent app. How ever this
>>> means react is bundled with both the widget and the parent app.
>>>
>>> Adding react as a peerDep doesn't resolve this, as peerDeps only makes
>>> sense if we add the widget as a dependency of the parent app and build the
>>> parent app only.
>>>
>>> To resolve this something we can do is to export React to the global
>>> scope and allow widgets to use this global reference to React. So we don't
>>> have to bundle React with widgets.
>>>
>>> To put React into global context in the parent dashboard app we can do,
>>>
>>> import React from 'react'
>>> global.React = React
>>>
>>> in the widget to use this global React ref instead of bundling use
>>> webpack externals <https://webpack.js.org/configuration/externals/>.
>>>
>>> webpack config should be,
>>>
>>> externals: {
>>>   react: 'React'
>>> }
>>>
>>> Instead of the variable name 'React' we can even use some other name
>>> like 'CarbonDashboardReactGlobalRef' to avoid  possible conflicts.
>>>
>>> --
>>> Aruna Herath
>>> Senior Software Engineer | WSO2
>>> Mobile: 0711 051 799 | 0774 569 555
>>>
>>> <http://wso2.com/signature>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile | +94 717600022
>> WSO2 Inc | http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sajith Janaprasad Ariyarathna
> Senior Software Engineer; WSO2, Inc.;  http://wso2.com/
> <https://wso2.com/signature>
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Avoid loading multiple copies of React

[Nisala Nanayakkara]

Hi Aruna,

+1 for the approach. We have faced a similar issue in Product SP and tested
the above-mentioned fix in our local environment. It is working fine.

Thanks,
Nisala

On Thu, Feb 15, 2018 at 12:04 PM, Aruna Herath  wrote:

> Loading multiple copies of React in the same page creates problems
> ,
> such as errors with discriptions like "Element ref was specified as a
> string (myRefName) but no owner was set. You may have multiple copies of
> React loaded."
>
> In our dashboards, we have widgets that can be added by dragging and
> dropping. Since it should be possible to add widgets without building the
> whole app, widgets are bundled separate to the parent app. How ever this
> means react is bundled with both the widget and the parent app.
>
> Adding react as a peerDep doesn't resolve this, as peerDeps only makes
> sense if we add the widget as a dependency of the parent app and build the
> parent app only.
>
> To resolve this something we can do is to export React to the global scope
> and allow widgets to use this global reference to React. So we don't have
> to bundle React with widgets.
>
> To put React into global context in the parent dashboard app we can do,
>
> import React from 'react'
> global.React = React
>
> in the widget to use this global React ref instead of bundling use webpack
> externals .
>
> webpack config should be,
>
> externals: {
>   react: 'React'
> }
>
> Instead of the variable name 'React' we can even use some other name like 
> 'CarbonDashboardReactGlobalRef'
> to avoid  possible conflicts.
>
> --
> Aruna Herath
> Senior Software Engineer | WSO2
> Mobile: 0711 051 799 | 0774 569 555
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Docs for how to create Siddhi Extensions using Maven Archetypes

[Nisala Nanayakkara]

Hi,

I have tested the siddhi maven archetypes and released the repository.
Sorry for the delay in updating the mail thread. The initial update mail
was not sent due to some connection issue. I just realized it. Sorry again
for the inconvenience. Please find the released version here[1].

[1] -
https://github.com/wso2-extensions/siddhi-maven-archetype/releases/tag/v1.0.1

Thanks,
Nisala

On Thu, Jan 11, 2018 at 12:41 PM, Nisala Nanayakkara <nis...@wso2.com>
wrote:

> Hi Mohan,
>
> Yes. I will look into this.
>
> Thanks,
> Nisala
>
> On Thu, Jan 11, 2018 at 12:35 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Thu, Jan 11, 2018 at 12:15 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>>
>>>
>>> On Thu, Jan 11, 2018 at 12:14 PM, Sriskandarajah Suhothayan <
>>> s...@wso2.com> wrote:
>>>
>>>> @mohan
>>>> Shall we get a person to create sample extensions and validate this
>>>> against SP-4.0
>>>> and then release these archetypes?
>>>>
>>>
>>>
>>>
>> @Nisala, can you please take this ?
>>
>> Thanks.
>> Mohan
>>
>>
>>>
>>>
>>>>
>>>> Regards
>>>> Suho
>>>>
>>>> On Thu, Jan 11, 2018 at 10:06 AM, Kalaiyarasi Ganeshalingam <
>>>> kalaiyar...@wso2.com> wrote:
>>>>
>>>>> Thanks.
>>>>>
>>>>> Kalaiyarasi Ganeshalingam
>>>>> Associate Software Engineer| WSO2
>>>>> WSO2 Inc : http://wso2.org
>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org=D=1=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg>
>>>>> Tel:+94 076 6792895 <076%20679%202895>
>>>>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>>>>> Blogs : https://kalaiyarasig.blogspot.com/
>>>>> <http://kalai4.blogspot.com/>
>>>>>
>>>>> On Thu, Jan 11, 2018 at 10:04 AM, Mohanadarshan Vivekanandalingam <
>>>>> mo...@wso2.com> wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Jan 11, 2018 at 9:58 AM, Kalaiyarasi Ganeshalingam <
>>>>>> kalaiyar...@wso2.com> wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> Please find the PR [1] for this.
>>>>>>>
>>>>>>> [1] https://github.com/wso2-extensions/siddhi-maven-acrchety
>>>>>>> pe/pull/2
>>>>>>>
>>>>>>
>>>>>> merged. Thanks.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Kalaiyarasi Ganeshalingam
>>>>>>> Associate Software Engineer| WSO2
>>>>>>> WSO2 Inc : http://wso2.org
>>>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org=D=1=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg>
>>>>>>> Tel:+94 076 6792895 <+94%2076%20679%202895>
>>>>>>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>>>>>>> Blogs : https://kalaiyarasig.blogspot.com/
>>>>>>> <http://kalai4.blogspot.com/>
>>>>>>>
>>>>>>> On Wed, Jan 10, 2018 at 6:25 PM, Kalaiyarasi Ganeshalingam <
>>>>>>> kalaiyar...@wso2.com> wrote:
>>>>>>>
>>>>>>>> Hi Mohanadarshan,
>>>>>>>>
>>>>>>>> Yeah, currently I am working on this. Once I have done this, I'll
>>>>>>>> update the thread.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Kalaiyarasi Ganeshalingam
>>>>>>>> Associate Software Engineer| WSO2
>>>>>>>> WSO2 Inc : http://wso2.org
>>>>>>>> <http://www.google.com/url?q=http%3A%2F%2Fwso2.org=D=1=AFQjCNE_eTDfyl2ibPcq0hcXvRDNVuQmMg>
>>>>>>>> Tel:+94 076 6792895 <+94%2076%20679%202895>
>>>>>>>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>>>>>>>> Blogs : https://kalaiyarasig.blogspot.com/
>>>>>>>> <http://kalai4.blogspot.com/>
>>>>>>>>
>>>>>>>> On Wed, Jan 10, 2018 at 6:17 PM,

Re: [Dev] Docs for how to create Siddhi Extensions using Maven Archetypes

[Nisala Nanayakkara]

Hi Mohan,

Yes. I will look into this.

Thanks,
Nisala

On Thu, Jan 11, 2018 at 12:35 PM, Mohanadarshan Vivekanandalingam <
mo...@wso2.com> wrote:

>
>
> On Thu, Jan 11, 2018 at 12:15 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>>
>>
>> On Thu, Jan 11, 2018 at 12:14 PM, Sriskandarajah Suhothayan <
>> s...@wso2.com> wrote:
>>
>>> @mohan
>>> Shall we get a person to create sample extensions and validate this
>>> against SP-4.0
>>> and then release these archetypes?
>>>
>>
>>
>>
> @Nisala, can you please take this ?
>
> Thanks.
> Mohan
>
>
>>
>>
>>>
>>> Regards
>>> Suho
>>>
>>> On Thu, Jan 11, 2018 at 10:06 AM, Kalaiyarasi Ganeshalingam <
>>> kalaiyar...@wso2.com> wrote:
>>>
 Thanks.

 Kalaiyarasi Ganeshalingam
 Associate Software Engineer| WSO2
 WSO2 Inc : http://wso2.org
 
 Tel:+94 076 6792895 <076%20679%202895>
 LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
 Blogs : https://kalaiyarasig.blogspot.com/
 

 On Thu, Jan 11, 2018 at 10:04 AM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

>
>
> On Thu, Jan 11, 2018 at 9:58 AM, Kalaiyarasi Ganeshalingam <
> kalaiyar...@wso2.com> wrote:
>
>> Hi all,
>>
>> Please find the PR [1] for this.
>>
>> [1] https://github.com/wso2-extensions/siddhi-maven-acrchetype/pull/2
>>
>
> merged. Thanks.
>
>
>>
>> Regards,
>>
>> Kalaiyarasi Ganeshalingam
>> Associate Software Engineer| WSO2
>> WSO2 Inc : http://wso2.org
>> 
>> Tel:+94 076 6792895 <+94%2076%20679%202895>
>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>> Blogs : https://kalaiyarasig.blogspot.com/
>> 
>>
>> On Wed, Jan 10, 2018 at 6:25 PM, Kalaiyarasi Ganeshalingam <
>> kalaiyar...@wso2.com> wrote:
>>
>>> Hi Mohanadarshan,
>>>
>>> Yeah, currently I am working on this. Once I have done this, I'll
>>> update the thread.
>>>
>>> Regards,
>>>
>>> Kalaiyarasi Ganeshalingam
>>> Associate Software Engineer| WSO2
>>> WSO2 Inc : http://wso2.org
>>> 
>>> Tel:+94 076 6792895 <+94%2076%20679%202895>
>>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>>> Blogs : https://kalaiyarasig.blogspot.com/
>>> 
>>>
>>> On Wed, Jan 10, 2018 at 6:17 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>


 On Wed, Jan 10, 2018 at 6:17 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

>
>
> On Wed, Jan 10, 2018 at 5:30 PM, Kalaiyarasi Ganeshalingam <
> kalaiyar...@wso2.com> wrote:
>
>> Hi Suho,
>>
>> Please find the docs [1] for how to create Siddhi Extensions
>> using Maven archetypes.
>>
>> [1] https://github.com/wso2-extensions/siddhi-maven-acrchety
>> pe/blob/master/siddhi-extension-archetype/setup.txt
>>
>
> @Kalaiyarasi, IMO above should come to our official documentation
> as well. Again, better to add above information which is available in
> setup.txt to the readme file rather having a separate file.
>
> Thanks,
> Mohan
>
>
>>
>> Regards,
>>
>> Kalaiyarasi Ganeshalingam
>> Associate Software Engineer| WSO2
>> WSO2 Inc : http://wso2.org
>> 
>> Tel:+94 076 6792895 <+94%2076%20679%202895>
>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>> Blogs : https://kalaiyarasig.blogspot.com/
>> 
>>
>> On Wed, Jan 10, 2018 at 5:18 PM, Sriskandarajah Suhothayan <
>> s...@wso2.com> wrote:
>>
>>> Hi Kalaiyarasi
>>>
>>> Where can I find $Subject?
>>>
>>> Regards
>>> Suho
>>>
>>> --
>>>
>>> *S. Suhothayan*
>>> Director
>>> *WSO2 Inc. *
>>> http://wso2.com  
>>>
>>>
>>> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
>>> http://suhothayan.blogspot.com/ 
>>> twitter:
>>> http://twitter.com/suhothayan  | 
>>> linked-in:
>>> http://lk.linkedin.com/in/suhothayan 
>>> *
>>>
>>
>>
>

Re: [Dev] Dashboard Component - Hierarchical Page Support

[Nisala Nanayakkara]

Hi Nipuna,

Yes. We do not support authentication and authorization yet in the
Dashboard Component. Once we do, we are going to maintain a separate table
for dashboard permissions. So we do not need this information inside
dashboard JSON. As an example, when there is a request to view a dashboard,
we can check the whether the user has the permission or not from the
permission DB and fetch the dashboard from dashboard DB according to the
permission.

Thanks,
Nisala

On Thu, Aug 31, 2017 at 10:38 AM, Nipuna Chandradasa <nipu...@wso2.com>
wrote:

> +1 for this format.
>
> Why are we removing lastUpdatedTime? isn't that important meta for an
> admin?
>
> Are we not yet supporting Autherization for dashboard ( who owns, who can
> edit or who can view and so on)? I thought those are parts of the dashboard
> json (not the most secure place but) ...
>
> On Wed, Aug 30, 2017 at 5:16 PM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> We had an off-line discussion regarding this with Suho,Tanya,
>> SajithR,Lasantha, SajithAR and came up with following structure for
>> dashboard JSON,
>>
>>> {
>>> "id": "2",
>>> "url": "sampledashboard",
>>> "name": "Sample Dashboard",
>>> "description": "Lorem ipsum dolor sit amet DAS",
>>> "landingPage": "page0",
>>> "parentId": "1",
>>> "content": {
>>> "pages": [
>>> {
>>> "id": "page0",
>>> "name": "Page 0",
>>> "content": []
>>> },
>>> {
>>> "id": "page1",
>>> "name": "Page 1",
>>> "content": [],
>>> "pages": [
>>> {
>>> "id": "page2",
>>> "name": "Page 2",
>>> "content": [],
>>> "pages": [
>>> {
>>> "id": "page3",
>>> "name": "Page 3",
>>> "content": []
>>> }
>>> ]
>>> },
>>> {
>>> "id": "page4",
>>> "name": "Page 4",
>>> "content": []
>>> }
>>> ]
>>> }
>>>     ]
>>> }
>>> }
>>>
>> So we keep the pageIds and its content with their hierarchy as in the
>> above sample dashboard JSON. There are several reasons to follow
>> above-mentioned approach,
>>
>>- If we follow this we do not need to keep separate mapping between
>>pageIds and its attributes
>>- Convenience in processing the dashboard JSON, when there is a
>>modification or deletion in the pages.
>>
>> Moreover, we are going to remove additional attributes which were
>> introduced in the UUF based dashboard component(version, lastUpdatedTime
>> and etc) as Tanya mentioned.
>>
>>
>> Thanks,
>> Nisala
>>
>> On Wed, Aug 30, 2017 at 8:51 AM, Tanya Madurapperuma <ta...@wso2.com>
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> First of all I think this mail should go to architecture@ :)
>>>
>>> On Mon, Aug 28, 2017 at 11:26 PM, Nisala Nanayakkara <nis...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> We are in the process of re-writing dashboard component using React.
>>>> Currently we have dashboard view component with following features,
>>>>
>>>>- Dashboard listing (will retrieve the dashboard from the DB and
>>>>list down)
>>>>- Backend API support for dashboard CRUD activities.
>>>>- Dashboard view support (This will retrieve the selected dashboard
>>>>from DB and render using Golden Layout)
>>>>- Multiple pages support for dashboards (This will introduce
>>>

Re: [Dev] Dashboard Component - Hierarchical Page Support

[Nisala Nanayakkara]

Hi all,

We had an off-line discussion regarding this with Suho,Tanya,
SajithR,Lasantha, SajithAR and came up with following structure for
dashboard JSON,

> {
> "id": "2",
> "url": "sampledashboard",
> "name": "Sample Dashboard",
> "description": "Lorem ipsum dolor sit amet DAS",
> "landingPage": "page0",
> "parentId": "1",
> "content": {
> "pages": [
> {
> "id": "page0",
> "name": "Page 0",
> "content": []
> },
> {
> "id": "page1",
> "name": "Page 1",
> "content": [],
> "pages": [
> {
> "id": "page2",
> "name": "Page 2",
> "content": [],
> "pages": [
> {
> "id": "page3",
> "name": "Page 3",
> "content": []
> }
> ]
> },
> {
> "id": "page4",
> "name": "Page 4",
> "content": []
> }
> ]
> }
> ]
> }
> }
>
So we keep the pageIds and its content with their hierarchy as in the above
sample dashboard JSON. There are several reasons to follow above-mentioned
approach,

   - If we follow this we do not need to keep separate mapping between
   pageIds and its attributes
   - Convenience in processing the dashboard JSON, when there is a
   modification or deletion in the pages.

Moreover, we are going to remove additional attributes which were
introduced in the UUF based dashboard component(version, lastUpdatedTime
and etc) as Tanya mentioned.


Thanks,
Nisala

On Wed, Aug 30, 2017 at 8:51 AM, Tanya Madurapperuma <ta...@wso2.com> wrote:

> Hi Nisala,
>
> First of all I think this mail should go to architecture@ :)
>
> On Mon, Aug 28, 2017 at 11:26 PM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> We are in the process of re-writing dashboard component using React.
>> Currently we have dashboard view component with following features,
>>
>>- Dashboard listing (will retrieve the dashboard from the DB and list
>>down)
>>- Backend API support for dashboard CRUD activities.
>>- Dashboard view support (This will retrieve the selected dashboard
>>from DB and render using Golden Layout)
>>- Multiple pages support for dashboards (This will introduce multiple
>>pages at the same level, We need to support hierarchical page support )
>>- Internal routing between dashboard listing and dashboard view
>>
>> Since we are using the golden layout for layouting, we keep the content
>> of the each page with respect to page resource url. When we are going to
>> implement the hierarchical pages support, we are going to process these
>> page urls and display the hierarchical menu according these page urls.
>> Please find the sample dashboard json given below,
>>
>>> {
>>> "id": "1",
>>> "url": "sampledashboard",
>>> "name": "Sample Dashboard",
>>> "version": "2.0.0",
>>
>> As we don't have versioning support for dashboards any reason for
> maintaining version info?
>
>>
>>> "description": "Lorem ipsum dolor sit amet DAS",
>>> "owner": "admin",
>>> "lastUpdatedBy": "admin",
>>> "createdTime": 150282009,
>>> "lastUpdatedTime": 1502820091112,
>>
>> Could you also explain the usage of lastUpdatedBy, createdTime and
> lastUpdateTime fields?
>
>>
>>> "isShared": false,
>>
>> I don't think we need isShared any more since we don't have a tenancy
> concept now. We used this attribute earlier to indicate whether a
> particular dashboard which is in super tenant is shared 

Re: [Dev] Dashboard Component - Hierarchical Page Support

[Nisala Nanayakkara]

Hi Nipuna,

We do not keep layout information separately in dashboard JSON as in the
previous version. Since layouting is handled by the GoldenLayout framework,
we keep the dashboard content and layouting information in the "content"
object of dashboard JSON. Since this is somewhat bound to the GoldenLayout
framework, it is bit difficult to separate the layout information into a
separate file.

Thanks,
Nisala

On Tue, Aug 29, 2017 at 10:50 AM, Nipuna Chandradasa <nipu...@wso2.com>
wrote:

> Hi Nisala,
>
> In previous dashboard.json we had a problem like we have bulky
> information(ex:- layout) inside the same JSON. So i assume inside the
> content attribute which holds the page contents we are going to keep these
> information? if it Is there's a plan to move these information to a
> separate file?
>
> Other than that i'm +1 for above mentioned JSON format.
>
> Thank you,
>
> On Tue, Aug 29, 2017 at 9:44 AM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi Udara,
>>
>> Please find my comments inline.
>>
>> Assume we have a page2, which is going to be listed under page0>page1. So
>> are we going to have a object like "page0/page1/page2" : {}
>>  ? This bit is not clear in the above.
>>
>> Yes. we are going to keep an object as mentioned above.
>>
>> Also better if you can explain what is a *page resource URL* so others
>> can understand.
>>
>> It simply means the resource path of the page URL.  Ex:-
>> "page0/page1/page2"
>>
>> {
>> "id": "1",
>> "url": "sampledashboard",
>> "name": "Sample Dashboard",
>> "version": "2.0.0",
>> "description": "Lorem ipsum dolor sit amet DAS",
>> "owner": "admin",
>> "lastUpdatedBy": "admin",
>> "createdTime": 150282009,
>> "lastUpdatedTime": 1502820091112,
>> "isShared": false,
>> "parentId": "1",
>>
>> Yes. We are going to have a dashboard to dashboard relationship. As an
>> example, if someone personalizes a dashboard and save it, we are going
>> maintain its original dashboard id as the parentId.
>>
>> Thanks,
>> Nisala
>>
>>
>> On Tue, Aug 29, 2017 at 8:37 AM, Udara Rathnayake <uda...@wso2.com>
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> Assume we have a page2, which is going to be listed under page0>page1.
>>> So are we going to have a object like "page0/page1/page2" : {}
>>>  ? This bit is not clear in the above.
>>>
>>> ​Also better if you can explain what is a *page resource URL* so others
>>> can understand.
>>>
>>>
>>> On Mon, Aug 28, 2017 at 11:26 PM, Nisala Nanayakkara <nis...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> We are in the process of re-writing dashboard component using React.
>>>> Currently we have dashboard view component with following features,
>>>>
>>>>- Dashboard listing (will retrieve the dashboard from the DB and
>>>>list down)
>>>>- Backend API support for dashboard CRUD activities.
>>>>- Dashboard view support (This will retrieve the selected dashboard
>>>>from DB and render using Golden Layout)
>>>>- Multiple pages support for dashboards (This will introduce
>>>>multiple pages at the same level, We need to support hierarchical page
>>>>support )
>>>>- Internal routing between dashboard listing and dashboard view
>>>>
>>>> Since we are using the golden layout for layouting, we keep the content
>>>> of the each page with respect to page resource url. When we are going to
>>>> implement the hierarchical pages support, we are going to process these
>>>> page urls and display the hierarchical menu according these page urls.
>>>> Please find the sample dashboard json given below,
>>>>
>>>>> {
>>>>> "id": "1",
>>>>> "url": "sampledashboard",
>>>>> "name": "Sample Dashboard",
>>>>> "version": "2.0.0",
>>>>> "description": "Lorem ipsum dolor sit amet DAS",
>>>>

Re: [Dev] Dashboard Component - Hierarchical Page Support

[Nisala Nanayakkara]

Hi Udara,

Ok. above sample doesn't explain this :) both id and parentId are same

Yes. This sample dashboard json is not personalized. So we keep the
parentId as same as its id :)

Thanks,
Nisala

On Tue, Aug 29, 2017 at 11:36 AM, Udara Rathnayake <uda...@wso2.com> wrote:

>
>
> On Tue, Aug 29, 2017 at 9:44 AM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi Udara,
>>
>> Please find my comments inline.
>>
>> Assume we have a page2, which is going to be listed under page0>page1. So
>> are we going to have a object like "page0/page1/page2" : {}
>>  ? This bit is not clear in the above.
>>
>> Yes. we are going to keep an object as mentioned above.
>>
>> Also better if you can explain what is a *page resource URL* so others
>> can understand.
>>
>> It simply means the resource path of the page URL.  Ex:-
>> "page0/page1/page2"
>>
>> {
>> "id": "1",
>> "url": "sampledashboard",
>> "name": "Sample Dashboard",
>> "version": "2.0.0",
>> "description": "Lorem ipsum dolor sit amet DAS",
>> "owner": "admin",
>> "lastUpdatedBy": "admin",
>> "createdTime": 150282009,
>> "lastUpdatedTime": 1502820091112,
>> "isShared": false,
>> "parentId": "1",
>>
>> Yes. We are going to have a dashboard to dashboard relationship. As an
>> example, if someone personalizes a dashboard and save it, we are going
>> maintain its original dashboard id as the parentId.
>>
> ​Ok. above sample doesn't explain this :) both id and parentId are same​
>
>
>>
>> Thanks,
>> Nisala
>>
>>
>> On Tue, Aug 29, 2017 at 8:37 AM, Udara Rathnayake <uda...@wso2.com>
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> Assume we have a page2, which is going to be listed under page0>page1.
>>> So are we going to have a object like "page0/page1/page2" : {}
>>>  ? This bit is not clear in the above.
>>>
>>> ​Also better if you can explain what is a *page resource URL* so others
>>> can understand.
>>>
>>>
>>> On Mon, Aug 28, 2017 at 11:26 PM, Nisala Nanayakkara <nis...@wso2.com>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> We are in the process of re-writing dashboard component using React.
>>>> Currently we have dashboard view component with following features,
>>>>
>>>>- Dashboard listing (will retrieve the dashboard from the DB and
>>>>list down)
>>>>- Backend API support for dashboard CRUD activities.
>>>>- Dashboard view support (This will retrieve the selected dashboard
>>>>from DB and render using Golden Layout)
>>>>- Multiple pages support for dashboards (This will introduce
>>>>multiple pages at the same level, We need to support hierarchical page
>>>>support )
>>>>- Internal routing between dashboard listing and dashboard view
>>>>
>>>> Since we are using the golden layout for layouting, we keep the content
>>>> of the each page with respect to page resource url. When we are going to
>>>> implement the hierarchical pages support, we are going to process these
>>>> page urls and display the hierarchical menu according these page urls.
>>>> Please find the sample dashboard json given below,
>>>>
>>>>> {
>>>>> "id": "1",
>>>>> "url": "sampledashboard",
>>>>> "name": "Sample Dashboard",
>>>>> "version": "2.0.0",
>>>>> "description": "Lorem ipsum dolor sit amet DAS",
>>>>> "owner": "admin",
>>>>> "lastUpdatedBy": "admin",
>>>>> "createdTime": 150282009,
>>>>> "lastUpdatedTime": 1502820091112,
>>>>> "isShared": false,
>>>>> "parentId": "1",
>>>>>
>>>> ​Also what is the use of parentId here?​
>>>
>>> ​Are we going to have any dashboard to dashboard relationship? ​
>

Re: [Dev] Dashboard Component - Hierarchical Page Support

[Nisala Nanayakkara]

Hi Udara,

Please find my comments inline.

Assume we have a page2, which is going to be listed under page0>page1. So
are we going to have a object like "page0/page1/page2" : {}
 ? This bit is not clear in the above.

Yes. we are going to keep an object as mentioned above.

Also better if you can explain what is a *page resource URL* so others can
understand.

It simply means the resource path of the page URL.  Ex:- "page0/page1/page2"

{
"id": "1",
"url": "sampledashboard",
"name": "Sample Dashboard",
"version": "2.0.0",
"description": "Lorem ipsum dolor sit amet DAS",
"owner": "admin",
"lastUpdatedBy": "admin",
"createdTime": 150282009,
"lastUpdatedTime": 1502820091112,
"isShared": false,
"parentId": "1",

Yes. We are going to have a dashboard to dashboard relationship. As an
example, if someone personalizes a dashboard and save it, we are going
maintain its original dashboard id as the parentId.

Thanks,
Nisala


On Tue, Aug 29, 2017 at 8:37 AM, Udara Rathnayake <uda...@wso2.com> wrote:

> Hi Nisala,
>
> Assume we have a page2, which is going to be listed under page0>page1. So
> are we going to have a object like "page0/page1/page2" : {}
>  ? This bit is not clear in the above.
>
> ​Also better if you can explain what is a *page resource URL* so others
> can understand.
>
>
> On Mon, Aug 28, 2017 at 11:26 PM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> We are in the process of re-writing dashboard component using React.
>> Currently we have dashboard view component with following features,
>>
>>- Dashboard listing (will retrieve the dashboard from the DB and list
>>down)
>>- Backend API support for dashboard CRUD activities.
>>- Dashboard view support (This will retrieve the selected dashboard
>>from DB and render using Golden Layout)
>>- Multiple pages support for dashboards (This will introduce multiple
>>pages at the same level, We need to support hierarchical page support )
>>- Internal routing between dashboard listing and dashboard view
>>
>> Since we are using the golden layout for layouting, we keep the content
>> of the each page with respect to page resource url. When we are going to
>> implement the hierarchical pages support, we are going to process these
>> page urls and display the hierarchical menu according these page urls.
>> Please find the sample dashboard json given below,
>>
>>> {
>>> "id": "1",
>>> "url": "sampledashboard",
>>> "name": "Sample Dashboard",
>>> "version": "2.0.0",
>>> "description": "Lorem ipsum dolor sit amet DAS",
>>> "owner": "admin",
>>> "lastUpdatedBy": "admin",
>>> "createdTime": 150282009,
>>> "lastUpdatedTime": 1502820091112,
>>> "isShared": false,
>>> "parentId": "1",
>>>
>> ​Also what is the use of parentId here?​
>
> ​Are we going to have any dashboard to dashboard relationship? ​
>
>> "content": [
>>> {
>>> "page0": {
>>> *content of page0*
>>> },
>>> "page1": {
>>> *content of page1*
>>> }
>>> }
>>> ]
>>> }
>>
>>
>>
>> So we do not keep any mapping between pages and its hierarchy as in the
>> previous versions of the dashboard component. But we may need to maintain
>> some additional attributes such as Page title, isHidden and etc wrt page
>> URL. In that case, I think it is better to maintain a separate mapping
>> between these attributes and page URLs as in the previous dashboard
>> component. Please find the sample dashboard json given below.
>>
>>> {
>>> "id": "1",
>>> "url": "sampledashboard",
>>> "name": "Sample Dashboard",
>>> "version": "2.0.0",
>>> "description": "Lorem ipsum dolor sit amet DAS"

[Dev] Dashboard Component - Hierarchical Page Support

[Nisala Nanayakkara]

Hi all,

We are in the process of re-writing dashboard component using React.
Currently we have dashboard view component with following features,

   - Dashboard listing (will retrieve the dashboard from the DB and list
   down)
   - Backend API support for dashboard CRUD activities.
   - Dashboard view support (This will retrieve the selected dashboard from
   DB and render using Golden Layout)
   - Multiple pages support for dashboards (This will introduce multiple
   pages at the same level, We need to support hierarchical page support )
   - Internal routing between dashboard listing and dashboard view

Since we are using the golden layout for layouting, we keep the content of
the each page with respect to page resource url. When we are going to
implement the hierarchical pages support, we are going to process these
page urls and display the hierarchical menu according these page urls.
Please find the sample dashboard json given below,

> {
> "id": "1",
> "url": "sampledashboard",
> "name": "Sample Dashboard",
> "version": "2.0.0",
> "description": "Lorem ipsum dolor sit amet DAS",
> "owner": "admin",
> "lastUpdatedBy": "admin",
> "createdTime": 150282009,
> "lastUpdatedTime": 1502820091112,
> "isShared": false,
> "parentId": "1",
> "content": [
> {
> "page0": {
> *content of page0*
> },
> "page1": {
> *content of page1*
> }
> }
> ]
> }



So we do not keep any mapping between pages and its hierarchy as in the
previous versions of the dashboard component. But we may need to maintain
some additional attributes such as Page title, isHidden and etc wrt page
URL. In that case, I think it is better to maintain a separate mapping
between these attributes and page URLs as in the previous dashboard
component. Please find the sample dashboard json given below.

> {
> "id": "1",
> "url": "sampledashboard",
> "name": "Sample Dashboard",
> "version": "2.0.0",
> "description": "Lorem ipsum dolor sit amet DAS",
> "owner": "admin",
> "lastUpdatedBy": "admin",
> "createdTime": 150282009,
> "lastUpdatedTime": 1502820091112,
> "isShared": false,
> "parentId": "1",
>
>
>
>
>
>
>
>
>
> *"menu": {"page0": {"ishidden": false,
> "title": "Page 0"},"page1": {"ishidden":
> false,"title": "Page 1"}}*,
> "content": [
> {
> "page0": {},
> "page1": {}
> }
> ]
> }
>
Because It will give a clear separation between dashboard content and the
pages’ menu attributes. WDYT?

Thanks,
Nisala

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile | +94 717600022
WSO2 Inc | http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error while installing Account Recovery and Credential Management Feature in wso2am-2.0.1-SNAPSHOT

[Nisala Nanayakkara]

Hi Mushtaq,

Were you able to resolve this issue ? I faced a similar scenario when I was
trying to install the above mentioned feature in APIM 2.0.0.

Thanks,
Nisala

On Tue, Nov 8, 2016 at 2:02 PM, Mushthaq Rumy  wrote:

> Hi Abimaran,
>
> I downloaded the P2 locally and checked. It still gives the same error.
> Any help on this is highly appreciated.
>
> Thanks & Regards,
> Mushthaq
>
> On Mon, Oct 31, 2016 at 2:27 PM, Abimaran Kugathasan 
> wrote:
>
>> Hi Mushthaq,
>>
>> This issue mostly occurs when the JARs are corrupted while installing
>> over the network. You can download the entire P2 locally and check.
>>
>> On Mon, Oct 31, 2016 at 12:22 PM, Mushthaq Rumy 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am getting an error in the console while trying to install Account
>>> Recovery and Credential Management Feature in wso2am-2.0.1-SNAPSHOT through
>>> management console. I have attached the error log file herewith.
>>>
>>> Has anyone has come across this? Any input on this is highly appreciated.
>>>
>>>
>>>
>>> *Error*TID: [-1234] [] [2016-10-31 11:07:10,686] ERROR
>>> {org.wso2.carbon.feature.mgt.services.prov.ProvisioningAdminService} -
>>> Error occurred while performing provisioning action
>>> {org.wso2.carbon.feature.mgt.services.prov.ProvisioningAdminService}
>>> org.wso2.carbon.feature.mgt.core.ProvisioningException: NLS missing
>>> message: Phase_Install_Error in: org.eclipse.equinox.internal.p
>>> 2.engine.messages
>>>   NLS missing message: session_context in: org.eclipse.equinox.internal.p
>>> 2.engine.messages
>>>   NLS missing message: artifact_file_not_found in:
>>> org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.messages
>>> at org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.perf
>>> ormProvisioningAction(ProvisioningUtils.java:76)
>>> at org.wso2.carbon.feature.mgt.core.util.ProvisioningUtils.perf
>>> ormProvisioningAction(ProvisioningUtils.java:85)
>>> at org.wso2.carbon.feature.mgt.services.prov.ProvisioningAdminS
>>> ervice.performProvisioningAction(ProvisioningAdminService.java:313)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce
>>> ssorImpl.java:57)
>>> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
>>> thodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:606)
>>> at org.apache.axis2.rpc.receivers.RPCUtil.invokeServiceClass(RP
>>> CUtil.java:212)
>>> at org.apache.axis2.rpc.receivers.RPCMessageReceiver.invokeBusi
>>> nessLogic(RPCMessageReceiver.java:117)
>>> at org.apache.axis2.receivers.AbstractInOutMessageReceiver.invo
>>> keBusinessLogic(AbstractInOutMessageReceiver.java:40)
>>> at org.apache.axis2.receivers.AbstractMessageReceiver.receive(A
>>> bstractMessageReceiver.java:110)
>>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180)
>>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>>> essMessage(LocalTransportReceiver.java:169)
>>> at org.apache.axis2.transport.local.LocalTransportReceiver.proc
>>> essMessage(LocalTransportReceiver.java:82)
>>> at org.wso2.carbon.core.transports.local.CarbonLocalTransportSe
>>> nder.finalizeSendWithToAddress(CarbonLocalTransportSender.java:45)
>>> at org.apache.axis2.transport.local.LocalTransportSender.invoke
>>> (LocalTransportSender.java:77)
>>> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:442)
>>> at org.apache.axis2.description.OutInAxisOperationClient.send(O
>>> utInAxisOperation.java:430)
>>> at org.apache.axis2.description.OutInAxisOperationClient.execut
>>> eImpl(OutInAxisOperation.java:225)
>>> at org.apache.axis2.client.OperationClient.execute(OperationCli
>>> ent.java:149)
>>> at org.wso2.carbon.feature.mgt.stub.ProvisioningAdminServiceStu
>>> b.performProvisioningAction(ProvisioningAdminServiceStub.java:1085)
>>> at org.wso2.carbon.feature.mgt.ui.ProvisioningAdminClient.perfo
>>> rmInstallation(ProvisioningAdminClient.java:138)
>>> at org.apache.jsp.feature_002dmgt.perform_005finstallation_002d
>>> ajaxprocessor_jsp._jspService(perform_005finstallation_002da
>>> jaxprocessor_jsp.java:134)
>>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.ja
>>> va:70)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at org.apache.jasper.servlet.JspServletWrapper.service(JspServl
>>> etWrapper.java:439)
>>> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServl
>>> et.java:395)
>>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
>>> at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.j
>>> ava:80)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>>> 

Re: [Dev] Creating a widget web-component using existing charting libraries

[Nisala Nanayakkara]

Hi Pawan,

AFAIK We are using vizGrammer library in widget generation in
carbon-dashboards 2.1.x version. Please find the analytics libraries which
is used in carbon-dashboards here[1].

[1] -
https://github.com/wso2/carbon-dashboards/tree/2.1.x/apps/portal/libs/analytics-wso2_5.0.12

Thanks,
Nisala

On Fri, Mar 24, 2017 at 2:22 PM, Pawan Gunaratne  wrote:

> Hi,
>
> I need to clarify that gadget creation in carbon-dashboard, are we still
> using that lgviz library or moved to VizGrammer ?
>
> Thanks.
>
> On Thu, Mar 23, 2017 at 12:37 PM, Udara Rathnayake 
> wrote:
>
>> Thanks Tharik!
>>
>> Updated my wso2-widget WC to use VizGrammer, but it seems we have a bunch
>> of document.getElementById()s which is not going to search inside shadow
>> roots. So this is not going to work :( . Let me look into other
>> alternatives.
>>
>> On Thu, Mar 23, 2017 at 12:11 PM, Tharik Kanaka  wrote:
>>
>>> Hi Udara,
>>>
>>> Igviz library is no longer used and we have replaced that with
>>> VizGrammar. In VizGrammar you can use draw() function to draw the chart in
>>> a div. If you want to insert records to update the chart you can use
>>> insert(). You can try samples [1] and all the library content along with
>>> samples are available in  github repository [2].
>>>
>>> *var data = {*
>>> *  "metadata" : {*
>>> *  "names" : ["rpm","torque","horsepower", "EngineType"],*
>>> *  "types" : ["linear","linear", "ordinal","ordinal"]*
>>> *  },*
>>> *  "data": [*
>>> *[1, 10, 1, "Piston"],  [2, 12, 5, "Piston"]]*
>>> *};*
>>>
>>> *var config = {*
>>> *charts : [{type: "area",  x : "rpm", y : "torque"}],*
>>> *maxLength: 10,*
>>> *width: 400,*
>>> *height: 200*
>>> *}*
>>>
>>> *var chart = new vizg(data, **config**);*
>>>
>>> *chart.draw("#chartDiv");*
>>>
>>> *chart.insert([[8000, 74, 120, "Rotary"]]);*
>>>
>>> [1] http://wso2.github.io/VizGrammar/samples/
>>>
>>> [2] https://github.com/wso2/VizGrammar/
>>>
>>> Thanks,
>>>
>>>
>>> On Thu, Mar 23, 2017 at 11:42 AM, Udara Rathnayake 
>>> wrote:
>>>
 Hi all,

 I'm trying to create a web component (wso2-widget) to try-out
 capabilities which we can incorporate in to our widget rendering framework.

 ​Within my renderWidget function[1] I'm using the usual igviz.plot but
 unable to draw the chart inside container element which exists inside a
 shadow-root.​ Did some debugging but unable to find the place which
 breaks(No errors too).

 ​Appreciate any feedback on this.​

 PS:- If you need to try out this, host the source within "wc" branch
 inside apache2 and use Google chrome.

 ​[1] https://github.com/udarakr/uuf-sample-gadget/blob/wc/wso2-wi
 dget/wso2-widget.comp.html#L121

 --
 Regards,
 UdaraR

>>>
>>>
>>>
>>> --
>>>
>>> *Tharik Kanaka*
>>>
>>> WSO2, Inc | lean . enterprise . middleware
>>>
>>> Email: tha...@wso2.com | Web: www.wso2.com
>>>
>>
>>
>>
>> --
>> Regards,
>> UdaraR
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Pawan Gunaratne*
> Software Engineering Intern
> *WSO2*
> *Mob : 0770373556*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How can we add multi language support in javascript files

[Nisala Nanayakkara]

Hi Prasanna,

UUF has the capability of facilitating above mentioned scenario. You can
define your language property file under the ‘lang’ directory as follows.

|src
| |main
|   | pages/
|   | fragments/
|   | layouts/
|   | modules/
|   | lang/
|en_US.properties
|   | public/

After that you can use following code segment to achieve your requirement
in your hbs file.

{{i18n "my.sample.key"}}

Please go through sample app available here[1] if you need more
clarification. Moreover you can find actual usage above code segment
here[2] and corresponding language file here[3].

[1] -
https://github.com/wso2/carbon-uuf/tree/master/samples/apps/org.wso2.carbon.uuf.sample.pets-store.app
[2] -
https://github.com/wso2/carbon-uuf/blob/master/samples/apps/org.wso2.carbon.uuf.sample.pets-store.app/src/main/pages/index.hbs#L16
[3] -
https://github.com/wso2/carbon-uuf/blob/master/samples/apps/org.wso2.carbon.uuf.sample.pets-store.app/src/main/lang/en_US.properties

Thanks,
Nisala

On Thu, Mar 23, 2017 at 9:01 AM, Prasanna Dangalla 
wrote:

> Hi Devs,
>
> Is there a mechanism defined to use something like i18n in javascript ?
> Does the UUF has the capability of facilitating this ? You inputs are
> highly appreciated.
>
> Thanks
>
> *Prasanna Dangalla*
> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
>
> *cell: +94 718 11 27 51*
> *twitter: @prasa77*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] about UUF

[Nisala Nanayakkara]

Hi Varuni,

Please find the UUF Web App Developer's guide here[1]. Additionally you can
go through readme files available in github repositories[2][3].

[1] -
https://docs.google.com/document/d/10UDdArHV1eYEfiONu8saqPnnJyUjH3vxOrv0k0rK5hc/edit#heading=h.9icxvol1vn83
[2] - https://github.com/wso2/carbon-uuf
[3] - https://github.com/wso2/carbon-uuf-maven-tools

Thanks,
Nisala

On Tue, Mar 7, 2017 at 5:16 PM, Varuni Alwis  wrote:

> Hi all,
>
> Is there any documentation  related to UUF where I can refer to?
>
> Thanks.
>
> *Varuni Alwis*
> *Software Engineer - Intern*
> *WSO2*
>
> Email : var...@wso2.com
> Mobile : +94 719865395 <+94%2071%20986%205395>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Exceeding the 65535 bytes limit - idp-mgt-edit.jsp - method _jspService(HttpServletRequest, HttpServletResponse)

[Nisala Nanayakkara]

Hi all,

I am trying to upgrade tomcat version in carbon-kernel 4.4.11 from 7.0.73
to 7.0.75. After upgrading, I cannot access to Identity Provider’s add
page. It gives following error[1],

It seems like method ‘jspService(HttpServletRequest, HttpServletResponse)’
is hitting 64k limit. I have tried adding additional paramaters as follows
in to /conf/tomcat/web.xml

mappedfile
false


But it is not working also. So I think we need to refactor the jsp page[2].
WDYT ?

[1] -

An error occurred at line: [109] in the generated java file:
[wso2is-5.3.0/lib/tomcat/work/Catalina/localhost/_/proxytemp/hc_487567695/org/apache/jsp/idpmgt/idp_002dmgt_002dedit_jsp.java]
The code of method _jspService(HttpServletRequest, HttpServletResponse) is
exceeding the 65535 bytes limit

Stacktrace:
at
org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:103)
at
org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:366)
at
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:490)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:379)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:354)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:341)
at
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:662)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:364)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:339)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at org.wso2.carbon.ui.JspServlet.service(JspServlet.java:155)
at org.wso2.carbon.ui.TilesJspServlet.service(TilesJspServlet.java:80)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor.service(ContextPathServletAdaptor.java:37)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:747)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:603)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:542)
at
org.eclipse.equinox.http.servlet.internal.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:37)
at
org.eclipse.equinox.http.helper.ContextPathServletAdaptor$RequestDispatcherAdaptor.include(ContextPathServletAdaptor.java:369)
at
org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:897)
at
org.apache.jasper.runtime.PageContextImpl.doInclude(PageContextImpl.java:688)
at
org.apache.jasper.runtime.PageContextImpl.include(PageContextImpl.java:682)
at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.tiles.jsp.context.JspUtil.doInclude(JspUtil.java:87)
at
org.apache.tiles.jsp.context.JspTilesRequestContext.include(JspTilesRequestContext.java:88)
at
org.apache.tiles.jsp.context.JspTilesRequestContext.dispatch(JspTilesRequestContext.java:82)
at
org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:465)
at
org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:140)
at
org.apache.tiles.jsp.taglib.InsertAttributeTag.render(InsertAttributeTag.java:117)
at
org.apache.tiles.jsp.taglib.RenderTagSupport.execute(RenderTagSupport.java:171)
at
org.apache.tiles.jsp.taglib.RoleSecurityTagSupport.doEndTag(RoleSecurityTagSupport.java:75)
at
org.apache.tiles.jsp.taglib.ContainerTagSupport.doEndTag(ContainerTagSupport.java:80)
at
org.apache.jsp.admin.layout.template_jsp._jspx_meth_tiles_005finsertAttribute_005f7(template_jsp.java:751)
at
org.apache.jsp.admin.layout.template_jsp._jspService(template_jsp.java:387)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:439)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:395)
at 

Re: [Dev] WSO2 Committers += Chanaka Cooray

[Nisala Nanayakkara]

Congratz Chanaka :D

On Fri, Feb 24, 2017 at 3:36 PM, Niranjan Karunanandham 
wrote:

> Hi All,
>
> It's my pleasure to welcome Chanaka Cooray as a WSO2 Committer.
>
> Chanaka has been a valuable contributor to the Platform Team. In
> recognition of his contribution, dedication and commitment he has been
> voted as a WSO2 committer.
>
> Chanaka, welcome aboard and keep up the good work!
>
> Regards,
> Nira
>
> --
>
>
> *Niranjan Karunanandham*
> Associate Technical Lead - WSO2 Inc.
> WSO2 Inc.: http://www.wso2.com
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [UUF] Define page layout for default error pages

[Nisala Nanayakkara]

Hi Danushka,

You can define your own error pages and its' layout as follows. As an
example you need to add below configuration to app.yaml.

*errorPages: *
*404: "/foundation/error/404"*
* default: **"/foundation/error/default**"*

Please find related app.yaml[1] and the error pages here[2].

[1] -
https://github.com/wso2/carbon-uuf/blob/master/samples/apps/org.wso2.carbon.uuf.sample.pets-store.app/src/main/app.yaml
[2] -
https://github.com/wso2/carbon-uuf/tree/master/samples/components/org.wso2.carbon.uuf.sample.foundation.ui/src/main/pages/error

Thanks,
Nisala



On Sat, Jan 21, 2017 at 6:20 AM, Danushka Fernando 
wrote:

> Hi All
> I found that default error pages like 404 error page which comes from UUF
> doesn't use app's basic layout. And I couldn't find a way to override it.
> Is there a way of achieving this.
>
> Thanks & Regards
> Danushka Fernando
> Senior Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729 <+94%2071%20633%202729>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invoking a Microservice REST api in UUF

[Nisala Nanayakkara]

Hi Denuwanthi,

Based on the off-line discussion we had, Please import the package
javax.ws.rs.* in  UI specific microservice pom file. It will solve the
issue of redirecting to "page not found' inside your uuf app.

Thanks,
Nisala

On Wed, Jan 18, 2017 at 2:26 PM, Denuwanthi De Silva 
wrote:

> Hi,
>
> I added a UI specific Microservice REST API following [1]and[2].
> But, When I invoke the url, it redirects to "page not found' inside our
> uuf app.
>
> I have added the REST service as an import in the uuf app pom as well.
> Is this all we need to do to register a UI specific microservice in UUF?
> Have I missed any registration step?
>
> Any input on this will be helpful
>
>
> [1]https://github.com/wso2/carbon-uuf/blob/master/
> samples/osgi-services/org.wso2.carbon.uuf.sample.api/
> src/main/java/org/wso2/carbon/uuf/sample/api/HelloService.java
> [2]https://github.com/wso2/carbon-uuf/blob/master/
> samples/apps/org.wso2.carbon.uuf.sample.pets-store.app/src/
> main/component.yaml
>
> Thanks
>
> --
> Denuwanthi De Silva
> Senior Software Engineer;
> WSO2 Inc.; http://wso2.com,
> Email: denuwan...@wso2.com
> Blog: https://denuwanthi.wordpress.com/
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Show images persisted in a database or in a non-public folder from a uuf app

[Nisala Nanayakkara]

HI,

We had a similar requirement like this in dashboard component. Our
requirement was to read dashboard files that resides in the DB from the
client-side. For that, we wrote an UI-specific REST API, that will read the
file from the DB. I think you can use the same strategy to do the $subject.
UUF can deploy REST apis for a UI component as [1][2].

[1] -
https://github.com/wso2/carbon-dashboards/blob/uuf-portal/components/org.wso2.carbon.dashboards.view/src/main/component.yaml
[2] -
https://github.com/wso2/carbon-dashboards/blob/uuf-portal/components/org.wso2.carbon.dashboards.metadata.api/src/main/java/org/wso2/carbon/dashboards/metadata/api/MetadataProviderAPI.java


Thanks,
Nisala

On Fri, Jan 13, 2017 at 2:49 PM, Thanuja Jayasinghe 
wrote:

> Hi Sajith,
>
> For the user portal feature in IS 6.0.0, we have a requirement to show
> user image in the app. These images are currently persisted inside a
> database. So we need a way to provide image URL for those.
>
> I have created the issue [1] to track this.
>
> [1] - https://github.com/wso2/carbon-uuf/issues/138
>
> Thanks,
> Thanuja
> --
> *Thanuja Lakmal*
> Senior Software Engineer
> WSO2 Inc. http://wso2.com/
> *lean.enterprise.middleware*
> Mobile: +94715979891 +94758009992
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 MSF4J 2.1.0 RC3

[Nisala Nanayakkara]

Hi Hanen,

Yes. Please find the samples here [1].

[1] - https://github.com/wso2/msf4j/tree/master/samples

Thanks,
Nisala

On Thu, Jan 5, 2017 at 8:50 PM, Hanen Ben Rhouma <hanen...@gmail.com> wrote:

> Hi,
>
> How can we get those samples?
>
> Regards,
> Hanen
>
> On Thu, Nov 3, 2016 at 10:01 AM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> Thank you for testing the MSF4J 2.1.0 RC3. This vote is passed with 3 +1s
>> and 0 -1s.
>> Therefore we will proceed with the MSF4J 2.1.0 release.
>>
>> Best Regards
>> Thusitha
>>
>> On Thu, Nov 3, 2016 at 2:17 PM, Nisala Nanayakkara <nis...@wso2.com>
>> wrote:
>>
>>> Hi Thusitha,
>>>
>>> I have tested following samples.
>>>
>>>- Hello World
>>>- Spring Hello World
>>>- Session-aware Service
>>>- Lifecycle
>>>- Metrics
>>>- File Server
>>>- FormParam
>>>- BasicAuth Security
>>>- OAuth2 Security
>>>- Template
>>>
>>> [x] Stable - go ahead and release
>>> Thanks,
>>> Nisala
>>>
>>> On Mon, Oct 31, 2016 at 8:41 PM, Thusitha Thilina Dayaratne <
>>> thusit...@wso2.com> wrote:
>>>
>>>> Hi Devs,
>>>>
>>>> This is the 3rd Release Candidate of WSO2 MSF4J(Microservices
>>>> Framework for Java) 2.1.0.
>>>>
>>>> Please download, test the framework and vote. The vote will be open
>>>> for 72 hours or as needed.
>>>> Refer to GitHub readmes for guides.
>>>>
>>>> *Source and binary distribution files:*
>>>> https://github.com/wso2/msf4j/releases/tag/v2.1.0-rc3
>>>>
>>>> *Maven staging repository:*
>>>> https://maven.wso2.org/nexus/content/repositories/orgwso2msf4j-1010
>>>>
>>>> *The tag to be voted upon:*
>>>> https://github.com/wso2/msf4j/tree/v2.1.0-rc3
>>>>
>>>>
>>>>
>>>> [ ] Broken - do not release (explain why)
>>>> [ ] Stable - go ahead and release
>>>>
>>>> Thank you,
>>>> Platform Team
>>>> --
>>>> Thusitha Dayaratne
>>>> Software Engineer
>>>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>>>
>>>> Mobile  +94712756809
>>>> Blog  alokayasoya.blogspot.com
>>>> Abouthttp://about.me/thusithathilina
>>>> <http://wso2.com/signature>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>
>>
>>
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809 <+94%2071%20275%206809>
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>> <http://wso2.com/signature>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

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 dependency within a UUF based application.


org.wso2.carbon.dashboards
org.wso2.carbon.dashboards.view
3.0.0-m2
zip
uuf-component



org.wso2.carbon.dashboards
org.wso2.carbon.dashboards.api.feature
3.0.0-m2
zip



You can find the release tag here[1]. Help us to improve the component,
report issue here[2].

[1] https://github.com/wso2/carbon-dashboards/releases/tag/v3.0.0-m2
[2] https://github.com/wso2/carbon-dashboards/issues


​-- WSO2 Platform Team--​

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] JAX-RS Enpoints are not exposed with Java Security Manager Enabled

[Nisala Nanayakkara]

Hi all,

I am trying to deploy a web app which contains some classes in the
web-inf/classes directory in AS 5.3.0. The classes inside the
web-inf/classes directory are used to expose several jaxrs endpoints. But
when I enabled the java security manager, those enpoints are not working
(404 Not found). I checked whether there are any back-end errors. But I was
unable to find any. Then I tried enabling the security logs by following
this article [1]. But I could not find any useful information in that also.
When I disabled the java security manager, it is working as expected. Then
I tried to pack the classes inside the web-inf/classes dir into a jar and
put it in the web-inf/lib directory. After doing that change, it is working
as expected. I have attached the sec.policy file here. Please be kind
enough to provide your kind input regarding this.

[1] -
http://isuru-perera.blogspot.com/2014/12/enabling-java-security-manager-for-wso2.html

Thanks,
Nisala

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/


sec.policy
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Shan Mahanama

[Nisala Nanayakkara]

Congratz Shan !! 

On Monday, 7 November 2016, Lasantha Samarakoon  wrote:

> Congratz Shan
>
> *Lasantha Samarakoon* | Software Engineer
> WSO2, Inc.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 (71) 214 1576
> Email:  lasant...@wso2.com
> 
> Web:www.wso2.com
>
> lean . enterprise . middleware
>
> On Mon, Nov 7, 2016 at 12:37 PM, Sameera Gunarathne  > wrote:
>
>> Congrats shan!!! :)
>>
>> On Mon, Nov 7, 2016 at 12:27 PM, Chanaka Cooray > > wrote:
>>
>>> Congratz shan !!!
>>>
>>> On Mon, Nov 7, 2016 at 12:14 PM, Niranjan Karunanandham <
>>> niran...@wso2.com >
>>> wrote:
>>>
 Hi all,

 It's my pleasure to announce Shan Mahanama as a WSO2 Committer. Shan
 has been a valuable contributor for Platform team. And in recognition of
 his contribution to WSO2, he has been voted as a WSO2 Committer.

 Shan, Congratulations and keep up the good work!

 Regards,
 Nira.

 --


 *Niranjan Karunanandham*
 Associate Technical Lead - WSO2 Inc.
 WSO2 Inc.: http://www.wso2.com


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


>>>
>>>
>>> --
>>> Chanaka Cooray
>>> Software Engineer, WSO2 Inc. http://wso2.com
>>> Email: chana...@wso2.com
>>> 
>>> Mobile: +94713149860
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org 
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sameera Gunarathne
>> Software Engineer, WSO2 Inc. http://wso2.com
>> 
>> Email: samee...@wso2.com
>> 
>> Mobile: +94714155561
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org 
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Megala Uthayakumar

[Nisala Nanayakkara]

Congratz Megala :D !!

On Tue, Nov 1, 2016 at 2:21 PM, Sinthuja Ragendran 
wrote:

> Hi all,
>
> It's my pleasure to announce Megala Uthayakumar as a WSO2 Committer.
> Megala had been a valuable contributor for Dashboard Server product, and
> now for EMM/IoT Products. And in recognition of her contribution to WSO2,
> she has been voted as a WSO2 Committer.
>
> Megala, Keep up the good work and wish you all the best for your future
> endeavors!
>
> Thanks,
> Sinthuja.
>
> --
> *Sinthuja Rajendran*
> Technical Lead
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 MSF4J 2.1.0 RC2

[Nisala Nanayakkara]

Hi Thusitha,

I have tested following samples.

   - Hello World
   - Spring Hello World
   - Session-aware Service
   - Lifecycle
   - Metrics
   - File Server
   - FormParam
   - Circuit Breaker
   - Log-interceptor
   - BasicAuth Security
   - OAuth2 Security
   - Template

No major issues were found. But found a bug in a sample. In the
Log-interceptor sample, 'org.wso2.carbon.messaging' package is not
imported. We need to import this to run Log-interceptor sample properly.
Other samples are working as expected.

Thanks,
Nisala


On Mon, Oct 24, 2016 at 4:26 PM, Isuru Perera  wrote:

> +1
>
> I tested metrics and http-monitoring samples.
>
> On Thu, Oct 20, 2016 at 5:36 PM, Thusitha Thilina Dayaratne <
> thusit...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> This is the 2nd Release Candidate of WSO2 MSF4J(Microservices Framework
>> for Java) 2.1.0.
>>
>> Please download, test the framework and vote. The vote will be open for
>> 72 hours or as needed.
>> Refer to GitHub readmes for guides.
>>
>> * Source and binary distribution files:*
>> https://github.com/wso2/msf4j/releases/tag/v2.1.0-rc2
>>
>> *Maven staging repository:*
>> https://maven.wso2.org/nexus/content/repositories/orgwso2msf4j-1008
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/msf4j/tree/v2.1.0-rc2
>>
>>
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you,
>> Platform Team
>>
>> --
>> Thusitha Dayaratne
>> Software Engineer
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Isuru Perera
> Associate Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Farasath Ahamed

[Nisala Nanayakkara]

Congratz fara !!! :D

On Mon, Oct 24, 2016 at 1:14 PM, Johann Nallathamby  wrote:

> Hi All,
>
> It's my pleasure to announce Farasath Ahamed as a WSO2 Committer. Farasath
>  has been a valuable contributor for WSO2 Identity Server product, and in
> recognition of his contribution to WSO2, he has been voted as a WSO2
> Committer.
>
> Farasath, congratulations and keep up the good work!
>
> Thanks & Regards.
>
> --
> Thanks & Regards,
>
> *Johann Dilantha Nallathamby*
> Technical Lead & Product Lead of WSO2 Identity Server
> Governance Technologies Team
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - *+9476950*
> Blog - *http://nallaa.wordpress.com *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Madawa Soysa

[Nisala Nanayakkara]

Congratz Madawa ! :D

On Tue, Oct 11, 2016 at 12:04 PM, Chandana Napagoda 
wrote:

> Hi Devs,
>
> It is my pleasure to welcome Madawa Soysa as a WSO2 Committer. Madawa has
> made some great contributions to WSO2 Governance Registry and WSO2
> Enterprise Store products during the last few months and in recognition of
> his commitment and contributions, he has been voted as a Committer for WSO2.
>
> Madawa, welcome aboard and keep up the good work.
>
> Best Regards,
> Chandana
>
> --
> *Chandana Napagoda*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.org
>
> *Email  :  chand...@wso2.com **Mobile : +94718169299
> <%2B94718169299>*
>
> *Blog  :http://cnapagoda.blogspot.com 
> | http://chandana.napagoda.com *
>
> *Linkedin : http://www.linkedin.com/in/chandananapagoda
> *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to get the page title of a dashboard page

[Nisala Nanayakkara]

Hi Kalpa,

I have created jira for this issue [1]. We will implement an api to get
dashboard-meta data information in the next release. So you can get
relevant meta data information of the dashboard using the api.

[1] - https://wso2.org/jira/browse/UES-1036

Thanks,
Nisala

On Mon, Aug 22, 2016 at 12:03 PM, Nipuna Chandradasa 
wrote:

> Hi Kalpa,
>
> We currently have a API to send dashboard name and id. But we don't have a
> api to get the page details. But we will create a jira for this and add
> this as an improvement on next release.
>
> Thank you,
>
> On Mon, Aug 22, 2016 at 11:29 AM, Kalpa Welivitigoda 
> wrote:
>
>> Hi devs,
>>
>> I have a dashboard with multiple pages. From a gadget in a page, I need
>> to get the current page title. What would be the recommended approach to do
>> this?
>>
>>
>>
>> --
>> Best Regards,
>>
>> Kalpa Welivitigoda
>> Senior Software Engineer, WSO2 Inc. http://wso2.com
>> Email: kal...@wso2.com
>> Mobile: +94776509215
>>
>> [image: http://wso2.com/signature] 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Nipuna Marcus
> *Software Engineer*
> WSO2 Inc.
> http://wso2.com/ - "lean . enterprise . middleware"
> Mobile : +94 (0) 713 667906
> nipu...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Nisala Nanayakkara]

Hi all,

I have scheduled a meeting on Wednesday afternoon to discuss about this
matter.

Thanks,
Nisala

On Mon, Aug 22, 2016 at 10:52 AM, Sinthuja Ragendran <sinth...@wso2.com>
wrote:

> Hi Susinda,
>
> On Mon, Aug 22, 2016 at 10:16 AM, Susinda Perera <susi...@wso2.com> wrote:
>
>>
>>
>> On Sun, Aug 21, 2016 at 5:06 PM, Sinthuja Ragendran <sinth...@wso2.com>
>> wrote:
>>
>>> Hi Nisala,
>>>
>>> So lets create a new repo for our new maven plugin, and lets include
>>> source there as per Susinda.
>>>
>>> @Susinda,
>>> Can you please elaborate bit more with what is the expected outcome when
>>> DevS based tooling using this maven plugin for DS? Because in the context,
>>> DS it self is a tool to create dashboard, gadgets, etc, therefore we don't
>>> intend to provide that sort of functionality with DevS. Therefore IMO we
>>> can maximum provide xml, js, css, jag file editors and lets them to create
>>> the structure of Capp from DevS. IMO creating such extension support will
>>> have considerable effort.
>>>
>>
>> Hi Sinthuja
>> Just had a chat with Nisala,
>> Expected outcome of DevS tooling was to make the developer's life easy on
>> creating dashboards, gadgets, layouts an themes. We have in built support
>> coming from eclipse for xml, html, css etc and we had jaggery editor with
>> code completion features. So I believe we can integrate these bits and
>> pieces and provide a IDE based tooling. As all developers are not command
>> line developers, I believe providing this kind of tooling would be useful
>> for general users.
>> As you already have maven build (packaging) tool and Capp tool for the
>> same, my suggestion is to introduce arch-type, then we can reuse use of
>> same arch-type and maven plugins to create the eclipse IDE plugin. So at
>> the end of the day we will have both command line and IDE based tooling.
>> WDYT?
>>
>
> Basically IMO IDE support is needed for creating custom gadgets and custom
> layouts. But the other parts such as creating dashboards, creating pages
> with default layouts, integrating gadgets into the dashboard pages, etc are
> provided from DS itself, and it's just drag and drop. And hence I don't
> think we need to provide same set of functionality which is already covered
> in DS, rather we need to focus on the point where users could create custom
> gadgets, and layouts which is the dev effort for the users in the context
> of DS. I don't think we can provide such DevS support feature for this
> release given the short time frame now.
>
> But anyhow lets have a discussion on this, come to our plan so that we can
> execute this on the future releases. @Nisala, please schedule a meeting
> Wednesday after noon or Thursday.
>
> Thanks,
> Sinthuja.
>
>
>> Thanks
>> Susinda
>>
>>
>>
>>
>>
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Fri, Aug 19, 2016 at 5:24 PM, Nisala Nanayakkara <nis...@wso2.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Thanks for prompt reply. I will arrange a meeting to discuss this
>>>> matter.
>>>>
>>>> Thanks,
>>>> Nisala
>>>>
>>>> On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera <susi...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Nisala
>>>>>
>>>>> We may need to create a new repo and host these maven plugins. As an
>>>>> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
>>>>> maintain the maven plugins. As we already have the maven plugins i think 
>>>>> we
>>>>> can easily build the DevStudio based tooling with using these plugins.
>>>>> Please arrange a time to discuss this.
>>>>>
>>>>> [1] - https://github.com/wso2/maven-tooling-esb
>>>>> [2] - https://github.com/wso2/maven-tooling-bps
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara <nis...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have implemented maven - plugins for each artifacts in WSO2
>>>>>> Dashboard Server. So there are four maven - plugins for
>>>>>> dashboards,gadgets,layouts and themes which can be used to generate a CAR
>>>>>> file consisting with these artifacts. But we are not very mu

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Nisala Nanayakkara]

Hi,

Thanks for prompt reply. I will arrange a meeting to discuss this matter.

Thanks,
Nisala

On Fri, Aug 19, 2016 at 10:52 AM, Susinda Perera <susi...@wso2.com> wrote:

> Hi Nisala
>
> We may need to create a new repo and host these maven plugins. As an
> example esb uses maven-tooling-esb[1] and bps uses maven-tooling-bps[2] to
> maintain the maven plugins. As we already have the maven plugins i think we
> can easily build the DevStudio based tooling with using these plugins.
> Please arrange a time to discuss this.
>
> [1] - https://github.com/wso2/maven-tooling-esb
> [2] - https://github.com/wso2/maven-tooling-bps
>
>
>
> On Thu, Aug 18, 2016 at 6:45 PM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi,
>>
>> I have implemented maven - plugins for each artifacts in WSO2 Dashboard
>> Server. So there are four maven - plugins for dashboards,gadgets,layouts
>> and themes which can be used to generate a CAR file consisting with these
>> artifacts. But we are not very much clear about where we have to maintain
>> these maven - plugins. Is it better to keep it within our carbon-dashboards
>> repository ? Or is it better to maintain these as a separate repository.
>>
>> @DevStudioTeam : Can you provide recommended way of maintaining these
>> maven-plugins ?
>>
>> Thanks,
>> Nisala
>>
>> On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera <susi...@wso2.com>
>> wrote:
>>
>>> Do we have tooling support for this new release, like create/edit/deploy
>>> gadgets/dashboards etc. If not shall we add this to roadmap. DevS team will
>>> be able to help on this task.
>>>
>>> Thanks
>>> Susinda
>>>
>>> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar <meg...@wso2.com>
>>> wrote:
>>>
>>>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>>>
>>>> WSO2 Dashboard Server team is pleased to announce the release of WSO2
>>>> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
>>>> fixes, improvements and tasks. You can download the distribution from [1]
>>>> and view the documentation at [2].
>>>> Bug
>>>>
>>>>- [UES-990 <https://wso2.org/jira/browse/UES-990>] - All the query
>>>>params get appended to the url when navigating via hierarchical menu
>>>>- [UES-1016 <https://wso2.org/jira/browse/UES-1016>] - Tenant ID is
>>>>always super tenant ID in Gadget Generation Wizard
>>>>- [UES-1018 <https://wso2.org/jira/browse/UES-1018>] - DS Console
>>>>differs from the WSO2 theme
>>>>- [UES-1022 <https://wso2.org/jira/browse/UES-1022>] - Product
>>>>version in footer is incorrect
>>>>- [UES-1023 <https://wso2.org/jira/browse/UES-1023>] - Create view
>>>>menu rendered incorrectly
>>>>- [UES-1028 <https://wso2.org/jira/browse/UES-1028>] - Creating
>>>>gadgets in third-party store - Thumbnail image does not show
>>>>
>>>> Improvement
>>>>
>>>>- [UES-970 <https://wso2.org/jira/browse/UES-970>] - Add download
>>>>functionality to gadgets listed
>>>>- [UES-995 <https://wso2.org/jira/browse/UES-995>] - Having a
>>>>landing page for a dashboard is optional
>>>>- [UES-1003 <https://wso2.org/jira/browse/UES-1003>] - Modify the
>>>>ES extension to not allow the assets to be editable in published asset
>>>>- [UES-1010 <https://wso2.org/jira/browse/UES-1010>] - Add shindig
>>>>features to get the hostName,port and tenant domain
>>>>- [UES-1012 <https://wso2.org/jira/browse/UES-1012>] - Store the
>>>>theme level properties to dashboard.json and retrieve these theme
>>>>properties while rendering the page
>>>>- [UES-1014 <https://wso2.org/jira/browse/UES-1014>] - Add new
>>>>gadget/layout button at the end of the gadget listing and layout 
>>>> listings
>>>>when user designs dashboard
>>>>- [UES-1015 <https://wso2.org/jira/browse/UES-1015>] - Dashboard
>>>>page loading icon for embeddable gadget feature
>>>>
>>>> Task
>>>>
>>>>- [UES-1005 <https://wso2.org/jira/browse/UES-1005>] - Provide
>>>>common repository for js libraries to use in gadgets
>>>>- [UES-1006 <https://wso2.org/jira/browse/UES-1006>] - 

Re: [Dev] [Announce] [Architecture] WSO2 Dashboard Server 2.1.0-Alpha Released!

[Nisala Nanayakkara]

Hi,

I have implemented maven - plugins for each artifacts in WSO2 Dashboard
Server. So there are four maven - plugins for dashboards,gadgets,layouts
and themes which can be used to generate a CAR file consisting with these
artifacts. But we are not very much clear about where we have to maintain
these maven - plugins. Is it better to keep it within our carbon-dashboards
repository ? Or is it better to maintain these as a separate repository.

@DevStudioTeam : Can you provide recommended way of maintaining these
maven-plugins ?

Thanks,
Nisala

On Mon, Aug 15, 2016 at 10:51 AM, Susinda Perera  wrote:

> Do we have tooling support for this new release, like create/edit/deploy
> gadgets/dashboards etc. If not shall we add this to roadmap. DevS team will
> be able to help on this task.
>
> Thanks
> Susinda
>
> On Fri, Aug 12, 2016 at 8:23 PM, Megala Uthayakumar 
> wrote:
>
>> WSO2 Dashboard Server 2.1.0-Alpha Released!
>>
>> WSO2 Dashboard Server team is pleased to announce the release of WSO2
>> Dashboard Server 2.1.0 Alpha. This release comes with the following bug
>> fixes, improvements and tasks. You can download the distribution from [1]
>> and view the documentation at [2].
>> Bug
>>
>>- [UES-990 ] - All the query
>>params get appended to the url when navigating via hierarchical menu
>>- [UES-1016 ] - Tenant ID is
>>always super tenant ID in Gadget Generation Wizard
>>- [UES-1018 ] - DS Console
>>differs from the WSO2 theme
>>- [UES-1022 ] - Product
>>version in footer is incorrect
>>- [UES-1023 ] - Create view
>>menu rendered incorrectly
>>- [UES-1028 ] - Creating
>>gadgets in third-party store - Thumbnail image does not show
>>
>> Improvement
>>
>>- [UES-970 ] - Add download
>>functionality to gadgets listed
>>- [UES-995 ] - Having a landing
>>page for a dashboard is optional
>>- [UES-1003 ] - Modify the ES
>>extension to not allow the assets to be editable in published asset
>>- [UES-1010 ] - Add shindig
>>features to get the hostName,port and tenant domain
>>- [UES-1012 ] - Store the
>>theme level properties to dashboard.json and retrieve these theme
>>properties while rendering the page
>>- [UES-1014 ] - Add new
>>gadget/layout button at the end of the gadget listing and layout listings
>>when user designs dashboard
>>- [UES-1015 ] - Dashboard page
>>loading icon for embeddable gadget feature
>>
>> Task
>>
>>- [UES-1005 ] - Provide common
>>repository for js libraries to use in gadgets
>>- [UES-1006 ] - Dashboard page
>>loading icon to show after all gadgets are loaded
>>- [UES-1007 ] - Fixed the
>>issue in PDF download feature in firefox browser
>>- [UES-1008 ] - Fixing issues
>>in running the dashboard server with samples
>>- [UES-1029 ] - Create Puppet
>>script for Dashboard Server Auto Deployment
>>
>> Reporting Issues
>>
>> Issues can be reported through the Public JIRA
>>  project for WSO2 Dashboard Server.
>>
>>
>> [1]- https://github.com/wso2/product-ds/releases/download/v2
>> .1.0-alpha/wso2ds-2.1.0-SNAPSHOT.zip
>>
>> [2]- https://docs.wso2.com/display/DS210/WSO2+Dashboard+Serv
>> er+Documentation
>>
>>
>> Thanks,
>>
>> Dashboard Server Team.
>>
>> --
>> Megala Uthayakumar
>>
>> Software Engineer
>> Mobile : 0779967122
>>
>> ___
>> Announce mailing list
>> annou...@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/announce
>>
>>
>
>
> --
> *Susinda Perera*
> Software Engineer
> B.Sc.(Eng), M.Sc(Computer Science), AMIE(SL)
> Mobile:(+94)716049075
> Blog: susinda.blogspot.com
> WSO2 Inc. http://wso2.com/
> Tel : 94 11 214 5345 Fax :94 11 2145300
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Shindig feature to get tenantDomain, Hostname and Port within a gadget

[Nisala Nanayakkara]

Hi,

Please note that we have added another shindig feature in order to provide
ability to get tenant domain, hostname and port within a gadget. You can
get the tenant domain by requiring identity feature and hostname, port by
requiring server feature as below.

*To get tenant domain*

Require identity feature - 
Then,
var tenantDomain;

wso2.gadgets.identity.getTenantDomain(function(tenantDomain){
this.tenantDomain = tenantDomain;
});

*To get hostname and port*

Require identity feature - 
Then,
var hostname;
wso2.gadgets.server.getTenantDomain(function(hostname){
this.hostname = hostname;
});

var port;

wso2.gadgets.server.getTenantDomain("{protocol}",function(port){
this.port = port;
});

Please note that you have to give appropriate protocol as "http" or "https"
in order to get relevant port.

Thanks,
Nisala

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Architecture] WSO2 Dashboard Server 2.1.0-M4 Released!

[Nisala Nanayakkara]

WSO2 Dashboard Server 2.1.0-M4 Released!

WSO2 Dashboard Server team is pleased to announce the release of WSO2
Dashboard Server 2.1.0 Milestone 4. This release comes with the following
bug fixes and features. You can download the distribution from [1].
Bug

   - [UES-971 ] - Gadgets are not
   rendering in tenant mode if the same gadget is not available in
   super-tenant store
   - [UES-972 ] - Advance UI elements
   does not work in chart wizard
   - [UES-973 ] - Remove the title
   bar in the view mode
   - [UES-987 ] - "undefined" color
   domain appears in chart preview in gadget generation wizard
   - [UES-988 ] - Line Chart Preview
   shows an extra incorrect point
   - [UES-989 ] - "Cannot read
   property 'style' of null" when editing User Preferences with Pubsub-2
   enabled

Improvement

   - [UES-974 ] - Make the security
   time-out of shindig to be configurable
   - [UES-985 ] - Treat dashboard
   theme as a personalization and persist within userspace rather than a cookie
   - [UES-994 ] - Shindig Feature to
   expose apis for getting dashboard name and ID

New Feature

   - [UES-991 ] - Multiple views
   support for page based on roles
   - [UES-992 ] - Download the
   dashboard page as pdf
   - [UES-993 ] - Support primitive
   edit operations (moving and delete gadgets) operations in the view mode

Task

   - [UES-968 ] - Move product-ds to
   kernel 4.4.6

Reporting Issues

Issues can be reported through the Public JIRA
 project for WSO2 Dashboard Server.


[1]-
https://github.com/wso2/product-ds/releases/download/v2.1.0-m4/wso2ds-2.1.0-M4.zip



Thanks,

Dashboard Server Team.


-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update - Provide runtime environment for jaggery apps in AS6

[Nisala Nanayakkara]

Hi KasunG,

Yes.This is the branch. Currently we are maintaining two branches as this
tomcat version(tomcat 8) will not work with carbon 4.4.x products due to
the tomcat API changes. So we have to maintain two branches now. But we
will move the current master to branch 0.12.x branch and merger
tomcat-8.0.x-jaggery to master. Then its a two different versions, not a
feature branch.

Thanks,
Nisala

On Mon, Jul 18, 2016 at 2:05 PM, KasunG Gajasinghe <kas...@wso2.com> wrote:

> Hi Nisala,
>
> On Thu, Jun 30, 2016 at 7:17 AM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> Please find the branch here.
>>
>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>
>
>
> From what I understood, this is a feature branch, is it not? Then, this
> does not really need a separate jenkins job since you will merge this into
> master soon. Please note that, you shouldn't have two diverged features in
> branches of the same repo.
>
> Thanks,
> KasunG
>
>
>>
>> Thanks,
>> Nisala
>>
>> On Thu, Jun 30, 2016 at 7:12 AM, Nisala Nanayakkara <nis...@wso2.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> We have created a seperate branch[1] with the changes required for
>>> providing runtime environment for jaggery apps in AS6. Currently there is
>>> no jenkins builder setup for this, Please get the 1.0.0-SNAPSHOT version by
>>> building the branch in local repo. Please inform me if there are any issues.
>>>
>>> Thanks,
>>> Nisala
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile:(+94)717600022
>> WSO2 Inc., http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
>
>
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

Hi Manjula,

Yes.Jaggery support will be inbuilt into the server with the release of
AS-6.0.0 next milestone. This email and documentation is provided to inform
the procedure of running jaggery apps in a pure tomcat server, not in the
AS-6.0.0. I will update the finalized documentation and configuration
details for AS-6.0.0 in a separate mail thread, once we finished the
fine-tuning process.

Thanks,
Nisala

On Mon, Jul 4, 2016 at 1:39 PM, Manjula Rathnayake <manju...@wso2.com>
wrote:

> Hi all,
>
> IIUC, when we release the next AS-6.0.0 milestone, jaggery support is
> inbuilt into the server. And users do not need to follow above instructions
> to copy jars etc. Please correct If it is not.
>
> thank you.
>
> On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran <sinth...@wso2.com>
> wrote:
>
>> Hi,
>>
>> Anyhow ultimately 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,
>>>
>>> Yes.We can do a performance round. Currently we manage the Tomcat
>>> Jaggery/ AS6 support code base under a new branch [1] in our jaggery
>>> repository. Current jaggery is based on tomcat version 7 and Tomcat Jaggery
>>> implementation is based on tomcat version 8. So there are some api changes
>>> in the jaggery level. So it is difficult to manage these codebases in same
>>> place.
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe <kas...@wso2.com>
>>> wrote:
>>>
>>>>
>>>> Good work Nisala.
>>>>
>>>> Can we also do a performance round to see whether there are any perf
>>>> gains 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:
>>>>
>>>>> Hi all,
>>>>>
>>>>> This is an update regarding the feature 'Provide Support to run
>>>>> Jaggery apps in Tomcat Server'.
>>>>>
>>>>> At present Jaggery scripts can only be executed in a jaggery server.
>>>>> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is 
>>>>> the
>>>>> Runtime Environment that hosts Jaggery applications. The goal of this
>>>>> feature is to provide support to run jaggery apps in a pure tomcat server
>>>>> without any modifications to the jaggery apps.This will enable developers
>>>>> to write Jaggery scripts and directly deploy them in apache tomcat server.
>>>>> So this will improve the flexibility of the jaggery apps.
>>>>>
>>>>> This is an extension for the Apache tomcat 8 to run the jaggery app
>>>>> without modifying it. Although this is implemented as a requirement of 
>>>>> WSO2
>>>>> Application Server 6, Users who want to run jaggery apps without jaggery
>>>>> server, can use this feature to run their jaggery apps in Apache tomcat
>>>>> server.
>>>>>
>>>>> I have attached the documentation and sample jaggery with this email.
>>>>> Please find these attachments and relevant jaggery branch here[1]. Please
>>>>> feel free to ask any questions.
>>>>>
>>>>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>>>>
>>>>> Thanks,
>>>>> Nisala
>>>>>
>>>>> --
>>>>> *Nisala Niroshana Nanayakkara,*
>>>>> Software Engineer
>>>>> Mobile:(+94)717600022
>>>>> WSO2 Inc., http://wso2.com/
>>>>>
>>>>> ___
>>>>> Dev mailing list
>>>>> Dev@wso2.org
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>>>> email: kasung AT spamfree wso2.com
>>>> linked-in: http://lk.linkedin.com/in/gajasinghe
>>>> blog: http://kasunbg.org
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Sinthuja Rajendran*
>> Technical Lead
>> WSO2, Inc.:http://wso2.com
>>
>> Blog: http://sinthu-rajan.blogspot.com/
>> Mobile: +94774273955
>>
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Manjula Rathnayaka
> Associate Technical Lead
> WSO2, Inc.
> Mobile:+94 77 743 1987
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

Hi Kasun,

Yes.We can do a performance round. Currently we manage the Tomcat Jaggery/
AS6 support code base under a new branch [1] in our jaggery repository.
Current jaggery is based on tomcat version 7 and Tomcat Jaggery
implementation is based on tomcat version 8. So there are some api changes
in the jaggery level. So it is difficult to manage these codebases in same
place.

Thanks,
Nisala

On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe <kas...@wso2.com> wrote:

>
> Good work Nisala.
>
> Can we also do a performance round to see whether there are any perf gains
> 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:
>
>> Hi all,
>>
>> This is an update regarding the feature 'Provide Support to run Jaggery
>> apps in Tomcat Server'.
>>
>> At present Jaggery scripts can only be executed in a jaggery server.
>> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is the
>> Runtime Environment that hosts Jaggery applications. The goal of this
>> feature is to provide support to run jaggery apps in a pure tomcat server
>> without any modifications to the jaggery apps.This will enable developers
>> to write Jaggery scripts and directly deploy them in apache tomcat server.
>> So this will improve the flexibility of the jaggery apps.
>>
>> This is an extension for the Apache tomcat 8 to run the jaggery app
>> without modifying it. Although this is implemented as a requirement of WSO2
>> Application Server 6, Users who want to run jaggery apps without jaggery
>> server, can use this feature to run their jaggery apps in Apache tomcat
>> server.
>>
>> I have attached the documentation and sample jaggery with this email.
>> Please find these attachments and relevant jaggery branch here[1]. Please
>> feel free to ask any questions.
>>
>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>
>> Thanks,
>> Nisala
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile:(+94)717600022
>> WSO2 Inc., http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
>
>
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Sharing a dashboard+gadgets across multiple tenants

[Nisala Nanayakkara]

Hi all,

I made the relevant changes and send a PR.

Thanks,
Nisala

On Fri, Jul 1, 2016 at 4:52 PM, Tanya Madurapperuma  wrote:

> Hi Dunith,
>
> There seems to be a regression issue introduced with gadget load ordering
> feature. We will fix this soon and update you.
> Sorry for the inconvenience caused.
>
> Thanks,
> Tanya
>
> On Fri, Jul 1, 2016 at 3:59 PM, Dunith Dhanushka  wrote:
>
>> Hi Tanya,
>>
>> Thanks for the quick response. My observations are below
>>
>> 1. Gadgets were not on the listing page.
>> 2. Gadgets did not render in view mode (Please see the attached
>> screenshot)
>>
>> I'll try with setting shareStore to true.
>>
>> Thanks,
>> Dunith
>>
>>
>> On Fri, Jul 1, 2016 at 3:52 PM, Tanya Madurapperuma 
>> wrote:
>>
>>> Hi Dunith,
>>>
>>> On Fri, Jul 1, 2016 at 3:42 PM, Dunith Dhanushka 
>>> wrote:
>>>
 Hi DS team,

 I have a dashboard and few gadgets deployed for super tenant. Now I
 need to share this dashboard+gadgets across multiple tenants.

 So I changed the dashboard settings and made the dashboard shareable.

 When I logged in as a tenant, I could only see the dashboard being
 shared. But gadgets were not there.

>>> What do you mean by gadgets were not there ? Is it in the gadget
>>> listing? or gadgets don't render in the view mode?
>>> In the shared dashboard feature, we only provide the viewing capability.
>>> Gadgets won't be available in the listing. Because it refers to the gadget
>>> in the super tenant store.
>>> I'm cc'ing Megala who implemented this feature for further
>>> clarifications.
>>>
>>> We have a config in designer.json as "shareStore" . IIRC if you set
>>> this to true it will share the super tenant store with other tenants.
>>> @ Megala : Could you please verify and update the thread.
>>>
>>> Thanks,
>>> Tanya
>>>

 My question is how can I make super tenant gadgets available in the
 tenant's dashboard as well?
 Is there a setting to share the store as well?


 Note: Tested above scenario with carbon-dashboards 1.0.20-SNAPSHOT

 --
 Regards,

 Dunith Dhanushka,
 Associate Technical Lead
 WSO2 Inc,

 Mobile - +94 71 8615744
 Blog - *https://medium.com/@dunithd *
 Twitter - @dunithd 

>>>
>>>
>>>
>>> --
>>> Tanya Madurapperuma
>>>
>>> Senior Software Engineer,
>>> WSO2 Inc. : wso2.com
>>> Mobile : +94718184439
>>> Blog : http://tanyamadurapperuma.blogspot.com
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Dunith Dhanushka,
>> Associate Technical Lead
>> WSO2 Inc,
>>
>> Mobile - +94 71 8615744
>> Blog - *https://medium.com/@dunithd *
>> Twitter - @dunithd 
>>
>
>
>
> --
> Tanya Madurapperuma
>
> Senior Software Engineer,
> WSO2 Inc. : wso2.com
> Mobile : +94718184439
> Blog : http://tanyamadurapperuma.blogspot.com
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Converting a HTML content into PDF using third party library

[Nisala Nanayakkara]

Hi all,

Currently, I am working on a feature in WSO2 Dashboard Server, which
involves in converting the dashboard page content with it's current
snapshot to be downloaded as a pdf file. While researching on this, I found
that there are several third party libraries such as jsPDF,PDFreactor which
can be used in this feature. Since jsPDF library has MIT license, I think
we can use it in our developments.

Do we already use such libraries that can be used to convert a html content
into pdf? If so, can you direct me with the necessary details. Then I can
re-use it without going to a new third party library.

Thanks,
Nisala

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Update - Provide runtime environment for jaggery apps in AS6

[Nisala Nanayakkara]

Hi all,

Please find the branch here.

[1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery

Thanks,
Nisala

On Thu, Jun 30, 2016 at 7:12 AM, Nisala Nanayakkara <nis...@wso2.com> wrote:

> Hi all,
>
> We have created a seperate branch[1] with the changes required for
> providing runtime environment for jaggery apps in AS6. Currently there is
> no jenkins builder setup for this, Please get the 1.0.0-SNAPSHOT version by
> building the branch in local repo. Please inform me if there are any issues.
>
> Thanks,
> Nisala
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>



-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Update - Provide runtime environment for jaggery apps in AS6

[Nisala Nanayakkara]

Hi all,

We have created a seperate branch[1] with the changes required for
providing runtime environment for jaggery apps in AS6. Currently there is
no jenkins builder setup for this, Please get the 1.0.0-SNAPSHOT version by
building the branch in local repo. Please inform me if there are any issues.

Thanks,
Nisala

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Failed to stop the deployment of Jaggery app using lifecycle listener in AS6

[Nisala Nanayakkara]

Hi,

As suggested in the code review, when there were issues in processing
jaggery.conf file, I tried to fail the deployment of the jaggery app by
throwing a runtime exception. But it did not fail the deployment of the
jaggery app. Are there any other methods to fail the jaggery app using its
lifecycle listener ?

Thanks,
Nisala

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Introducing Zip Unzip Functionality in Jaggery File Host Object

[Nisala Nanayakkara]

Hi all,

I have an use-case of zipping and unzipping functionality for one of my
ongoing improvement. Since it is difficult to achieve this task using
JavaScript. Once I discussed about this with my teammates, they said that
it is better to add these functionalities in Jaggery file hostobject. So
Shall I add this functionalities into Jaggery file hostobject ?

Please feel free to give any feedback about this matter.

Thanks,
Nisala

-- 
*Nisala Niroshana Nanayakkara,*
Software Engineer
Mobile:(+94)717600022
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Need AS 6.0.0 Pack

[Nisala Nanayakkara]

Hi all,

I have managed to build the product-as. I was using java7 before building
the product-as.So I moved to java8 using the command 'sudo
update-alternatives --config java'. But it doesn't update the JAVA_HOME
into java8.So I had to manually configure it.Thanks all for the quick
responses.

Thanks,
Nisala

On Thu, Jun 2, 2016 at 9:05 PM, Nisala Nanayakkara <nis...@wso2.com> wrote:

> Hi all,
>
> I am trying to build the product-as in order to get the AS-6.0.0 pack. But
> it gives the following error.
>
> *[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
> (default-compile) on project appserver-utils: Fatal error compiling:
> invalid target release: 1.8 -> [Help 1]*
>
> *org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
> (default-compile) on project appserver-utils: Fatal error compiling*
>
> *at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)*
>
> *at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)*
>
> *at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)*
>
> *at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)*
>
> *at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)*
>
> *at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)*
>
> *at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)*
>
> *at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)*
>
> *at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)*
>
> *at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)*
>
> *at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)*
>
> *at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)*
>
> *at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
>
> *at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)*
>
> *at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
>
> *at java.lang.reflect.Method.invoke(Method.java:606)*
>
> *at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)*
>
> *at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)*
>
> *at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)*
>
> *at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)*
>
> *Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error
> compiling*
>
> *at
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:897)*
>
> *at
> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)*
>
> *at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)*
>
> *at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)*
>
> *... 19 more*
>
> *Caused by: org.codehaus.plexus.compiler.CompilerException: invalid target
> release: 1.8*
>
> *at
> org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:172)*
>
> *at
> org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:171)*
>
> *at
> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:886)*
>
> *... 22 more*
>
> *Caused by: java.lang.IllegalArgumentException: invalid target release:
> 1.8*
>
> *at
> com.sun.tools.javac.main.RecognizedOptions$GrumpyHelper.error(RecognizedOptions.java:88)*
>
> *at
> com.sun.tools.javac.main.RecognizedOptions$10.process(RecognizedOptions.java:359)*
>
> *at
> com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:242)*
>
> *at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:199)*
>
> *at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:68)*
>
> *at
> org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:124)*
>
> *... 24 more*
>
>
> Then I download the built pack of AS 6.0.0 from jenkins. When I run it, it
> gives the following error.
>
> *02-Jun-2016 20:32:01.358 SEVERE [main]
> org.apache.tomcat.util.digester.Digester.startElement Begin event threw

Re: [Dev] Need AS 6.0.0 Pack

[Nisala Nanayakkara]

Hi Megala,

Thanks for the quick response. I will check it.

Thanks,
Nisala

On Thu, Jun 2, 2016 at 9:11 PM, Megala Uthayakumar <meg...@wso2.com> wrote:

> Hi Nisala,
>
> Can you check the mail with the subject "[Dev][AS] Help to build
> product-as". Product-as 6.0.0 requires jdk 1.8.
>
> Thanks.
>
> Regards,
> Megala
>
> On Thu, Jun 2, 2016 at 9:05 PM, Nisala Nanayakkara <nis...@wso2.com>
> wrote:
>
>> Hi all,
>>
>> I am trying to build the product-as in order to get the AS-6.0.0 pack.
>> But it gives the following error.
>>
>> *[ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
>> (default-compile) on project appserver-utils: Fatal error compiling:
>> invalid target release: 1.8 -> [Help 1]*
>>
>> *org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>> execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
>> (default-compile) on project appserver-utils: Fatal error compiling*
>>
>> *at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)*
>>
>> *at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)*
>>
>> *at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)*
>>
>> *at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)*
>>
>> *at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)*
>>
>> *at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)*
>>
>> *at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)*
>>
>> *at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)*
>>
>> *at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)*
>>
>> *at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)*
>>
>> *at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)*
>>
>> *at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)*
>>
>> *at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
>>
>> *at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)*
>>
>> *at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
>>
>> *at java.lang.reflect.Method.invoke(Method.java:606)*
>>
>> *at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)*
>>
>> *at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)*
>>
>> *at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)*
>>
>> *at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)*
>>
>> *Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error
>> compiling*
>>
>> *at
>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:897)*
>>
>> *at
>> org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)*
>>
>> *at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)*
>>
>> *at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)*
>>
>> *... 19 more*
>>
>> *Caused by: org.codehaus.plexus.compiler.CompilerException: invalid
>> target release: 1.8*
>>
>> *at
>> org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:172)*
>>
>> *at
>> org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:171)*
>>
>> *at
>> org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:886)*
>>
>> *... 22 more*
>>
>> *Caused by: java.lang.IllegalArgumentException: invalid target release:
>> 1.8*
>>
>> *at
>> com.sun.tools.javac.main.RecognizedOptions$GrumpyHelper.error(RecognizedOptions.java:88)*
>>
>> *at
>> com.sun.tools.javac.main.RecognizedOptions$10.process(RecognizedOptions.java:359)*
>>
>> *at
>> com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:242)*
>>
>> *at com.sun.tools.javac.

[Dev] Need AS 6.0.0 Pack

[Nisala Nanayakkara]

Hi all,

I am trying to build the product-as in order to get the AS-6.0.0 pack. But
it gives the following error.

*[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
(default-compile) on project appserver-utils: Fatal error compiling:
invalid target release: 1.8 -> [Help 1]*

*org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
(default-compile) on project appserver-utils: Fatal error compiling*

*at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)*

*at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)*

*at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)*

*at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)*

*at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)*

*at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)*

*at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)*

*at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)*

*at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)*

*at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)*

*at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)*

*at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)*

*at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*

*at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)*

*at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*

*at java.lang.reflect.Method.invoke(Method.java:606)*

*at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)*

*at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)*

*at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)*

*at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)*

*Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error
compiling*

*at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:897)*

*at
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)*

*at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)*

*at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)*

*... 19 more*

*Caused by: org.codehaus.plexus.compiler.CompilerException: invalid target
release: 1.8*

*at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:172)*

*at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:171)*

*at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:886)*

*... 22 more*

*Caused by: java.lang.IllegalArgumentException: invalid target release: 1.8*

*at
com.sun.tools.javac.main.RecognizedOptions$GrumpyHelper.error(RecognizedOptions.java:88)*

*at
com.sun.tools.javac.main.RecognizedOptions$10.process(RecognizedOptions.java:359)*

*at
com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:242)*

*at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:199)*

*at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:68)*

*at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:124)*

*... 24 more*


Then I download the built pack of AS 6.0.0 from jenkins. When I run it, it
gives the following error.

*02-Jun-2016 20:32:01.358 SEVERE [main]
org.apache.tomcat.util.digester.Digester.startElement Begin event threw
error*

*java.lang.UnsupportedClassVersionError:
org/wso2/appserver/configuration/listeners/ServerConfigurationLoader :
Unsupported major.minor version 52.0*

*at java.lang.ClassLoader.defineClass1(Native Method)*

*at java.lang.ClassLoader.defineClass(ClassLoader.java:800)*

*at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)*

*at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)*

*at java.net.URLClassLoader.access$100(URLClassLoader.java:71)*

*at java.net.URLClassLoader$1.run(URLClassLoader.java:361)*

*at java.net.URLClassLoader$1.run(URLClassLoader.java:355)*

*at java.security.AccessController.doPrivileged(Native Method)*

*at java.net.URLClassLoader.findClass(URLClassLoader.java:354)*

*at java.lang.ClassLoader.loadClass(ClassLoader.java:425)*

*at java.lang.ClassLoader.loadClass(ClassLoader.java:358)*

*at
org.apache.tomcat.util.digester.ObjectCreateRule.begin(ObjectCreateRule.java:116)*

*

[Dev] [WSO2-ESB]Script Mediator not working properly when iterating

[Nisala Nanayakkara]

Hi,

I am trying to convert json array to an xml using script mediator,in which
I am using

/script
 ![CDATA[



*for(var i=0;i
parametersArray.length;i++){
Parameters += sub1:Parameters; Parameters += 
sub:Id+parametersArray[i].Id+/sub:Id;
Parameters += 
sub:Value+parametersArray[i].Value/sub:Value;
Parameters +=  /sub1:Parameters; } *
/script
]]

However, in the XML we get #60 instead of . How can overcome this
issue ??

Thanks
-- 

*Best Regards,Nisala Niroshana Nanayakkara,*
*Bsc. Eng Undergraduate | Department of Computer Science  Engineering |
University of Moratuwa | Sri Lanka*

*Intern Software Engineer | WSO2 Lanka(pvt) Ltd *
*Director | Leo Club of University of Moratuwa.*
*Mobile | +94717600022*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC-2015] Proposal 8 : WSO2 CEP Based Throttling for API Manager

[Nisala Nanayakkara]

Hi,

I am Nisala Niroshana ,an Undergraduate from Department of Computer Science
and Engineering, University of Moratuwa. Currently I am working as an
intern at WSO2.I went through the GSoC proposal list and interested in
proposal [1]. Currently I am working in API Manager team and already familiar
with WSO2 CEP and Siddhi while working on my fast track training project.

So I am looking forward to contribute for this project.

Thanks,
Nisala




-- 

*Best Regards,Nisala Niroshana Nanayakkara,*
*Bsc. Eng Undergraduate | Department of Computer Science  Engineering |
University of Moratuwa | Sri Lanka*

*Intern Software Engineer | WSO2 Lanka(pvt) Ltd *
*Director | Leo Club of University of Moratuwa.*
*Mobile | +94717600022*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSoC-2015] Proposal 8 : WSO2 CEP Based Throttling for API Manager

[Nisala Nanayakkara]

Hi,

I am Nisala Niroshana ,an Undergraduate from Department of Computer Science
and Engineering, University of Moratuwa. Currently I am working as an
intern at WSO2.I went through the GSoC proposal list and interested in
proposal [1]. Currently I am working in API Manager team and already familiar
with WSO2 CEP and Siddhi while working on my fast track training project.

So I am looking forward to contribute for this project.

[1]-
https://docs.wso2.com/display/GSoC/Project+Proposals+for+2015#ProjectProposalsfor2015-Proposal8:WSO2CEPBasedThrottlingforAPIManager

Thanks,
Nisala

-- 

*Best Regards,Nisala Niroshana Nanayakkara,*
*Bsc. Eng Undergraduate | Department of Computer Science  Engineering |
University of Moratuwa | Sri Lanka*

*Intern Software Engineer | WSO2 Lanka(pvt) Ltd *
*Director | Leo Club of University of Moratuwa.*
*Mobile | +94717600022*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Problem with uploading API Image in 'Add API' Rest Resource

[Nisala Nanayakkara]

Hi,

I am using Rest resources given in [1] to generate a sampleAPI ,if there is
no APIs in the API Manger. I have used addAPI rest resource to add the
sample API..But it did not upload the API image in to the registry and
default image was set as the api image.

Did anyone use those rest resources and get the same error  ??

[1]-https://docs.wso2.com/display/AM180/Publisher+APIs

Thanks,
Nisala

-- 

*Best Regards,Nisala Niroshana Nanayakkara,*
*Bsc. Eng Undergraduate | Department of Computer Science  Engineering |
University of Moratuwa | Sri Lanka*

*Intern Software Engineer | WSO2 Lanka(pvt) Ltd *
*Director | Leo Club of University of Moratuwa.*
*Mobile | +94717600022*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Integration New Test Module - BUILD FAILURE

[Nisala Nanayakkara]

Thanks for the help..I will try it.

Thanks,
Nisala

On Mon, Feb 23, 2015 at 3:33 PM, Chanuka Dissanayake chan...@wso2.com
wrote:

 Hi Nisala,

 You get this error because it cannot find the wso2 AM 1.9.0 product zip
 file in the particular relative path.

 in parallel to your integration folder, create another folder with the
 name distribution. Inside that, create a folder with the name target
 and add the WSO2 AM 1.9.0 zip file to that.

 In tree view, it's like following.

 integration
 distribution
  |target
   |wso2am-1.9.0.zip

 Regards,
 Chanuka.

 On Mon, Feb 23, 2015 at 3:25 PM, Krishantha Samaraweera 
 krishan...@wso2.com wrote:

 Did APIM distribution created successfully ? can you check whether the
 distribution is there in the local .m2 repo.

 Thanks,
 Krishantha.

 On Mon, Feb 23, 2015 at 2:51 PM, Nisala Nanayakkara nis...@wso2.com
 wrote:

 When I tried to build the POM file in the directory
 turing/apimgt/1.9.0/modules/integration, It gives the following error
 message,




 *Failed to execute goal
 org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack
 (unpack-mar-jks) on project org.wso2.carbon.am.backend.integration.test:
 Unable to find artifact. Failure to find org.wso2.am:wso2am:zip:1.9.0 in
 http://maven.wso2.org/nexus/content/repositories/releases/
 http://maven.wso2.org/nexus/content/repositories/releases/ was cached in
 the local repository, resolution will not be reattempted until the update
 interval of wso2.releases has elapsed or updates are forced*
 Did anybody get the same error ??


 Thanks,
 Nisala
 --

 *Best Regards,Nisala Niroshana Nanayakkara,*
 *Bsc. Eng Undergraduate | Department of Computer Science  Engineering |
 University of Moratuwa | Sri Lanka*

 *Intern Software Engineer | WSO2 Lanka(pvt) Ltd *
 *Director | Leo Club of University of Moratuwa.*
 *Mobile | +94717600022*

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




 --
 Krishantha Samaraweera
 Senior Technical Lead - Test Automation
 Mobile: +94 77 7759918
 WSO2, Inc.; http://wso2.com/
 lean . enterprise . middlewear.

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




 --
 Chanuka Dissanayake
 *Software Engineer | **WSO2 Inc.*; http://wso2.com

 Mobile: +94 71 33 63 596
 Email: chan...@wso2.com




-- 

*Best Regards,Nisala Niroshana Nanayakkara,*
*Bsc. Eng Undergraduate | Department of Computer Science  Engineering |
University of Moratuwa | Sri Lanka*

*Intern Software Engineer | WSO2 Lanka(pvt) Ltd *
*Director | Leo Club of University of Moratuwa.*
*Mobile | +94717600022*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Integration New Test Module - BUILD FAILURE

[Nisala Nanayakkara]

When I tried to build the POM file in the directory
turing/apimgt/1.9.0/modules/integration, It gives the following error
message,




*Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack
(unpack-mar-jks) on project org.wso2.carbon.am.backend.integration.test:
Unable to find artifact. Failure to find org.wso2.am:wso2am:zip:1.9.0 in
http://maven.wso2.org/nexus/content/repositories/releases/
http://maven.wso2.org/nexus/content/repositories/releases/ was cached in
the local repository, resolution will not be reattempted until the update
interval of wso2.releases has elapsed or updates are forced*
Did anybody get the same error ??


Thanks,
Nisala
-- 

*Best Regards,Nisala Niroshana Nanayakkara,*
*Bsc. Eng Undergraduate | Department of Computer Science  Engineering |
University of Moratuwa | Sri Lanka*

*Intern Software Engineer | WSO2 Lanka(pvt) Ltd *
*Director | Leo Club of University of Moratuwa.*
*Mobile | +94717600022*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SVN error when trying to checkout source from Turing chunk 11

[Nisala Nanayakkara]

I got the same error, when I tried to build the API-Manager 1.8.0 using
turing-chunk14.

Thanks

On Thu, Feb 5, 2015 at 6:23 PM, Farasath Ahamed farasa...@wso2.com wrote:


 Hi,

 I am trying to build IS 5.0.0 following [1] from the documentation. While
 checking out the product source using the svn command

 svn checkout
 https://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk11/
 wso2-products
 the checkout fails after running for a few mins with a

 svn: E120104: ra_serf: An error occurred during decompression, error.

 I think this is something related to the svn client. I searched online but
 didn't get an answer.

 Has anyone come across this error? is there a solution for this?

 Is there any alternative way to checkout the source(like git) and build
 the product?

 [1] https://docs.wso2.com/display/IS500/Building+from+Source


 --
 *Farasath Ahamed*
 Software Engineering Intern
 WSO2 Inc.; http://wso2.com

 Mobile: +94 777 603 866
 E-Mail:  farasath http://goog_1999535192a...@wso2.com

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




-- 

*Best Regards,Nisala Niroshana Nanayakkara,*
*Bsc. Eng Undergraduate | Department of Computer Science  Engineering |
University of Moratuwa | Sri Lanka*

*Intern Software Engineer | WSO2 Lanka(pvt) Ltd *
*Director | Leo Club of University of Moratuwa.*
*Mobile | +94717600022*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev