Re: [Dev] Summarization of JSON data in DAS

[Lahiru Madushanka]

Hi Nirmal,

Documentation says arbitrary data support can be used with wso2event input
format. But in my case its "JSON".
Custom event receiver will be an option. But is there a way I can do this
without writing a custom event receiver ?

Thanks for the help.

Regards,
Lahiru

On Sat, Jul 8, 2017 at 10:02 AM, Nirmal Fernando  wrote:

> Check on arbitrary data support https://docs.wso2.com/
> display/DAS310/Input+Mapping+Types
>
> On Sat, Jul 8, 2017 at 7:48 AM, Lahiru Madushanka 
> wrote:
>
>> Hi all,
>>
>> I have a requirement where data values published to DAS are not
>> predefined (dynamic)
>> ( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
>> Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores": 4}
>> This JSON string will be changed with no of cores in the PC which pushes
>> the data.
>>
>> Is there a way I can write a summarization query in siddhiql to take
>> average of average corePercentages for a time interval. (first take avg of
>> percentage values and then average it over time )
>>
>> Thanks
>> Lahiru
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Technical Lead, WSO2 Inc.
> Mobile: +94715779733 <+94%2071%20577%209733>
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Summarization of JSON data in DAS

[Nirmal Fernando]

Well the question is about; taking averages; yes it's certainly possible
with Siddhi. https://docs.wso2.com/display/DAS310/Siddhi+Query+Language

On Sat, Jul 8, 2017 at 10:02 AM, Nirmal Fernando  wrote:

> Check on arbitrary data support https://docs.wso2.com/
> display/DAS310/Input+Mapping+Types
>
> On Sat, Jul 8, 2017 at 7:48 AM, Lahiru Madushanka 
> wrote:
>
>> Hi all,
>>
>> I have a requirement where data values published to DAS are not
>> predefined (dynamic)
>> ( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
>> Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores": 4}
>> This JSON string will be changed with no of cores in the PC which pushes
>> the data.
>>
>> Is there a way I can write a summarization query in siddhiql to take
>> average of average corePercentages for a time interval. (first take avg of
>> percentage values and then average it over time )
>>
>> Thanks
>> Lahiru
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Technical Lead, WSO2 Inc.
> Mobile: +94715779733 <+94%2071%20577%209733>
> Blog: http://nirmalfdo.blogspot.com/
>
>
>


-- 

Thanks & regards,
Nirmal

Technical Lead, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Summarization of JSON data in DAS

[Nirmal Fernando]

Check on arbitrary data support
https://docs.wso2.com/display/DAS310/Input+Mapping+Types

On Sat, Jul 8, 2017 at 7:48 AM, Lahiru Madushanka 
wrote:

> Hi all,
>
> I have a requirement where data values published to DAS are not predefined
> (dynamic)
> ( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
> Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores": 4}
> This JSON string will be changed with no of cores in the PC which pushes
> the data.
>
> Is there a way I can write a summarization query in siddhiql to take
> average of average corePercentages for a time interval. (first take avg of
> percentage values and then average it over time )
>
> Thanks
> Lahiru
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Thanks & regards,
Nirmal

Technical Lead, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to build a connector?

[Rajkumar Rajaratnam]

Yeah, but it doesn't give an impression that it won't work with maven >
3.0.5. So better to reword it.

On Sat, Jul 8, 2017 at 12:10 AM, Rajjaz Mohammed  wrote:

> Hi Rajkumar,
>
> In the doc[1] we mentioned that it's tested with Maven 3.0.5.
>
> [1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+
> Connector#WritingaConnector-CreatetheMavenprojecttemplate
>
> On Sat, Jul 8, 2017 at 9:20 AM, Rajkumar Rajaratnam 
> wrote:
>
>> Thanks Hasitha.
>>
>> I was using maven 3.3.9. Downgraded it to 3.0.5 and it builds now.
>>
>> So we need to mention in the doc [1] that this won't build with maven
>> version > 3.0.5
>>
>> [1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector
>>
>> Thanks,
>> Raj.
>>
>>
>> On Fri, Jul 7, 2017 at 11:37 PM, Hasitha Jayasundara <
>> hasithajayasunda...@gmail.com> wrote:
>>
>>> Hi Rajkumar,
>>>
>>> Works fine with
>>>
>>> Apache Maven 3.0.5
>>> Java version: 1.8.0_131, vendor: Oracle Corporation
>>>
>>> Thanks
>>>
>>> On Sat, Jul 8, 2017 at 8:52 AM, Rajkumar Rajaratnam 
>>> wrote:
>>>
 I'm trying to build this connector https://github.com/w
 so2-extensions/esb-connector-gmail

 It's failing - see below. Do we need to do anything special to build
 this other than doing mvn clean install?


 [INFO] Building WSO2 Carbon - Mediation Library Connector For Gmail
 3.0.6-SNAPSHOT
 [INFO] 
 
 [WARNING] The POM for org.apache.bsf:bsf-all:jar:3.0 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.http.servlet:jar:1.0.200.v20090520-1800 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.osgi:org.eclipse.o
 sgi.services:jar:3.2.0.v20090520-1800 is missing, no dependency
 information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.simpleconfigurator:jar:1.0.100.v20090520-1905 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.util:jar:1.0.100.v20090520-1800 is missing, no dependency
 information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.ds:jar:1.1.0.v20090520-1800 is missing, no dependency
 information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.jsp.jasper:jar:1.0.200.v20090520-1800 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:javax.serv
 let.jsp:jar:2.0.0.v200806031607 is missing, no dependency information
 available
 [WARNING] The POM for org.eclipse.equinox:org.apache
 .jasper:jar:5.5.17.v200806031609 is missing, no dependency information
 available
 [WARNING] The POM for org.eclipse.equinox:org.apache
 .commons.el:jar:1.0.0.v200806031608 is missing, no dependency
 information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.app:jar:1.2.0.v20090520-1800 is missing, no dependency
 information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.concurrent:jar:1.0.0.v20090520-1800 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.frameworkadmin:jar:1.0.100.v20090520-1905 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.frameworkadmin.equinox:jar:1.0.100.v20090520-1905 is
 missing, no dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.p2.artifact.repository:jar:1.0.100.v20090520-1905 is
 missing, no dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.p2.core:jar:1.0.100.v20090520-1905 is missing, no dependency
 information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.p2.director:jar:1.0.100.v20090520-1905 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.p2.director.app:jar:1.0.100.v20090521-1912 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.p2.directorywatcher:jar:1.0.100.v20090520-1905 is missing,
 no dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.p2.engine:jar:1.0.100.v20090520-1905 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.p2.exemplarysetup:jar:1.0.100.v20090520-1905 is missing, no
 dependency information available
 [WARNING] The POM for org.eclipse.equinox:org.eclips
 e.equinox.p2.extensionlocation:jar:1.0.100.v20090520-1905 is missing,
 no dependency information availabl

Re: [Dev] How to build a connector?

[Rajjaz Mohammed]

Hi Rajkumar,

In the doc[1] we mentioned that it's tested with Maven 3.0.5.

[1]
https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector#WritingaConnector-CreatetheMavenprojecttemplate

On Sat, Jul 8, 2017 at 9:20 AM, Rajkumar Rajaratnam 
wrote:

> Thanks Hasitha.
>
> I was using maven 3.3.9. Downgraded it to 3.0.5 and it builds now.
>
> So we need to mention in the doc [1] that this won't build with maven
> version > 3.0.5
>
> [1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector
>
> Thanks,
> Raj.
>
>
> On Fri, Jul 7, 2017 at 11:37 PM, Hasitha Jayasundara <
> hasithajayasunda...@gmail.com> wrote:
>
>> Hi Rajkumar,
>>
>> Works fine with
>>
>> Apache Maven 3.0.5
>> Java version: 1.8.0_131, vendor: Oracle Corporation
>>
>> Thanks
>>
>> On Sat, Jul 8, 2017 at 8:52 AM, Rajkumar Rajaratnam 
>> wrote:
>>
>>> I'm trying to build this connector https://github.com/w
>>> so2-extensions/esb-connector-gmail
>>>
>>> It's failing - see below. Do we need to do anything special to build
>>> this other than doing mvn clean install?
>>>
>>>
>>> [INFO] Building WSO2 Carbon - Mediation Library Connector For Gmail
>>> 3.0.6-SNAPSHOT
>>> [INFO] 
>>> 
>>> [WARNING] The POM for org.apache.bsf:bsf-all:jar:3.0 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.http.servlet:jar:1.0.200.v20090520-1800 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.osgi:org.eclipse.o
>>> sgi.services:jar:3.2.0.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.simpleconfigurator:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.util:jar:1.0.100.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.ds:jar:1.1.0.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.jsp.jasper:jar:1.0.200.v20090520-1800 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:javax.serv
>>> let.jsp:jar:2.0.0.v200806031607 is missing, no dependency information
>>> available
>>> [WARNING] The POM for org.eclipse.equinox:org.apache
>>> .jasper:jar:5.5.17.v200806031609 is missing, no dependency information
>>> available
>>> [WARNING] The POM for org.eclipse.equinox:org.apache
>>> .commons.el:jar:1.0.0.v200806031608 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.app:jar:1.2.0.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.concurrent:jar:1.0.0.v20090520-1800 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.frameworkadmin:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.frameworkadmin.equinox:jar:1.0.100.v20090520-1905 is missing,
>>> no dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.artifact.repository:jar:1.0.100.v20090520-1905 is missing,
>>> no dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.core:jar:1.0.100.v20090520-1905 is missing, no dependency
>>> information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.director:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.director.app:jar:1.0.100.v20090521-1912 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.directorywatcher:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.engine:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.exemplarysetup:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.extensionlocation:jar:1.0.100.v20090520-1905 is missing,
>>> no dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.jarprocessor:jar:1.0.100.v20090520-1905 is missing, no
>>> dependency information available
>>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>>> e.equinox.p2.metadata.generator:jar:1.0.100.v20090520-

Re: [Dev] How to build a connector?

[Rajkumar Rajaratnam]

Thanks Hasitha.

I was using maven 3.3.9. Downgraded it to 3.0.5 and it builds now.

So we need to mention in the doc [1] that this won't build with maven
version > 3.0.5

[1] https://docs.wso2.com/display/ESBCONNECTORS/Writing+a+Connector

Thanks,
Raj.


On Fri, Jul 7, 2017 at 11:37 PM, Hasitha Jayasundara <
hasithajayasunda...@gmail.com> wrote:

> Hi Rajkumar,
>
> Works fine with
>
> Apache Maven 3.0.5
> Java version: 1.8.0_131, vendor: Oracle Corporation
>
> Thanks
>
> On Sat, Jul 8, 2017 at 8:52 AM, Rajkumar Rajaratnam 
> wrote:
>
>> I'm trying to build this connector https://github.com/w
>> so2-extensions/esb-connector-gmail
>>
>> It's failing - see below. Do we need to do anything special to build this
>> other than doing mvn clean install?
>>
>>
>> [INFO] Building WSO2 Carbon - Mediation Library Connector For Gmail
>> 3.0.6-SNAPSHOT
>> [INFO] 
>> 
>> [WARNING] The POM for org.apache.bsf:bsf-all:jar:3.0 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.http.servlet:jar:1.0.200.v20090520-1800 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.osgi:org.eclipse.o
>> sgi.services:jar:3.2.0.v20090520-1800 is missing, no dependency
>> information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.simpleconfigurator:jar:1.0.100.v20090520-1905 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.util:jar:1.0.100.v20090520-1800 is missing, no dependency
>> information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.ds:jar:1.1.0.v20090520-1800 is missing, no dependency
>> information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.jsp.jasper:jar:1.0.200.v20090520-1800 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:javax.serv
>> let.jsp:jar:2.0.0.v200806031607 is missing, no dependency information
>> available
>> [WARNING] The POM for org.eclipse.equinox:org.apache
>> .jasper:jar:5.5.17.v200806031609 is missing, no dependency information
>> available
>> [WARNING] The POM for org.eclipse.equinox:org.apache
>> .commons.el:jar:1.0.0.v200806031608 is missing, no dependency
>> information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.app:jar:1.2.0.v20090520-1800 is missing, no dependency
>> information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.concurrent:jar:1.0.0.v20090520-1800 is missing, no dependency
>> information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.frameworkadmin:jar:1.0.100.v20090520-1905 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.frameworkadmin.equinox:jar:1.0.100.v20090520-1905 is missing,
>> no dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.artifact.repository:jar:1.0.100.v20090520-1905 is missing,
>> no dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.core:jar:1.0.100.v20090520-1905 is missing, no dependency
>> information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.director:jar:1.0.100.v20090520-1905 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.director.app:jar:1.0.100.v20090521-1912 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.directorywatcher:jar:1.0.100.v20090520-1905 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.engine:jar:1.0.100.v20090520-1905 is missing, no dependency
>> information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.exemplarysetup:jar:1.0.100.v20090520-1905 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.extensionlocation:jar:1.0.100.v20090520-1905 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.jarprocessor:jar:1.0.100.v20090520-1905 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.metadata.generator:jar:1.0.100.v20090520-1905 is missing,
>> no dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.metadata:jar:1.0.100.v20090520-1905 is missing, no
>> dependency information available
>> [WARNING] The POM for org.eclipse.equinox:org.eclips
>> e.equinox.p2.metadata.repository:jar:1.0.100.v20090520-1905 is missing,
>> no dependency informatio

Re: [Dev] How to build a connector?

[Hasitha Jayasundara]

Hi Rajkumar,

Works fine with

Apache Maven 3.0.5
Java version: 1.8.0_131, vendor: Oracle Corporation

Thanks

On Sat, Jul 8, 2017 at 8:52 AM, Rajkumar Rajaratnam 
wrote:

> I'm trying to build this connector https://github.com/
> wso2-extensions/esb-connector-gmail
>
> It's failing - see below. Do we need to do anything special to build this
> other than doing mvn clean install?
>
>
> [INFO] Building WSO2 Carbon - Mediation Library Connector For Gmail
> 3.0.6-SNAPSHOT
> [INFO] 
> 
> [WARNING] The POM for org.apache.bsf:bsf-all:jar:3.0 is missing, no
> dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.http.servlet:jar:1.0.200.v20090520-1800 is missing, no
> dependency information available
> [WARNING] The POM for org.eclipse.osgi:org.eclipse.
> osgi.services:jar:3.2.0.v20090520-1800 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.
> simpleconfigurator:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.util:jar:1.0.100.v20090520-1800 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.ds:jar:1.1.0.v20090520-1800 is missing, no dependency
> information available
> [WARNING] The POM for 
> org.eclipse.equinox:org.eclipse.equinox.jsp.jasper:jar:1.0.200.v20090520-1800
> is missing, no dependency information available
> [WARNING] The POM for 
> org.eclipse.equinox:javax.servlet.jsp:jar:2.0.0.v200806031607
> is missing, no dependency information available
> [WARNING] The POM for 
> org.eclipse.equinox:org.apache.jasper:jar:5.5.17.v200806031609
> is missing, no dependency information available
> [WARNING] The POM for 
> org.eclipse.equinox:org.apache.commons.el:jar:1.0.0.v200806031608
> is missing, no dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.app:jar:1.2.0.v20090520-1800 is missing, no dependency
> information available
> [WARNING] The POM for 
> org.eclipse.equinox:org.eclipse.equinox.concurrent:jar:1.0.0.v20090520-1800
> is missing, no dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.
> frameworkadmin:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.
> frameworkadmin.equinox:jar:1.0.100.v20090520-1905 is missing, no
> dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.artifact.
> repository:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.p2.core:jar:1.0.100.v20090520-1905 is missing, no
> dependency information available
> [WARNING] The POM for 
> org.eclipse.equinox:org.eclipse.equinox.p2.director:jar:1.0.100.v20090520-1905
> is missing, no dependency information available
> [WARNING] The POM for 
> org.eclipse.equinox:org.eclipse.equinox.p2.director.app:jar:1.0.100.v20090521-1912
> is missing, no dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.
> directorywatcher:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.p2.engine:jar:1.0.100.v20090520-1905 is missing, no
> dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.
> exemplarysetup:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.
> extensionlocation:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.
> jarprocessor:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.metadata.
> generator:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for 
> org.eclipse.equinox:org.eclipse.equinox.p2.metadata:jar:1.0.100.v20090520-1905
> is missing, no dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.eclipse.equinox.p2.metadata.
> repository:jar:1.0.100.v20090520-1905 is missing, no dependency
> information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.p2.reconciler.dropins:jar:1.0.100.v20090520-1905 is
> missing, no dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.p2.publisher:jar:1.0.0.v20090521-1912 is missing, no
> dependency information available
> [WARNING] The POM for org.eclipse.equinox:org.
> eclipse.equinox.p2.repository.tools:jar:1.0.0.v20090520-1905 is missing,

[Dev] How to build a connector?

[Rajkumar Rajaratnam]

I'm trying to build this connector
https://github.com/wso2-extensions/esb-connector-gmail

It's failing - see below. Do we need to do anything special to build this
other than doing mvn clean install?


[INFO] Building WSO2 Carbon - Mediation Library Connector For Gmail
3.0.6-SNAPSHOT
[INFO]

[WARNING] The POM for org.apache.bsf:bsf-all:jar:3.0 is missing, no
dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.http.servlet:jar:1.0.200.v20090520-1800
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.osgi:org.eclipse.osgi.services:jar:3.2.0.v20090520-1800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.simpleconfigurator:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.util:jar:1.0.100.v20090520-1800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.ds:jar:1.1.0.v20090520-1800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.jsp.jasper:jar:1.0.200.v20090520-1800
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:javax.servlet.jsp:jar:2.0.0.v200806031607 is missing,
no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.apache.jasper:jar:5.5.17.v200806031609 is missing,
no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.apache.commons.el:jar:1.0.0.v200806031608 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.app:jar:1.2.0.v20090520-1800 is
missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.concurrent:jar:1.0.0.v20090520-1800
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.frameworkadmin:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.frameworkadmin.equinox:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.artifact.repository:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.core:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.director:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.director.app:jar:1.0.100.v20090521-1912
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.directorywatcher:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.engine:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.exemplarysetup:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.extensionlocation:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.jarprocessor:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.metadata.generator:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.metadata:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.metadata.repository:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.reconciler.dropins:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.publisher:jar:1.0.0.v20090521-1912
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.repository.tools:jar:1.0.0.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.repository:jar:1.0.0.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.eclipse.equinox.p2.touchpoint.natives:jar:1.0.100.v20090520-1905
is missing, no dependency information available
[WARNING] The POM for
org.eclipse.equinox:org.e

[Dev] Summarization of JSON data in DAS

[Lahiru Madushanka]

Hi all,

I have a requirement where data values published to DAS are not predefined
(dynamic)
( Ex :- cpu usage of a given laptop ) So I push them as a JSON string
Ex:-  "cpuinfo":{"corePercentages": [4.1, 3.1, 5.2, 7.1], "numOfCores": 4}
This JSON string will be changed with no of cores in the PC which pushes
the data.

Is there a way I can write a summarization query in siddhiql to take
average of average corePercentages for a time interval. (first take avg of
percentage values and then average it over time )

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

Re: [Dev] Problems on MB Cluster Enterprise Integrator 6.1.0

[Júnior]

Hello Hasitha,

I have tried that, but I keep receiving this error message in the second
node:


oreImpl
TID: [-1234] [] [2017-07-07 20:51:13,838]  WARN
{org.wso2.andes.server.cluster.CoordinationConfigurableClusterAgent} -
 Node id was null for member Member [.xxx.X.X]:5711. Node id will be
read again after 2 seconds.


After 4 attempts it shutdown the node.

Follow my axis2 configuration for clustering:




true
aws
localhost

5711
accesskey
secretkey
secrutiy-group
us-east-2
ClusterName
mb_int







 


When i start the second node, I can see in the logs that has joined the
cluster, but as it is not able to get the hazelcast node id of the first
node, it shutdowns the second one.


Any clue on this is very welcome.

Thanks,

2017-07-05 14:20 GMT-03:00 Júnior :

> Thank you Hasitha.
>
> It thought leaving it as default, it would generate one.
>
> The ports are open, I can see in the logs it saying the new member has
> joined, but it keeps trying to get the node id of the other member, and
> when it is not able to do, it shutdown the node.
>
> I will try and let you know the results.
>
> Thanks,
>
> 2017-07-05 8:52 GMT-03:00 Hasitha Hiranya :
>
>> Hi,
>>
>> 
>> 
>> default
>>
>> Set a node id in broker.xml file at [EI_HOME]/wso2/broker/conf
>>
>> BTW, are necessary ports open for Hazelcast to communicate?
>>
>> Thanks
>>
>> On Mon, Jul 3, 2017 at 6:51 PM, Júnior  wrote:
>>
>>> Hello,
>>>
>>> I am trying to setup a cluster for the Broker Profile on AWS.
>>>
>>> I am able to start the first node without problem, but when we start the
>>> second node, it doesn't start because it says it is not able to get the
>>> node id of the other member:
>>>
>>> TID: [-1234] [] [2017-07-03 12:55:10,193] ERROR
>>> {org.wso2.andes.server.registry.ApplicationRegistry} -
>>>  org.wso2.andes.kernel.AndesException: Failed to read Node id of
>>> hazelcast member Member [X.X.X.X]:5711
>>>
>>> On the nodes I have leave the nodeId on broker.xml as default, so it
>>> will generate a random one.
>>>
>>> Do you have any clue on where should I set this node id?
>>>
>>> Thanks,
>>>
>>>
>>>
>>> --
>>> Francisco Ribeiro
>>> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Hasitha Abeykoon*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* 
>>
>>
>
>
> --
> Francisco Ribeiro
> *SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
>



-- 
Francisco Ribeiro
*SCEA|SCJP|SCWCD|IBM Certified SOA Associate*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [GSOC][DAS][DEV] Python Client on DAS 4.0

[Madhawa Vidanapathirana]

Hi,

So far I've managed to implement the REST endpoints of Event Simulator
mentioned at [1]. The code is available at repository [2].

The objects passed to REST API has been mapped to Python Classes. All the
fields mentioned in POSTMAN samples (attached) given by Ramindu has been
added to the classes. Additionally, most of the POSTMAN samples has been
implemented as tests in Python Code.

Is their any technique I can use to identify the possible fields of any
object that could be passed to REST API?

[1] -
https://docs.google.com/document/d/154ndex3OBoE0zNOLHatmMOvt2JHh9RJya2VdHlHOTl4/edit?usp=sharing
[2] - https://github.com/madhawav/DASPythonClient

Kind Regards,
Madhawa

-- 
*Madhawa Vidanapathirana*
Student
Department of Computer Science and Engineering
University of Moratuwa
Sri Lanka

Mobile: (+94) 716874425
Email: madhawavidanapathir...@gmail.com
Linked-In: https://lk.linkedin.com/in/madhawa-vidanapathirana-3430b94


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

Re: [Dev] Getting and resorting snapshots of a SiddhiAppRuntime

[Nirmal Fernando]

@Minudika Can you elaborate a bit? What code you're referring to?

On Fri, Jul 7, 2017 at 8:45 PM, Sriskandarajah Suhothayan 
wrote:

> To my knowledge it's doing a pause() restoreState() and then resume().
>
> Am I wrong?
>
> On Fri, Jul 7, 2017 at 6:28 PM, Minudika Malshan 
> wrote:
>
>> Hi,
>>
>> When restarting a siddhiAppRuntime with restoring a snapshot of the
>> source, it calls the connect() method in source and then restoreState()
>> method.
>>
>> Since the source is supposed to do the process using previously captured
>> state, shouldn't the order be restore() and then connect() ?
>>
>> Appreciate if you can help me to clarify this.
>>
>> Thanks and regards!
>>
>> --
>> *Minudika Gammanpila*
>> Software Engineer - WSO2
>>
>> Email   :  minud...@wso2.com
>> Mobile :  +94715659887 <071%20565%209887>
>> Web :  http://wso2.com 
>>
>
>
>
> --
>
> *S. Suhothayan*
> Associate Director / Architect
> *WSO2 Inc. *http://wso2.com
> * *
> lean . enterprise . middleware
>
>
> *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 *
>



-- 

Thanks & regards,
Nirmal

Technical Lead, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Getting and resorting snapshots of a SiddhiAppRuntime

[Sriskandarajah Suhothayan]

To my knowledge it's doing a pause() restoreState() and then resume().

Am I wrong?

On Fri, Jul 7, 2017 at 6:28 PM, Minudika Malshan  wrote:

> Hi,
>
> When restarting a siddhiAppRuntime with restoring a snapshot of the
> source, it calls the connect() method in source and then restoreState()
> method.
>
> Since the source is supposed to do the process using previously captured
> state, shouldn't the order be restore() and then connect() ?
>
> Appreciate if you can help me to clarify this.
>
> Thanks and regards!
>
> --
> *Minudika Gammanpila*
> Software Engineer - WSO2
>
> Email   :  minud...@wso2.com
> Mobile :  +94715659887 <071%20565%209887>
> Web :  http://wso2.com 
>



-- 

*S. Suhothayan*
Associate Director / Architect
*WSO2 Inc. *http://wso2.com
* *
lean . enterprise . middleware


*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan
 | linked-in:
http://lk.linkedin.com/in/suhothayan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon Config Test Dependencies are not in test scope.

[Isuru Perera]

Thanks!

This is a separate question. What's the reason for using EasyMock? I use
Mockito in Carbon Metrics and it seems to be easier to use than EasyMock.

On Fri, Jul 7, 2017 at 7:03 PM, Danesh Kuruppu  wrote:

> git Issue url https://github.com/wso2/carbon-config/issues/41
>
> On Fri, Jul 7, 2017 at 7:02 PM, Danesh Kuruppu  wrote:
>
>> Thanks for reporting Isuru.
>>
>> I created git issue to track[1] this issue will fix it in our next
>> release. Please send the PR if you can.
>>
>> Regards.
>> Danesh
>>
>> On Fri, Jul 7, 2017 at 6:46 PM, Isuru Perera  wrote:
>>
>>> Hi,
>>>
>>> See: https://github.com/wso2/carbon-config/blob/v2.0.0/components
>>> /org.wso2.carbon.config/pom.xml#L44-L57
>>>
>>> The test dependencies like testng and easymock are not in "test" scope.
>>> This is a problem as when we use carbon-config as a dependency, we also get
>>> easymock etc.
>>>
>>> Could someone please fix the scopes in dependencies? (Or else I will try
>>> to send a PR)
>>>
>>> Thanks!
>>>
>>> Best Regards,
>>>
>>> --
>>> Isuru Perera
>>> Technical Lead | WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> about.me/chrishantha
>>> Contact: +IsuruPereraWSO2
>>> 
>>>
>>
>>
>>
>> --
>>
>> *Danesh Kuruppu*
>> Senior Software Engineer | WSO2
>>
>> Email: dan...@wso2.com
>> Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
>> Web: WSO2 Inc 
>>
>>
>
>
> --
>
> *Danesh Kuruppu*
> Senior Software Engineer | WSO2
>
> Email: dan...@wso2.com
> Mobile: +94 (77) 1690552 <077%20169%200552>
> Web: WSO2 Inc 
>
>


-- 
Isuru Perera
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

Re: [Dev] Carbon Config Test Dependencies are not in test scope.

[Danesh Kuruppu]

git Issue url https://github.com/wso2/carbon-config/issues/41

On Fri, Jul 7, 2017 at 7:02 PM, Danesh Kuruppu  wrote:

> Thanks for reporting Isuru.
>
> I created git issue to track[1] this issue will fix it in our next
> release. Please send the PR if you can.
>
> Regards.
> Danesh
>
> On Fri, Jul 7, 2017 at 6:46 PM, Isuru Perera  wrote:
>
>> Hi,
>>
>> See: https://github.com/wso2/carbon-config/blob/v2.0.0/components
>> /org.wso2.carbon.config/pom.xml#L44-L57
>>
>> The test dependencies like testng and easymock are not in "test" scope.
>> This is a problem as when we use carbon-config as a dependency, we also get
>> easymock etc.
>>
>> Could someone please fix the scopes in dependencies? (Or else I will try
>> to send a PR)
>>
>> Thanks!
>>
>> Best Regards,
>>
>> --
>> Isuru Perera
>> Technical Lead | WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>> about.me/chrishantha
>> Contact: +IsuruPereraWSO2 
>>
>
>
>
> --
>
> *Danesh Kuruppu*
> Senior Software Engineer | WSO2
>
> Email: dan...@wso2.com
> Mobile: +94 (77) 1690552 <+94%2077%20169%200552>
> Web: WSO2 Inc 
>
>


-- 

*Danesh Kuruppu*
Senior Software Engineer | WSO2

Email: dan...@wso2.com
Mobile: +94 (77) 1690552
Web: WSO2 Inc 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon Config Test Dependencies are not in test scope.

[Danesh Kuruppu]

Thanks for reporting Isuru.

I created git issue to track[1] this issue will fix it in our next release.
Please send the PR if you can.

Regards.
Danesh

On Fri, Jul 7, 2017 at 6:46 PM, Isuru Perera  wrote:

> Hi,
>
> See: https://github.com/wso2/carbon-config/blob/v2.0.0/
> components/org.wso2.carbon.config/pom.xml#L44-L57
>
> The test dependencies like testng and easymock are not in "test" scope.
> This is a problem as when we use carbon-config as a dependency, we also get
> easymock etc.
>
> Could someone please fix the scopes in dependencies? (Or else I will try
> to send a PR)
>
> Thanks!
>
> Best Regards,
>
> --
> Isuru Perera
> Technical Lead | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> about.me/chrishantha
> Contact: +IsuruPereraWSO2 
>



-- 

*Danesh Kuruppu*
Senior Software Engineer | WSO2

Email: dan...@wso2.com
Mobile: +94 (77) 1690552
Web: WSO2 Inc 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Carbon Config Test Dependencies are not in test scope.

[Isuru Perera]

Hi,

See:
https://github.com/wso2/carbon-config/blob/v2.0.0/components/org.wso2.carbon.config/pom.xml#L44-L57

The test dependencies like testng and easymock are not in "test" scope.
This is a problem as when we use carbon-config as a dependency, we also get
easymock etc.

Could someone please fix the scopes in dependencies? (Or else I will try to
send a PR)

Thanks!

Best Regards,

-- 
Isuru Perera
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

[Dev] Getting and resorting snapshots of a SiddhiAppRuntime

[Minudika Malshan]

Hi,

When restarting a siddhiAppRuntime with restoring a snapshot of the source,
it calls the connect() method in source and then restoreState() method.

Since the source is supposed to do the process using previously captured
state, shouldn't the order be restore() and then connect() ?

Appreciate if you can help me to clarify this.

Thanks and regards!

-- 
*Minudika Gammanpila*
Software Engineer - WSO2

Email   :  minud...@wso2.com
Mobile :  +94715659887
Web :  http://wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Should we refactor CarbonMessage

[Shafreen Anfar]

Hi All,

In addition to considering all the facts presented above, I also talked to
each transport developer who actually came up with different types of
carbon-messages. Based on those discussion I came up with below design.

Originally, CarbonMessage is designed to carry data between two components
and I believe it should stay the same. However, it should be able carry
data relevant to each component. For instance, in JMS case, it should be
able carry a map for map messages where as in websockets case it should be
able carry a string.

Therefore, I thought of creating a CarbonMessage with java generics. Then
we can extend it accordingly.

​

As you can see above, we can provide a DefaultCarbonMessage implementation.
However, in HTTP case, we have done some specific implementation to
optimize the transport. At the moment those logic also resides inside the
abstract CarbonMessage. With the new design we can simply move them to
something like ByteCarbonMessage.

I believe with this design we can have proper abstraction while reducing
number of redundant carbon messages.


On Thu, Jul 6, 2017 at 12:16 AM, Chanaka Fernando  wrote:

> It seems there is room to improve the current CarbonMessage
> implementation. Following are few main areas where we can improve its
> functionality.
>
>- At the moment there are too many ways to get the message body from
>the CarbonMessage
>- getMessageBody()
>   - getInputStream() - This is a http specific impl.
>   - getMessageDateSource()
>
> The above 3 methods serve 3 different purposes. This design has been done
> mainly thinking about the HTTP messages. In a message passthrough scenario,
> content is kept in the content queue and accessed as a stream. When the
> message content is accessed within intermediate layer (like ballerina), it
> will be retrieved through messageDataSource.
>
>- There are too many types of CarbonMessages in carbon-messaging that
>are only used by a specific transport implementation
>   - BinaryCarbonMessage
>   - ControlCarbonMessage
>   - DefaultCarbonMessage
>   - MapCarbonMessage
>   - SerializableCarbonMessage
>   - StatusCarbonMessage
>   - StreamingCarbonMessage
>   - TextCarbonMessage
>
>
>- Most of above CarbonMessages do not adhere to the contract that is
>imposed by the CarbonMessage interface.
>
> I agree on the fact that we need to refactor these different types of
> CarbonMessage implementations. I think what Asitha suggested is a viable
> approach to handle different types of messages.
>
> Considering these facts, I believe we should refactor CarbonMessage before
> others starting using it in their implementations. Please let us know your
> thoughts as well :)
>
> +1 for refactoring the carbon message and relevant implementations to
> support non-HTTP use cases. In the meantime, we should support HTTP
> messaging in an efficient manner since that will be the mostly used
> scenario of ballerina.
>
> On Wed, Jul 5, 2017 at 4:55 PM, Irunika Weeraratne 
> wrote:
>
>> Hi Shafreen and Asitha,
>> In the first place, they were introduced after a long discussion in
>> WebSocket scenarios. This was because when the WebSocket messages are
>> arrived to transport level we already knew what kind of message it is.
>> Eg: Text, Binary, Control, Status
>>
>> So I made sense to create the same type of carbon message in the
>> transport. Then carbon message types were used to identify the scenarios we
>> had to address in the application layer.
>> Eg: If the carbon message is an instance of TextCarbonMessage we know
>> what to do in the first place. Also converting text into byte buffer in the
>> transport and then converting it again into text in the application layer
>> doesn't make sense.
>>
>> Because of that, those message types were introduced. IMO while we reduce
>> the no. of carbon message types we might need to keep some of the types
>> because it will affect the performance.
>> Also, we can always override the methods in default carbon message if in
>> order to work with default scenarios.
>>
>> WDYT?
>>
>> Thanks,
>> Irunika
>>
>> *Irunika Weeraratne*
>> *Software Engineer | WSO2, Inc. *
>> *Email : irun...@wso2.com *
>> *LinkedIn : https://lk.linkedin.com/in/irunika
>> *
>> *Mobile : +94712403314 <071%20240%203314>*
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Wed, Jul 5, 2017 at 3:54 PM, Asitha Nanayakkara 
>> wrote:
>>
>>> Hi Shafreen,
>>>
>>> I would suggest having a single Carbon Message with the option to set
>>> different types of data sources as the data source for the message. For
>>> that, we might need to go through the existing other message types and
>>> think what kind of functionality to be added to carbon message. If our
>>> intention is not to extend carbon message, we can make it a final class. If
>>> not we have to design it to be extended by other users.
>>>
>>> When reading the payload multiple ti

Re: [Dev] Issue in the deployment of WSO2am docker image in to aws EC2 container service

[Ayeshmantha Perera]

Hi All
I ssh into the instance and had a look at the docker ps command to see the
mapping of the container port to open the ports in the security groups
inbound.First time when I add them I got a message from the wso2apim
manager and It was a server error kind of a message in the next time when
I'm accessing there was a gateway 504 error.And the ports mapping of the
docker ps command is totally different this time it has changed
dynamically.And when I'm looking in to this error I recognized that service
is stopping due to health check failure and restarting.In that time the
ports are changing

Is the health check target working properly it was mentioned as /echo/wso2
in the post[1].

[1]
https://medium.com/containermind/how-to-deploy-wso2-api-manager-on-amazon-ecs-bdc5a8d22844

Regards
Ayeshmantha


On Wed, Jul 5, 2017 at 1:34 PM, Ayeshmantha Perera 
wrote:

> Hi All
>
> I tried to telnet in to the instance but it's not working.But it says
> container started succefully.And all the ports are opend for the load
> balancer.But still no luck.Any idea on this
>
> Regards
> Ayesh
>
> On Tue, Jul 4, 2017 at 4:50 PM, Ayeshmantha Perera <
> akayeshman...@gmail.com> wrote:
>
>>
>>
>> On Mon, Jul 3, 2017 at 8:17 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi,
>>>
>>> Server log looks okay. Can you check whether api manager is running in
>>> the container? I guess you should be able to login to the container. Maybe
>>> you can telnet and check 9443 port is up and running.
>>>
>>> Thank you!
>>>
>>> On Mon, Jul 3, 2017 at 6:35 PM, Ayeshmantha Perera <
>>> akayeshman...@gmail.com> wrote:
>>>
 Hi Pubudu

 Am using a self signed certificate is that a problem.Because always
 with that cert when I'm creating a http/s load blancer it says no healthy
 targets are found

 Thanks
 Regards
 Ayesh

 On Mon, Jul 3, 2017 at 5:02 PM, Ayeshmantha Perera <
 akayeshman...@gmail.com> wrote:

> Hi Pubudu
>
> The log shows that hthe apim is up and running
> Is there an issue with /echo/wso2 health check endpoint
>
> Here I attach the log with the mail
>
> On Wed, Jun 28, 2017 at 8:06 PM, Pubudu Gunatilaka 
> wrote:
>
>> HI Ayesh,
>>
>> Do you see any errors in the container logs?
>>
>> Thank you!
>>
>> On Wed, Jun 28, 2017 at 12:13 PM, Ayeshmantha Perera <
>> akayeshman...@gmail.com> wrote:
>>
>>> Hi All
>>>
>>> We deploy the wso2am 2.1.0 docker image which was taken from the
>>> wso2 docker hub in aws EC2 container service.And also followed the [1] 
>>> as a
>>> referece on deploying
>>>
>>> After creating the ECS service which is exposing the management
>>> console outside.It gives a 504 bad gateway error.And also it shows that 
>>> non
>>> of the instances are healthy in the region.I deployed it on 4 regions in
>>> all regions it was the same
>>>
>>> Appreciate if someone can help us to resolve this deployment issue
>>>
>>> Regards,
>>> Ayeshmantha
>>>
>>> [1] https://medium.com/containermind/how-to-deploy-wso2-api-
>>> manager-on-amazon-ecs-bdc5a8d22844
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049 <%2B94772207163>
>>
>>
>

>>>
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev