date:20170130

Re: [Dev] carbon-business-process build failure (was: [Builder] Build failed in Jenkins: carbon-business-process #2420)

2017-01-30 Thread Vinod Kavinda

Hi KasunG,
I think it is  wso2-scm-server.

/vinod


On Tue, Jan 31, 2017 at 12:47 PM, Vinod Kavinda  wrote:

> [Adding hasitha,Nandika]
>
> On Tue, Jan 31, 2017 at 12:43 PM, KasunG Gajasinghe 
> wrote:
>
>> Hi all,
>>
>> The maven-release-plugin which is part of the Jenkins wso2 maven release
>> plugin has failed to find the credentials.
>>
>> These credentials are read from maven settings.xml. There should be a
>>  entry for the project.scm.id you guys are using. What is the
>> project.scm.id you are using?
>>
>>
>> On Tue, Jan 31, 2017 at 9:51 AM, Maheshika Goonetilleke <
>> mahesh...@wso2.com> wrote:
>>
>>> Hi Vinod
>>>
>>> Just checked the configuration, the credentials (wso2-jenkins-bot) are
>>> the same given in other jobs as well.
>>>
>>> @kasung : please advice.
>>>
>>> On Tue, Jan 31, 2017 at 9:34 AM, Vinod Kavinda  wrote:
>>>
 Hi KasunG,
 The business process build has failed when trying to do a release after
 a commit. It seems the GitHub credentials are incorrect. Please have a 
 look.

 Regards,
 Vinod

 On Tue, Jan 31, 2017 at 9:22 AM,  wrote:

> See  >
>
> Changes:
>
> [suba.11] fixing issues with #447
>
> --
> [...truncated 21671 lines...]
> [WARNING] Ignoring unrecognized line: ?? features/unified-endpoint/pom.
> xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? release.properties
> [WARNING] Ignoring unrecognized line: ?? repoLastDeleteRecord.txt
> [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
> org.wso2.carbon.application.mgt.bpel.stub/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
> org.wso2.carbon.application.mgt.humantask.stub/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
> pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/o
> rg.wso2.carbon.attachment.mgt.skeleton/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/o
> rg.wso2.carbon.attachment.mgt.stub/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/p
> om.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/
> org.wso2.carbon.bpel.analytics.publisher.
> skeleton/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/
> org.wso2.carbon.bpel.analytics.publisher.stub/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/
> org.wso2.carbon.bpel.skeleton/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/
> org.wso2.carbon.bpel.stub/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/pom.xml.rel
> easeBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpmn/
> org.wso2.carbon.bpmn.stub/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpmn/pom.xml.rel
> easeBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/
> org.wso2.carbon.humantask.skeleton/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/
> org.wso2.carbon.humantask.stub/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/pom.xm
> l.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/unified-endpoint
> /org.wso2.carbon.unifiedendpoint.stub/pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? service-stubs/unified-endpoint
> /pom.xml.releaseBackup
> [INFO] Executing: /bin/sh -c cd  carbon-business-process/ws/> && git commit --verbose -F
> /tmp/maven-scm-614765158.commit pom.xml 
> service-stubs/attachment-mgt/pom.xml
> service-stubs/attachment-mgt/org.wso2.carbon.attachment.mgt.skeleton/pom.xml
> service-stubs/attachment-mgt/org.wso2.carbon.attachment.mgt.stub/pom.xml
> service-stubs/bpel/pom.xml 
> service-stubs/bpel/org.wso2.carbon.bpel.skeleton/pom.xml
> service-stubs/bpel/org.wso2.carbon.bpel.stub/pom.xml
> service-stubs/bpel/org.wso2.carbon.bpel.analytics.publisher.skeleton/pom.xml
> service-stubs/bpel/org.wso2.carbon.bpel.analytics.publisher.stub/pom.xml
> service-stubs/humantask/pom.xml service-stubs/humantask/org.ws
> o2.carbon.humantask.skeleton/pom.xml service-stubs/humantask/org.ws
> o2.carbon.humantask.stub/pom.xml service-stubs/unified-endpoint/pom.xml
>

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Chamila Adhikarinayake

Hi,

Tested Workflows for API state change feature.

[+] Stable - go ahead and release

Chamila

On Tue, Jan 31, 2017 at 12:31 PM, Rajith Roshan  wrote:

> Hi,
>
> Tested API manager with third party key manager.
>
> [+] Stable - go ahead and release
>
>
> Thanks!
> Rajith
>
> On Tue, Jan 31, 2017 at 12:23 PM, Anuruddha Liyanarachchi <
> anurudd...@wso2.com> wrote:
>
>> Hi,
>>
>> Tested following:
>>
>> 1. Websocket API create, publish and invocation.
>> 2. SOAP endpoint API create, publish and invocation.
>>
>> [+] Stable - go ahead and release
>>
>> On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe <
>> malint...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>>>
>>> Please download, test the product and vote. The vote will be open for 72
>>> hours or as needed.
>>>
>>> Source and distribution
>>>
>>> Run-time : https://github.com/wso2/prod
>>> uct-apim/releases/download/v2.1.0-rc4/wso2am-2.1.0-RC4.zip
>>> Analytics : https://github.com/wso2/anal
>>> ytics-apim/releases/download/v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
>>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>>> g/v2.1.0-rc2
>>>
>>>
>>> This release fixes the following issues:
>>> Runtime : https://wso2.org/jira/issues/?filter=13623
>>> Analytics : https://wso2.org/jira/issues/?filter=13624
>>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>>
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> - WSO2 API Manager Team -
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Thanks and Regards,*
>> Anuruddha Lanka Liyanarachchi
>> Software Engineer - WSO2
>> Mobile : +94 (0) 712762611
>> Tel  : +94 112 145 345
>> a nurudd...@wso2.com
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Rajith Roshan
> Software Engineer, WSO2 Inc.
> Mobile: +94-72-642-8350 <%2B94-71-554-8430>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Regards,
Chamila Adhikarinayake
Senior Software Engineer
WSO2, Inc.
Mobile - +94712346437
Email  - chami...@wso2.com
Blog  -  http://helpfromadhi.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] carbon-business-process build failure (was: [Builder] Build failed in Jenkins: carbon-business-process #2420)

2017-01-30 Thread Vinod Kavinda

[Adding hasitha,Nandika]

On Tue, Jan 31, 2017 at 12:43 PM, KasunG Gajasinghe  wrote:

> Hi all,
>
> The maven-release-plugin which is part of the Jenkins wso2 maven release
> plugin has failed to find the credentials.
>
> These credentials are read from maven settings.xml. There should be a
>  entry for the project.scm.id you guys are using. What is the
> project.scm.id you are using?
>
>
> On Tue, Jan 31, 2017 at 9:51 AM, Maheshika Goonetilleke <
> mahesh...@wso2.com> wrote:
>
>> Hi Vinod
>>
>> Just checked the configuration, the credentials (wso2-jenkins-bot) are
>> the same given in other jobs as well.
>>
>> @kasung : please advice.
>>
>> On Tue, Jan 31, 2017 at 9:34 AM, Vinod Kavinda  wrote:
>>
>>> Hi KasunG,
>>> The business process build has failed when trying to do a release after
>>> a commit. It seems the GitHub credentials are incorrect. Please have a look.
>>>
>>> Regards,
>>> Vinod
>>>
>>> On Tue, Jan 31, 2017 at 9:22 AM,  wrote:
>>>
 See 

 Changes:

 [suba.11] fixing issues with #447

 --
 [...truncated 21671 lines...]
 [WARNING] Ignoring unrecognized line: ?? features/unified-endpoint/pom.
 xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? release.properties
 [WARNING] Ignoring unrecognized line: ?? repoLastDeleteRecord.txt
 [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
 org.wso2.carbon.application.mgt.bpel.stub/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
 org.wso2.carbon.application.mgt.humantask.stub/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
 pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/o
 rg.wso2.carbon.attachment.mgt.skeleton/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/o
 rg.wso2.carbon.attachment.mgt.stub/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/p
 om.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/org.wso2.ca
 rbon.bpel.analytics.publisher.skeleton/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/org.wso2.ca
 rbon.bpel.analytics.publisher.stub/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/org.wso2.ca
 rbon.bpel.skeleton/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/org.wso2.ca
 rbon.bpel.stub/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/pom.xml.rel
 easeBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/bpmn/org.wso2.ca
 rbon.bpmn.stub/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/bpmn/pom.xml.rel
 easeBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/org.ws
 o2.carbon.humantask.skeleton/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/org.ws
 o2.carbon.humantask.stub/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/pom.xm
 l.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/unified-endpoint
 /org.wso2.carbon.unifiedendpoint.stub/pom.xml.releaseBackup
 [WARNING] Ignoring unrecognized line: ?? service-stubs/unified-endpoint
 /pom.xml.releaseBackup
 [INFO] Executing: /bin/sh -c cd  && git commit --verbose -F
 /tmp/maven-scm-614765158.commit pom.xml 
 service-stubs/attachment-mgt/pom.xml
 service-stubs/attachment-mgt/org.wso2.carbon.attachment.mgt.skeleton/pom.xml
 service-stubs/attachment-mgt/org.wso2.carbon.attachment.mgt.stub/pom.xml
 service-stubs/bpel/pom.xml 
 service-stubs/bpel/org.wso2.carbon.bpel.skeleton/pom.xml
 service-stubs/bpel/org.wso2.carbon.bpel.stub/pom.xml
 service-stubs/bpel/org.wso2.carbon.bpel.analytics.publisher.skeleton/pom.xml
 service-stubs/bpel/org.wso2.carbon.bpel.analytics.publisher.stub/pom.xml
 service-stubs/humantask/pom.xml service-stubs/humantask/org.ws
 o2.carbon.humantask.skeleton/pom.xml service-stubs/humantask/org.ws
 o2.carbon.humantask.stub/pom.xml service-stubs/unified-endpoint/pom.xml
 service-stubs/unified-endpoint/org.wso2.carbon.unifiedendpoint.stub/pom.xml
 service-stubs/bpmn/pom.xml 
 service-stubs/bpmn/org.wso2.carbon.bpmn.stub/pom.xml
 service-s
  tubs/application-mgt/pom.xml service-stubs/application-mgt/
 org.wso2.carbon.application.mgt.bpel.stub/pom.xml

[Dev] carbon-business-process build failure (was: [Builder] Build failed in Jenkins: carbon-business-process #2420)

2017-01-30 Thread KasunG Gajasinghe

Hi all,

The maven-release-plugin which is part of the Jenkins wso2 maven release
plugin has failed to find the credentials.

These credentials are read from maven settings.xml. There should be a
 entry for the project.scm.id you guys are using. What is the
project.scm.id you are using?


On Tue, Jan 31, 2017 at 9:51 AM, Maheshika Goonetilleke 
wrote:

> Hi Vinod
>
> Just checked the configuration, the credentials (wso2-jenkins-bot) are the
> same given in other jobs as well.
>
> @kasung : please advice.
>
> On Tue, Jan 31, 2017 at 9:34 AM, Vinod Kavinda  wrote:
>
>> Hi KasunG,
>> The business process build has failed when trying to do a release after a
>> commit. It seems the GitHub credentials are incorrect. Please have a look.
>>
>> Regards,
>> Vinod
>>
>> On Tue, Jan 31, 2017 at 9:22 AM,  wrote:
>>
>>> See 
>>>
>>> Changes:
>>>
>>> [suba.11] fixing issues with #447
>>>
>>> --
>>> [...truncated 21671 lines...]
>>> [WARNING] Ignoring unrecognized line: ?? features/unified-endpoint/pom.
>>> xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? release.properties
>>> [WARNING] Ignoring unrecognized line: ?? repoLastDeleteRecord.txt
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
>>> org.wso2.carbon.application.mgt.bpel.stub/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
>>> org.wso2.carbon.application.mgt.humantask.stub/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/application-mgt/
>>> pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/o
>>> rg.wso2.carbon.attachment.mgt.skeleton/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/o
>>> rg.wso2.carbon.attachment.mgt.stub/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/attachment-mgt/p
>>> om.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/org.wso2.ca
>>> rbon.bpel.analytics.publisher.skeleton/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/org.wso2.ca
>>> rbon.bpel.analytics.publisher.stub/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/org.wso2.ca
>>> rbon.bpel.skeleton/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/org.wso2.ca
>>> rbon.bpel.stub/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpel/pom.xml.rel
>>> easeBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpmn/org.wso2.ca
>>> rbon.bpmn.stub/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/bpmn/pom.xml.rel
>>> easeBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/org.ws
>>> o2.carbon.humantask.skeleton/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/org.ws
>>> o2.carbon.humantask.stub/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/humantask/pom.xm
>>> l.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/unified-endpoint
>>> /org.wso2.carbon.unifiedendpoint.stub/pom.xml.releaseBackup
>>> [WARNING] Ignoring unrecognized line: ?? service-stubs/unified-endpoint
>>> /pom.xml.releaseBackup
>>> [INFO] Executing: /bin/sh -c cd >> carbon-business-process/ws/> && git commit --verbose -F
>>> /tmp/maven-scm-614765158.commit pom.xml service-stubs/attachment-mgt/pom.xml
>>> service-stubs/attachment-mgt/org.wso2.carbon.attachment.mgt.skeleton/pom.xml
>>> service-stubs/attachment-mgt/org.wso2.carbon.attachment.mgt.stub/pom.xml
>>> service-stubs/bpel/pom.xml 
>>> service-stubs/bpel/org.wso2.carbon.bpel.skeleton/pom.xml
>>> service-stubs/bpel/org.wso2.carbon.bpel.stub/pom.xml service-stubs/bpel/
>>> org.wso2.carbon.bpel.analytics.publisher.skeleton/pom.xml
>>> service-stubs/bpel/org.wso2.carbon.bpel.analytics.publisher.stub/pom.xml
>>> service-stubs/humantask/pom.xml service-stubs/humantask/org.ws
>>> o2.carbon.humantask.skeleton/pom.xml service-stubs/humantask/org.ws
>>> o2.carbon.humantask.stub/pom.xml service-stubs/unified-endpoint/pom.xml
>>> service-stubs/unified-endpoint/org.wso2.carbon.unifiedendpoint.stub/pom.xml
>>> service-stubs/bpmn/pom.xml 
>>> service-stubs/bpmn/org.wso2.carbon.bpmn.stub/pom.xml
>>> service-s
>>>  tubs/application-mgt/pom.xml service-stubs/application-mgt/
>>> org.wso2.carbon.application.mgt.bpel.stub/pom.xml
>>> service-stubs/application-mgt/org.wso2.carbon.application.mgt.humantask.stub/pom.xml
>>> components/application-deployers/pom.xml components/application-deploye
>>> rs/org.wso2.carbon.application.deployer.bpel/pom.xml
>>>

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Rajith Roshan

Hi,

Tested API manager with third party key manager.

[+] Stable - go ahead and release


Thanks!
Rajith

On Tue, Jan 31, 2017 at 12:23 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi,
>
> Tested following:
>
> 1. Websocket API create, publish and invocation.
> 2. SOAP endpoint API create, publish and invocation.
>
> [+] Stable - go ahead and release
>
> On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe  > wrote:
>
>> Hi All,
>>
>> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
>> 1.0-rc4/wso2am-2.1.0-RC4.zip
>> Analytics : https://github.com/wso2/anal
>> ytics-apim/releases/download/v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>> g/v2.1.0-rc2
>>
>>
>> This release fixes the following issues:
>> Runtime : https://wso2.org/jira/issues/?filter=13623
>> Analytics : https://wso2.org/jira/issues/?filter=13624
>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 API Manager Team -
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Anuruddha Liyanarachchi

Hi,

Tested following:

1. Websocket API create, publish and invocation.
2. SOAP endpoint API create, publish and invocation.

[+] Stable - go ahead and release

On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe 
wrote:

> Hi All,
>
> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> Source and distribution
>
> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
> 1.0-rc4/wso2am-2.1.0-RC4.zip
> Analytics : https://github.com/wso2/analytics-apim/releases/download/v
> 2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
> g/v2.1.0-rc2
>
>
> This release fixes the following issues:
> Runtime : https://wso2.org/jira/issues/?filter=13623
> Analytics : https://wso2.org/jira/issues/?filter=13624
> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 API Manager Team -
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306 <+94%2071%20238%203306>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Thanks and Regards,*
Anuruddha Lanka Liyanarachchi
Software Engineer - WSO2
Mobile : +94 (0) 712762611
Tel  : +94 112 145 345
a nurudd...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] wso2 iot 3.0 connectedup sample

2017-01-30 Thread Menaka Jayawardena

[+ Dev@]

On Tue, Jan 31, 2017 at 11:25 AM, Siddheshwar <
siddh...@infrarootsolutions.com> wrote:

> thanks its working...
>
> On 30-Jan-2017 10:44 pm, Menaka Jayawardena  wrote:
>
> Hi Siddheshwar,
>
> Thank you very much for trying out WSO2 IoT Server.
>
> This is an issue with Java 8.
>
> Please replace the pom file in *samples/connectedcup/components/plugin*
> with the attached file.
>
> Thanks and Regards,
> Menaka
>
>
> On Mon, Jan 30, 2017 at 12:39 PM, Siddheshwar Borwandkar <
> siddh...@infrarootsolutions.com> wrote:
>
> i working on *connectedcup* sample .
> when i run "*mvn clean install -f samples-deployer.xml*"
>
> it return build failure.
>
>
>
> [INFO] 
> 
> [INFO] Building WSO2 IoTS(Device Types) - Connected Cup CDMF Plugin 1.0.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @
> org.coffeeking.connectedcup.plugin ---
> [INFO] Deleting /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/target
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @
> org.coffeeking.connectedcup.plugin ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] File encoding has not been set, using platform encoding UTF-8,
> i.e. build is platform dependent!
> [INFO] Compiling 9 source files to /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/target/classes
> [INFO]
> [INFO] --- maven-scr-plugin:1.7.2:scr (generate-scr-scrdescriptor) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Class org.coffeeking.connectedcup.pl
> ugin.internal.ConnectedCupServiceComponent is using deprecated javadoc
> tags  at file:/infralabs/servers/wso2iot-3.0.0/samples/connectedcup/
> component/plugin/src/main/java/org/coffeeking/connectedc
> up/plugin/internal/ConnectedCupServiceComponent.java:30
> [WARNING] It is highly recommended to fix these problems, as future
> versions might not support these features anymore.
> [INFO] Generating 2 MetaType Descriptors to /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/target/scr-plugin-
> generated/OSGI-INF/metatype/metatype.xml
> [INFO] Writing abstract service descriptor /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/target/scr-plugin-
> generated/OSGI-INF/scr-plugin/scrinfo.xml with 1 entries.
> [INFO] Generating 1 Service Component Descriptors to
> /infralabs/servers/wso2iot-3.0.0/samples/connectedcup/compon
> ent/plugin/target/scr-plugin-generated/OSGI-INF/serviceComponents.xml
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:testResources
> (default-testResources) @ org.coffeeking.connectedcup.plugin ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /infralabs/servers/wso2iot-3.0
> .0/samples/connectedcup/component/plugin/src/test/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile)
> @ org.coffeeking.connectedcup.plugin ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.18:test (default-test) @
> org.coffeeking.connectedcup.plugin ---
> [INFO]
> [INFO] --- maven-bundle-plugin:1.4.0:bundle (default-bundle) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.bind.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.bind.annotation.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.parsers.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> org.wso2.carbon.context.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Importing packages that are never
> refered to by any class on the Bundle-Classpath[Jar:dot]: [javax.net,
> javax.net.ssl, org.w3c.dom, org.wso2.carbon.ndatasource.core].
>
> *[ERROR] Error building bundle
> org.coffeeking:org.coffeeking.connectedcup.plugin:bundle:1.0.0 : Unresolved
> references to

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Prasanna Dangalla

Hi All,

Tested the following scenarios.


   - Create an API
   - Added subscription level policy
   - Validated the throttled out use case
   - Created store users.
   - Invoke API through newly created uses.
   - Changes throttling policies from admin panel and validated


[+]   Stable   - go ahead and release.

Thanks

*Prasanna Dangalla*
Senior Software Engineer, WSO2, Inc.; http://wso2.com/
lean.enterprise.middleware


*cell: +94 718 11 27 51*
*twitter: @prasa77*

On Tue, Jan 31, 2017 at 11:05 AM, Nuwan Dias  wrote:

> Tested the following, no issues found.
>
> 1. Adding/Updating APIs.
> 2. API Visibility for tenants and ST.
> 3. Tags with visibility and tag grouping for tenants and ST.
> 4. Product profiles.
>
> [+] Stable - go ahead and release
>
> Thanks,
> NuwanD.
>
> On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe  > wrote:
>
>> Hi All,
>>
>> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
>> 1.0-rc4/wso2am-2.1.0-RC4.zip
>> Analytics : https://github.com/wso2/anal
>> ytics-apim/releases/download/v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>> g/v2.1.0-rc2
>>
>>
>> This release fixes the following issues:
>> Runtime : https://wso2.org/jira/issues/?filter=13623
>> Analytics : https://wso2.org/jira/issues/?filter=13624
>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 API Manager Team -
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <+94%2077%20777%205729>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Rukshan Premathunga

Test Statistics and basic functions. No issues found.

[+] Stable - go ahead and release

Thanks and Regards

On Tue, Jan 31, 2017 at 11:05 AM, Nuwan Dias  wrote:

> Tested the following, no issues found.
>
> 1. Adding/Updating APIs.
> 2. API Visibility for tenants and ST.
> 3. Tags with visibility and tag grouping for tenants and ST.
> 4. Product profiles.
>
> [+] Stable - go ahead and release
>
> Thanks,
> NuwanD.
>
> On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe  > wrote:
>
>> Hi All,
>>
>> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
>> 1.0-rc4/wso2am-2.1.0-RC4.zip
>> Analytics : https://github.com/wso2/anal
>> ytics-apim/releases/download/v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>> g/v2.1.0-rc2
>>
>>
>> This release fixes the following issues:
>> Runtime : https://wso2.org/jira/issues/?filter=13623
>> Analytics : https://wso2.org/jira/issues/?filter=13624
>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 API Manager Team -
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729 <+94%2077%20777%205729>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rukshan Chathuranga.
Software Engineer.
WSO2, Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Nuwan Dias

Tested the following, no issues found.

1. Adding/Updating APIs.
2. API Visibility for tenants and ST.
3. Tags with visibility and tag grouping for tenants and ST.
4. Product profiles.

[+] Stable - go ahead and release

Thanks,
NuwanD.

On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe 
wrote:

> Hi All,
>
> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> Source and distribution
>
> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
> 1.0-rc4/wso2am-2.1.0-RC4.zip
> Analytics : https://github.com/wso2/analytics-apim/releases/download/v
> 2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
> g/v2.1.0-rc2
>
>
> This release fixes the following issues:
> Runtime : https://wso2.org/jira/issues/?filter=13623
> Analytics : https://wso2.org/jira/issues/?filter=13624
> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 API Manager Team -
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306 <+94%2071%20238%203306>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Nuwan Dias

Software Architect - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Chamalee De Silva

Tested following.

1. Basic API functionalities and API documentation functionalities.
2. Single Sign On with WSO2 IS 5.3.0 ( Publisher/Store/admin/carbon) - [ SP
initiated SSO ] with and without Single Logout.
3. IS as Key Manager with WSO2 IS 5.3.0
4. Database functionalities with following databases
MySQL 5.6, 5,7
Oracle 11g
PostgreSQL 9.3
MSSQL
DB2
5. Publishing APIs for External Stores in both tenant and super tenant
6. Provisioning out of band auth Clients
7. Analytics for Publisher and Store (for Linux and Windows)
8. SDK generation feature (for admin, non admin, self signup users in both
super tenant & tenant)
9. Account Recovery and Credential Management feature installation

No issues found.

[+]   Stable   - go ahead and release.




Thanks,
Chamalee

On Tue, Jan 31, 2017 at 11:00 AM, Tharindu Dharmarathna 
wrote:

> Tested Subscription level throttling in tenant and super tenant.
>
> [+]   Stable   - go ahead and release
>
> On Tue, Jan 31, 2017 at 10:47 AM, Fazlan Nazeem  wrote:
>
>> Hi,
>>
>> Tested following.
>>
>>-
>>- Alert generation
>>- Alert subscription
>>
>> [+]   Stable   - go ahead and release
>>
>> On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe <
>> malint...@wso2.com> wrote:
>>
>>> Hi All,
>>>
>>> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>>>
>>> Please download, test the product and vote. The vote will be open for 72
>>> hours or as needed.
>>>
>>> Source and distribution
>>>
>>> Run-time : https://github.com/wso2/prod
>>> uct-apim/releases/download/v2.1.0-rc4/wso2am-2.1.0-RC4.zip
>>> Analytics : https://github.com/wso2/anal
>>> ytics-apim/releases/download/v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
>>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>>> g/v2.1.0-rc2
>>>
>>>
>>> This release fixes the following issues:
>>> Runtime : https://wso2.org/jira/issues/?filter=13623
>>> Analytics : https://wso2.org/jira/issues/?filter=13624
>>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>>
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> - WSO2 API Manager Team -
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> Fazlan Nazeem
>>
>> *Software Engineer*
>>
>> *WSO2 Inc*
>> Mobile : +94772338839
>> <%2B94%20%280%29%20773%20451194>
>> fazl...@wso2.com
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> *Tharindu Dharmarathna*Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091 <+94%2077%20910%209091>*
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thanks & Regards,

*Chamalee De Silva*
Software Engineer
*WS**O2* Inc. :http://wso2.com/

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error when tenant admin tries to login at the first time

2017-01-30 Thread Sumedha Rubasinghe

It looks like throttling tier 'Unlimited' is not available.  Tenant loading
issue?

Is it the same on API cloud?

On Jan 31, 2017 10:01 AM, "Geeth Munasinghe"  wrote:

> Following error occurrs while tenant admin tries to login first time.
> Second time it works.
>
> TID: [-1234] [] [2017-01-31 04:20:40,089]  INFO {org.wso2.carbon.user.core.
> ldap.ReadWriteLDAPUserStoreManager} -  LDAP connection created
> successfully in read-write mode {org.wso2.carbon.user.core.ldap.
> ReadWriteLDAPUserStoreManager}
>
> TID: [10346] [] [2017-01-31 04:20:40,368] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.core.multitenancy.TenantAxisConfigurator} -  Creating
> tenant AxisConfiguration for tenant: myworld[10346] {org.wso2.carbon.core.
> multitenancy.TenantAxisConfigurator}
>
> TID: [10346] [] [2017-01-31 04:20:40,428] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.identity.user.store.configuration.deployer.
> UserStoreConfigurationDeployer} -  User Store Configuration Deployer
> initiated. {org.wso2.carbon.identity.user.store.configuration.deployer.
> UserStoreConfigurationDeployer}
>
> TID: [10346] [] [2017-01-31 04:20:40,428] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.identity.user.store.configuration.deployer.
> UserStoreConfigurationDeployer} -  User Store Configuration Deployer
> initiated. {org.wso2.carbon.identity.user.store.configuration.deployer.
> UserStoreConfigurationDeployer}
>
> TID: [10346] [] [2017-01-31 04:20:40,767] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.initializer.multitenancy.TenantServiceBusInitializer}
> -  Intializing the ESB Configuration for the tenant domain : myworld
> {org.wso2.carbon.mediation.initializer.multitenancy.
> TenantServiceBusInitializer}
>
> TID: [10346] [] [2017-01-31 04:20:40,798] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.initializer.CarbonSynapseController} -
> Loading the mediation configuration from the file system
> {org.wso2.carbon.mediation.initializer.CarbonSynapseController}
>
> TID: [10346] [] [2017-01-31 04:20:45,176] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -  Task
> scheduled: [-1234][ESB_TASK][SSS-Salesforce_Gmail-Task]
> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager}
>
> TID: [10346] [] [2017-01-31 04:20:45,177] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.ntask.NTaskTaskManager} -  Initialized task
> manager. Tenant [10346] {org.wso2.carbon.mediation.ntask.NTaskTaskManager}
>
> TID: [10346] [] [2017-01-31 04:20:45,204] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : main was added to the Synapse configuration successfully
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,218] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : fault was added to the Synapse configuration successfully
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,237] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _cors_request_handler_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,241] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _production_key_error_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,247] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _auth_failure_handler_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,247] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _resource_mismatch_handler_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,248] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _throttle_out_handler_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,249] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _sandbox_key_error_ was added to the Synapse configuration successfully
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,249] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Local
> entry : SERVER_HOST was added to the Synapse configuration

Re: [Dev] Error when tenant admin tries to login at the first time

2017-01-30 Thread Nuwandi Wickramasinghe

Hi Geeth,

Is there any chance you changed the tenant admin password ? Issue might be
related to [1]

[1] https://wso2.org/jira/browse/EMM-1684

thanks
Nuwandi

On Tue, Jan 31, 2017 at 10:00 AM, Geeth Munasinghe  wrote:

> Following error occurrs while tenant admin tries to login first time.
> Second time it works.
>
> TID: [-1234] [] [2017-01-31 04:20:40,089]  INFO {org.wso2.carbon.user.core.
> ldap.ReadWriteLDAPUserStoreManager} -  LDAP connection created
> successfully in read-write mode {org.wso2.carbon.user.core.ldap.
> ReadWriteLDAPUserStoreManager}
>
> TID: [10346] [] [2017-01-31 04:20:40,368] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.core.multitenancy.TenantAxisConfigurator} -  Creating
> tenant AxisConfiguration for tenant: myworld[10346] {org.wso2.carbon.core.
> multitenancy.TenantAxisConfigurator}
>
> TID: [10346] [] [2017-01-31 04:20:40,428] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.identity.user.store.configuration.deployer.
> UserStoreConfigurationDeployer} -  User Store Configuration Deployer
> initiated. {org.wso2.carbon.identity.user.store.configuration.deployer.
> UserStoreConfigurationDeployer}
>
> TID: [10346] [] [2017-01-31 04:20:40,428] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.identity.user.store.configuration.deployer.
> UserStoreConfigurationDeployer} -  User Store Configuration Deployer
> initiated. {org.wso2.carbon.identity.user.store.configuration.deployer.
> UserStoreConfigurationDeployer}
>
> TID: [10346] [] [2017-01-31 04:20:40,767] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.initializer.multitenancy.TenantServiceBusInitializer}
> -  Intializing the ESB Configuration for the tenant domain : myworld
> {org.wso2.carbon.mediation.initializer.multitenancy.
> TenantServiceBusInitializer}
>
> TID: [10346] [] [2017-01-31 04:20:40,798] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.initializer.CarbonSynapseController} -
> Loading the mediation configuration from the file system
> {org.wso2.carbon.mediation.initializer.CarbonSynapseController}
>
> TID: [10346] [] [2017-01-31 04:20:45,176] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -  Task
> scheduled: [-1234][ESB_TASK][SSS-Salesforce_Gmail-Task]
> {org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager}
>
> TID: [10346] [] [2017-01-31 04:20:45,177] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.ntask.NTaskTaskManager} -  Initialized task
> manager. Tenant [10346] {org.wso2.carbon.mediation.ntask.NTaskTaskManager}
>
> TID: [10346] [] [2017-01-31 04:20:45,204] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : main was added to the Synapse configuration successfully
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,218] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : fault was added to the Synapse configuration successfully
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,237] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _cors_request_handler_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,241] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _production_key_error_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,247] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _auth_failure_handler_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,247] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _resource_mismatch_handler_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,248] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _throttle_out_handler_ was added to the Synapse configuration
> successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,249] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence
> : _sandbox_key_error_ was added to the Synapse configuration successfully
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}
>
> TID: [10346] [] [2017-01-31 04:20:45,249] @myworld [10346] [IOT] INFO
> {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Local
> entry :

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Tharindu Dharmarathna

Tested Subscription level throttling in tenant and super tenant.

[+]   Stable   - go ahead and release

On Tue, Jan 31, 2017 at 10:47 AM, Fazlan Nazeem  wrote:

> Hi,
>
> Tested following.
>
>-
>- Alert generation
>- Alert subscription
>
> [+]   Stable   - go ahead and release
>
> On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe  > wrote:
>
>> Hi All,
>>
>> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> Source and distribution
>>
>> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
>> 1.0-rc4/wso2am-2.1.0-RC4.zip
>> Analytics : https://github.com/wso2/anal
>> ytics-apim/releases/download/v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
>> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>> g/v2.1.0-rc2
>>
>>
>> This release fixes the following issues:
>> Runtime : https://wso2.org/jira/issues/?filter=13623
>> Analytics : https://wso2.org/jira/issues/?filter=13624
>> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> - WSO2 API Manager Team -
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306 <+94%2071%20238%203306>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Thanks & Regards,
>
> Fazlan Nazeem
>
> *Software Engineer*
>
> *WSO2 Inc*
> Mobile : +94772338839
> <%2B94%20%280%29%20773%20451194>
> fazl...@wso2.com
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

*Tharindu Dharmarathna*Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

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

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Fazlan Nazeem

Hi,

Tested following.

   -
   - Alert generation
   - Alert subscription

[+]   Stable   - go ahead and release

On Mon, Jan 30, 2017 at 10:28 PM, Malintha Amarasinghe 
wrote:

> Hi All,
>
> This is the 4th Release Candidate of WSO2 API Manager 2.1.0
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> Source and distribution
>
> Run-time : https://github.com/wso2/product-apim/releases/download/v2.
> 1.0-rc4/wso2am-2.1.0-RC4.zip
> Analytics : https://github.com/wso2/analytics-apim/releases/download/v
> 2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
> Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
> g/v2.1.0-rc2
>
>
> This release fixes the following issues:
> Runtime : https://wso2.org/jira/issues/?filter=13623
> Analytics : https://wso2.org/jira/issues/?filter=13624
> Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> - WSO2 API Manager Team -
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306 <+94%2071%20238%203306>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

*WSO2 Inc*
Mobile : +94772338839
<%2B94%20%280%29%20773%20451194>
fazl...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error when tenant admin tries to login at the first time

2017-01-30 Thread Geeth Munasinghe

Following error occurrs while tenant admin tries to login first time.
Second time it works.

TID: [-1234] [] [2017-01-31 04:20:40,089]  INFO
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager} -  LDAP
connection created successfully in read-write mode
{org.wso2.carbon.user.core.ldap.ReadWriteLDAPUserStoreManager}

TID: [10346] [] [2017-01-31 04:20:40,368] @myworld [10346] [IOT] INFO
{org.wso2.carbon.core.multitenancy.TenantAxisConfigurator} -  Creating
tenant AxisConfiguration for tenant: myworld[10346]
{org.wso2.carbon.core.multitenancy.TenantAxisConfigurator}

TID: [10346] [] [2017-01-31 04:20:40,428] @myworld [10346] [IOT] INFO
{org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}
-  User Store Configuration Deployer initiated.
{org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}

TID: [10346] [] [2017-01-31 04:20:40,428] @myworld [10346] [IOT] INFO
{org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}
-  User Store Configuration Deployer initiated.
{org.wso2.carbon.identity.user.store.configuration.deployer.UserStoreConfigurationDeployer}

TID: [10346] [] [2017-01-31 04:20:40,767] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.initializer.multitenancy.TenantServiceBusInitializer}
-  Intializing the ESB Configuration for the tenant domain : myworld
{org.wso2.carbon.mediation.initializer.multitenancy.TenantServiceBusInitializer}

TID: [10346] [] [2017-01-31 04:20:40,798] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.initializer.CarbonSynapseController} -  Loading
the mediation configuration from the file system
{org.wso2.carbon.mediation.initializer.CarbonSynapseController}

TID: [10346] [] [2017-01-31 04:20:45,176] @myworld [10346] [IOT] INFO
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager} -  Task
scheduled: [-1234][ESB_TASK][SSS-Salesforce_Gmail-Task]
{org.wso2.carbon.ntask.core.impl.AbstractQuartzTaskManager}

TID: [10346] [] [2017-01-31 04:20:45,177] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.ntask.NTaskTaskManager} -  Initialized task
manager. Tenant [10346] {org.wso2.carbon.mediation.ntask.NTaskTaskManager}

TID: [10346] [] [2017-01-31 04:20:45,204] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence :
main was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,218] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence :
fault was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,237] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence :
_cors_request_handler_ was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,241] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence :
_production_key_error_ was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,247] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence :
_auth_failure_handler_ was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,247] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence :
_resource_mismatch_handler_ was added to the Synapse configuration
successfully {org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,248] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence :
_throttle_out_handler_ was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,249] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Sequence :
_sandbox_key_error_ was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,249] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Local entry
: SERVER_HOST was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID: [10346] [] [2017-01-31 04:20:45,250] @myworld [10346] [IOT] INFO
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker} -  Local entry
: SERVER_IP was added to the Synapse configuration successfully
{org.wso2.carbon.mediation.dependency.mgt.DependencyTracker}

TID:

Re: [Dev] wso2 iot 3.0 connectedup sample

2017-01-30 Thread Menaka Jayawardena

Hi Siddheshwar,

Thank you very much for trying out WSO2 IoT Server.

This is an issue with Java 8.

Please replace the pom file in *samples/connectedcup/components/plugin*
with the attached file.

Thanks and Regards,
Menaka


On Mon, Jan 30, 2017 at 12:39 PM, Siddheshwar Borwandkar <
siddh...@infrarootsolutions.com> wrote:

> i working on *connectedcup* sample .
> when i run "*mvn clean install -f samples-deployer.xml*"
>
> it return build failure.
>
>
>
> [INFO] 
> 
> [INFO] Building WSO2 IoTS(Device Types) - Connected Cup CDMF Plugin 1.0.0
> [INFO] 
> 
> [INFO]
> [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @
> org.coffeeking.connectedcup.plugin ---
> [INFO] Deleting /infralabs/servers/wso2iot-3.0.0/samples/connectedcup/
> component/plugin/target
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.5:process (default) @
> org.coffeeking.connectedcup.plugin ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:resources (default-resources) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /infralabs/servers/wso2iot-3.
> 0.0/samples/connectedcup/component/plugin/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] File encoding has not been set, using platform encoding UTF-8,
> i.e. build is platform dependent!
> [INFO] Compiling 9 source files to /infralabs/servers/wso2iot-3.
> 0.0/samples/connectedcup/component/plugin/target/classes
> [INFO]
> [INFO] --- maven-scr-plugin:1.7.2:scr (generate-scr-scrdescriptor) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Class 
> org.coffeeking.connectedcup.plugin.internal.ConnectedCupServiceComponent
> is using deprecated javadoc tags  at file:/infralabs/servers/
> wso2iot-3.0.0/samples/connectedcup/component/plugin/
> src/main/java/org/coffeeking/connectedcup/plugin/internal/
> ConnectedCupServiceComponent.java:30
> [WARNING] It is highly recommended to fix these problems, as future
> versions might not support these features anymore.
> [INFO] Generating 2 MetaType Descriptors to /infralabs/servers/wso2iot-3.
> 0.0/samples/connectedcup/component/plugin/target/scr-
> plugin-generated/OSGI-INF/metatype/metatype.xml
> [INFO] Writing abstract service descriptor /infralabs/servers/wso2iot-3.
> 0.0/samples/connectedcup/component/plugin/target/scr-
> plugin-generated/OSGI-INF/scr-plugin/scrinfo.xml with 1 entries.
> [INFO] Generating 1 Service Component Descriptors to
> /infralabs/servers/wso2iot-3.0.0/samples/connectedcup/
> component/plugin/target/scr-plugin-generated/OSGI-INF/
> serviceComponents.xml
> [INFO]
> [INFO] --- maven-resources-plugin:2.7:testResources
> (default-testResources) @ org.coffeeking.connectedcup.plugin ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory /infralabs/servers/wso2iot-3.
> 0.0/samples/connectedcup/component/plugin/src/test/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile)
> @ org.coffeeking.connectedcup.plugin ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.18:test (default-test) @
> org.coffeeking.connectedcup.plugin ---
> [INFO]
> [INFO] --- maven-bundle-plugin:1.4.0:bundle (default-bundle) @
> org.coffeeking.connectedcup.plugin ---
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.bind.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.bind.annotation.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> javax.xml.parsers.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Did not find matching referal for
> org.wso2.carbon.context.*
> [WARNING] Warning building bundle org.coffeeking:org.coffeeking.
> connectedcup.plugin:bundle:1.0.0 : Importing packages that are never
> refered to by any class on the Bundle-Classpath[Jar:dot]: [javax.net,
> javax.net.ssl, org.w3c.dom, org.wso2.carbon.ndatasource.core].
>
> *[ERROR] Error building bundle
> org.coffeeking:org.coffeeking.connectedcup.plugin:bundle:1.0.0 : Unresolved
> references to [org.wso2.carbon.base] by class(es) on the
> Bundle-Classpath[Jar:dot]:
> [org/coffeeking/connectedcup/plugin/impl/ConnectedCupManagerService.class]*
> *[ERROR] Error(s) found in bundle configuration*
> [INFO]

[Dev] [VOTE] Release WSO2 API Manager 2.1.0 RC4

2017-01-30 Thread Malintha Amarasinghe

Hi All,

This is the 4th Release Candidate of WSO2 API Manager 2.1.0

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

Source and distribution

Run-time : https://github.com/wso2/product-apim/releases/
download/v2.1.0-rc4/wso2am-2.1.0-RC4.zip
Analytics : https://github.com/wso2/analytics-apim/releases/download/
v2.1.0-rc3/wso2am-analytics-2.1.0-RC3.zip
Tooling : https://github.com/wso2/devstudio-tooling-apim/releases/ta
g/v2.1.0-rc2


This release fixes the following issues:
Runtime : https://wso2.org/jira/issues/?filter=13623
Analytics : https://wso2.org/jira/issues/?filter=13624
Tooling : https://wso2.org/jira/browse/DEVTOOLAPI-1


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

Thanks,
- WSO2 API Manager Team -

-- 
Malintha Amarasinghe
Software Engineer
*WSO2, Inc. - lean | enterprise | middleware*
http://wso2.com/

Mobile : +94 712383306 <+94%2071%20238%203306>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] carbon-mediation 4.6.11 released

2017-01-30 Thread Madhawa Gunasekara

Hi All,

Carbon-mediation 4.6.11 released.

org.wso2.carbon.mediation
carbon-mediation
4.6.11

Thanks,
Madhawa
-- 
*Madhawa Gunasekara*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please Review and Merge (WebSocket Suppport for Carbon-Messaging)

2017-01-30 Thread Irunika Weeraratne

Hi Senduran,
Yes. We can use a general control message type instead of ping and pong
messages. So I removed ping and pong carbon message types from
Carbon-Messaging and added new message type ".

Please review and merge.

Thanks,
Irunika

*Irunika Weeraratne*
*Software Engineer | WSO2, Inc. *
*Email : irun...@wso2.com *
*LinkedIn : https://lk.linkedin.com/in/irunika
*
*Mobile : +94712403314*
*Lean . Enterprise . Middleware*


On Mon, Jan 30, 2017 at 2:20 PM, Senduran Balasubramaniyam <
sendu...@wso2.com> wrote:

> Hi Irunika,
>
> The above PR has PingCarbonMessage and PongCarbonMessage. It will be
> better if you could rename those two classes to generalized name.
>
> Regards
> Senduran
>
> On Fri, Jan 27, 2017 at 2:47 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Looks ok.
>>
>> Senduran/Shafreen, can we merge this PR?
>>
>> On Thu, Jan 26, 2017 at 7:27 PM, Irunika Weeraratne 
>> wrote:
>>
>>> Hi,
>>> Fixed the issues mentioned.
>>> Please review and merge.
>>>
>>> Thanks,
>>> Irunika
>>>
>>> *Irunika Weeraratne*
>>> *Software Engineer | WSO2, Inc. *
>>> *Email : irun...@wso2.com *
>>> *LinkedIn : https://lk.linkedin.com/in/irunika
>>> *
>>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Thu, Jan 26, 2017 at 7:04 PM, Irunika Weeraratne 
>>> wrote:
>>>
 Noted.

 Thanks,
 Irunika

 *Irunika Weeraratne*
 *Software Engineer | WSO2, Inc. *
 *Email : irun...@wso2.com *
 *LinkedIn : https://lk.linkedin.com/in/irunika
 *
 *Mobile : +94712403314 <+94%2071%20240%203314>*
 *Lean . Enterprise . Middleware*


 On Thu, Jan 26, 2017 at 4:34 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> PR has some formatting issue to be fixed. Can you look into it?
>
> On Thu, Jan 26, 2017 at 12:03 PM, Irunika Weeraratne  > wrote:
>
>> Hi all,
>> Can you please review and merge the PR?
>>
>> Thanks,
>> Irunika
>>
>> *Irunika Weeraratne*
>> *Software Engineer | WSO2, Inc. *
>> *Email : irun...@wso2.com *
>> *LinkedIn : https://lk.linkedin.com/in/irunika
>> *
>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Wed, Jan 25, 2017 at 3:35 PM, Irunika Weeraratne > > wrote:
>>
>>> Hi all,
>>> I modified the Carbon-Messaging according to the requirements.
>>> Please review and merge.
>>> https://github.com/wso2/carbon-messaging/pull/40
>>>
>>> Thanks,
>>> Irunika
>>>
>>> *Irunika Weeraratne*
>>> *Software Engineer | WSO2, Inc. *
>>> *Email : irun...@wso2.com *
>>> *LinkedIn : https://lk.linkedin.com/in/irunika
>>> *
>>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Mon, Jan 2, 2017 at 12:47 PM, Irunika Weeraratne <
>>> irun...@wso2.com> wrote:
>>>
 Hi all,
 I did necessary changes after the review.
 Please review and merge
 https://github.com/wso2/carbon-messaging/pull/40

 Thanks,
 Irunika

 *Irunika Weeraratne*
 *Software Engineer | WSO2, Inc. *
 *Email : irun...@wso2.com *
 *LinkedIn : https://lk.linkedin.com/in/irunika
 *
 *Mobile : +94712403314 <+94%2071%20240%203314>*
 *Lean . Enterprise . Middleware*


 On Fri, Dec 23, 2016 at 1:36 PM, Irunika Weeraratne <
 irun...@wso2.com> wrote:

> Noted.
>
> Thanks,
> Irunika
>
> *Irunika Weeraratne*
> *Software Engineer | WSO2, Inc. *
> *Email : irun...@wso2.com *
> *LinkedIn : https://lk.linkedin.com/in/irunika
> *
> *Mobile : +94712403314 <+94%2071%20240%203314>*
> *Lean . Enterprise . Middleware*
>
>
> On Fri, Dec 23, 2016 at 1:30 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Adding @dev
>>
>> @Irunika, always copy the relevant mailing list.
>>
>> On Fri, Dec 23, 2016 at 1:17 PM, Irunika Weeraratne <
>> irun...@wso2.com> wrote:
>>
>>> Hi,
>>> Please review and merge
>>> https://github.com/wso2/carbon-messaging/pull/39

[Dev] Carbon-mediation 4.6.11 staged

2017-01-30 Thread Madhawa Gunasekara

Hi All,

Please find the staged carbon-mediation-4.6.11 at [1].

[1]
https://maven.wso2.org/nexus/content/repositories/orgwso2carbonmediation-1012

Thanks,
Madhawa

-- 
*Madhawa Gunasekara*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Email attachments with CEP output email adapter

2017-01-30 Thread Vinuri Perera

Hi Dilini and Damith,

Thanks for verifying this.

Best Regards,
~Vinuri~

On Mon, Jan 30, 2017 at 12:32 PM, Dilini Muthumala  wrote:

> Hi Shenavi,
>
> Adding to Damith's answer, the reason why it is not currently supported is
> because sending an attachment is not much useful for real-time alerting use
> cases. Typically, a user will need to be informed about some interesting
> activity via an e-mail; so an attachment is unlikely to be needed.
>
> Thanks,
> Dilini
>
> On Mon, Jan 30, 2017 at 12:13 PM, Damith Wickramasinghe 
> wrote:
>
>> Hi Shenavi,
>>
>> No we will have to include the support. It will be available in future
>> and I do not think we have a immediate plan to add it. As mentioned above
>> please check with IS team.
>>
>> Regards,
>> Damith.
>>
>> On Mon, Jan 30, 2017 at 10:54 AM, Shenavi de Mel 
>> wrote:
>>
>>> Hi Damith,
>>>
>>> Is there any specific reason this support is not included? Or is this
>>> something which is there in the CEP roadmap. I am inquiring regarding this
>>> since we were asked to move our email sending to use CEP adapter as it was
>>> identified as the best practice.
>>>
>>> Thanks
>>> Shenavi
>>>
>>> *Shenavi de Mel*
>>> Software Engineer
>>> WSO2 Inc: http://wso2.com
>>> email: shen...@wso2.com
>>> mobile: 0711644470
>>>
>>>
>>> On Sat, Jan 28, 2017 at 7:36 PM, Damith Wickramasinghe >> > wrote:
>>>

 Hi Vinuri,

 Currently CEP Email Output adapter does not provide the support for
 attachments . I think IS team(Adding indunil) has done some work on said
 adapter. Not sure whether they implemented the support.

 Regards,
 Damith.

 On Sat, Jan 28, 2017 at 12:00 PM, Vinuri Perera 
 wrote:

> Hi All,
>
> We have configured our email sending to use the CEP output email
> adapter. We were able to send the plain text / html mails. We have a new
> requirement where we need to send pdf attachment in the mail.
>
> Since we are using the CEP output email adapter is it possible to send
> email attachments?
> Appreciate if anyone could  shed some light on this.
>
> Best Regards,
> ~Vinuri~
>
> --
> Vinuri Perera
> Software Engineer | WSO2 Inc
>
> M : 0711518805
>
>


 --
 Software Engineer
 WSO2 Inc.; http://wso2.com
 
 lean.enterprise.middleware

 mobile: *+94728671315 <+94%2072%20867%201315>*


>>>
>>
>>
>> --
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> 
>> lean.enterprise.middleware
>>
>> mobile: *+94728671315 <+94%2072%20867%201315>*
>>
>>
>
>
> --
> *Dilini Muthumala*
> Senior Software Engineer,
> WSO2 Inc.
>
> *E-mail :* dil...@wso2.com
> *Mobile: *+94 713-400-029 <+94%2071%20340%200029>
>



-- 
Vinuri Perera
Software Engineer | WSO2 Inc

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

Re: [Dev] Please Review and Merge (WebSocket Suppport for Carbon-Messaging)

2017-01-30 Thread Senduran Balasubramaniyam

Hi Irunika,

The above PR has PingCarbonMessage and PongCarbonMessage. It will be better
if you could rename those two classes to generalized name.

Regards
Senduran

On Fri, Jan 27, 2017 at 2:47 PM, Kishanthan Thangarajah  wrote:

> Looks ok.
>
> Senduran/Shafreen, can we merge this PR?
>
> On Thu, Jan 26, 2017 at 7:27 PM, Irunika Weeraratne 
> wrote:
>
>> Hi,
>> Fixed the issues mentioned.
>> Please review and merge.
>>
>> Thanks,
>> Irunika
>>
>> *Irunika Weeraratne*
>> *Software Engineer | WSO2, Inc. *
>> *Email : irun...@wso2.com *
>> *LinkedIn : https://lk.linkedin.com/in/irunika
>> *
>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Thu, Jan 26, 2017 at 7:04 PM, Irunika Weeraratne 
>> wrote:
>>
>>> Noted.
>>>
>>> Thanks,
>>> Irunika
>>>
>>> *Irunika Weeraratne*
>>> *Software Engineer | WSO2, Inc. *
>>> *Email : irun...@wso2.com *
>>> *LinkedIn : https://lk.linkedin.com/in/irunika
>>> *
>>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Thu, Jan 26, 2017 at 4:34 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 PR has some formatting issue to be fixed. Can you look into it?

 On Thu, Jan 26, 2017 at 12:03 PM, Irunika Weeraratne 
 wrote:

> Hi all,
> Can you please review and merge the PR?
>
> Thanks,
> Irunika
>
> *Irunika Weeraratne*
> *Software Engineer | WSO2, Inc. *
> *Email : irun...@wso2.com *
> *LinkedIn : https://lk.linkedin.com/in/irunika
> *
> *Mobile : +94712403314 <+94%2071%20240%203314>*
> *Lean . Enterprise . Middleware*
>
>
> On Wed, Jan 25, 2017 at 3:35 PM, Irunika Weeraratne 
> wrote:
>
>> Hi all,
>> I modified the Carbon-Messaging according to the requirements.
>> Please review and merge.
>> https://github.com/wso2/carbon-messaging/pull/40
>>
>> Thanks,
>> Irunika
>>
>> *Irunika Weeraratne*
>> *Software Engineer | WSO2, Inc. *
>> *Email : irun...@wso2.com *
>> *LinkedIn : https://lk.linkedin.com/in/irunika
>> *
>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Mon, Jan 2, 2017 at 12:47 PM, Irunika Weeraratne > > wrote:
>>
>>> Hi all,
>>> I did necessary changes after the review.
>>> Please review and merge
>>> https://github.com/wso2/carbon-messaging/pull/40
>>>
>>> Thanks,
>>> Irunika
>>>
>>> *Irunika Weeraratne*
>>> *Software Engineer | WSO2, Inc. *
>>> *Email : irun...@wso2.com *
>>> *LinkedIn : https://lk.linkedin.com/in/irunika
>>> *
>>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Fri, Dec 23, 2016 at 1:36 PM, Irunika Weeraratne <
>>> irun...@wso2.com> wrote:
>>>
 Noted.

 Thanks,
 Irunika

 *Irunika Weeraratne*
 *Software Engineer | WSO2, Inc. *
 *Email : irun...@wso2.com *
 *LinkedIn : https://lk.linkedin.com/in/irunika
 *
 *Mobile : +94712403314 <+94%2071%20240%203314>*
 *Lean . Enterprise . Middleware*


 On Fri, Dec 23, 2016 at 1:30 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> Adding @dev
>
> @Irunika, always copy the relevant mailing list.
>
> On Fri, Dec 23, 2016 at 1:17 PM, Irunika Weeraratne <
> irun...@wso2.com> wrote:
>
>> Hi,
>> Please review and merge
>> https://github.com/wso2/carbon-messaging/pull/39
>>
>> Thanks,
>> Irunika
>> *Irunika Weeraratne*
>> *Software Engineer | WSO2, Inc. *
>> *Email : irun...@wso2.com *
>> *LinkedIn : https://lk.linkedin.com/in/irunika
>> *
>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>> *Lean . Enterprise . Middleware*
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Technical Lead,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635 <+94%2077%20342%206635>
> Blog - *http://kishanthan.wordpress.com
>

Re: [Dev] carbon-business-process build failure (was: [Builder] Build failed in Jenkins: carbon-business-process #2420)

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

Re: [Dev] carbon-business-process build failure (was: [Builder] Build failed in Jenkins: carbon-business-process #2420)

[Dev] carbon-business-process build failure (was: [Builder] Build failed in Jenkins: carbon-business-process #2420)

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

Re: [Dev] wso2 iot 3.0 connectedup sample

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

Re: [Dev] Error when tenant admin tries to login at the first time

Re: [Dev] Error when tenant admin tries to login at the first time

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.1.0 RC4

[Dev] Error when tenant admin tries to login at the first time

Re: [Dev] wso2 iot 3.0 connectedup sample

[Dev] [VOTE] Release WSO2 API Manager 2.1.0 RC4

[Dev] carbon-mediation 4.6.11 released

Re: [Dev] Please Review and Merge (WebSocket Suppport for Carbon-Messaging)

[Dev] Carbon-mediation 4.6.11 staged

Re: [Dev] Email attachments with CEP output email adapter

Re: [Dev] Please Review and Merge (WebSocket Suppport for Carbon-Messaging)

23 matches

Site Navigation

Mail list logo

Footer information