date:20160728

Re: [Dev] [GSOC 16] Initial Project Progress

2016-07-28 Thread Osura Rathnayake

Hi Isuru,

I'm researching about automation in Azure. Shall we please have the hangout
on Monday?
BTW I will be able to complete the documentation on centralized logging,
monitoring, auto scaling and load balancing by this weekend and I will
update my blog with the progress. Your feedback is much appreciated.

Thank you,

On Fri, Jul 29, 2016 at 9:51 AM, Isuru Haththotuwa  wrote:

> Hi Osura,
>
> On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
> wrote:
>
>> Hi All,
>>
>> Following are the meeting notes of the hangout we had on 25th of July,
>> 2016.
>>
>> *Centralized logging*
>>
>> Azure Log Analytics provides centralized logging which facilitates the
>> users to get logs from a given location in a VM, to a centralized location
>> so that they can analyse and query those logs as they need.
>> *next task - Documentation in terms of a blog post or webinar
>>
>> *Auto scaling*
>>
>> Auto scaling is achieved through scale sets in Azure. Scale set is a set
>> of VMs and auto scaling rules that defines auto scale metrics & actions and
>> the specification of the VMs.
>>
>> *Limitations - Azure portal doesn't support addition of auto scale rules,
>> it only allows to add a simple scale set with a given number of instances.
>> Whereas azure CLI, Powershell and REST API supports full functionality.
>>
>> I have added the template to the github repo which I used to create the
>> auto scale settings which includes the ability to add a custom VM image and
>> auto scale rules. When you deploy from this template you should give the
>> URI of the VM image. you can edit auto scale rules using CLI, Power shell
>> or REST API. Azure Resource Explorer  can be
>> used if you choose REST API to modify.
>>
>> *next tasks - 1) Have to figure out a way to pass application and user
>> data such as usernames and passwords of database, to the VM image through
>> the template. 2) Documentaion
>>
>>
>> *Load balancing*
>>
>> Following are some key terms you need to know.
>>
>> · Backend pool: This is a pool of virtual machines that share
>> the traffic
>>
>> · Probe: The load balancer can probe the health of the various
>> server instances. When a probe fails to respond, the load balancer stops
>> sending new connections to the unhealthy instances. Existing connections
>> are not impacted.
>>
>> · Availability set: when you have a set of virtual machines for
>> the same purpose, azure recommends to add them to an availability set.
>>
>> We can add load balancing rules such that requests coming from a given
>> URL  are shared among the VMs in backend pool. if we configure the load
>> balancer with auto scaling, VMs in the scale set can be added to the
>> backend pool so if the auto scale rules are met, it can scale in or out.
>>
>> *next tasks - 1)  research more about Probe and service health checking.
>> 2)  documentation 3) How to automate the whole deployment process.
>>
> Thanks for the notes.
>
> From the next steps you have mentioned here, deployment automation part is
> very vital for the project completion. Basically we would need to use
> either the CLI or the Rest API and create a few of scripts to do a complete
> deployment on Azure. We can have a hangout today/Monday to discuss the
> progress on the next tasks and the automation aspects.
>
>>
>> [1] https://github.com/osuran/Azure-templates
>>
>> Thank you,
>>
>>
>> On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> Thank you. That will solve the issue.
>>>
>>> On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Osura,

 If you need any customizations/configurations done at the VM startup,
 you can use /etc/rc.local script to do it. Also, if you define the
 JAVA_HOME in a system wide bashrc file at /etc/bash.bashrc it won't get
 deleted when the user home is removed.


 On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
 wrote:

> Hi Imesh,
>
> You can only capture a generalized VM image, so when it's being
> generalized, all of the data in '/home' is erased. Since .bashrc is also 
> in
> '/home/', it's also erased. Only the data that are 
> not
> in '/home' is preserved.
>
> Okay I will try out these steps.
>
> Thanks,
>
> On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
> wrote:
>
>> Hi Osura,
>>
>> On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake > > wrote:
>>
>>> Hi Mentors,
>>>
>>> I could successfully configure auto scaling with a VM which has a
>>> WSO2 application server installed in it. When capturing a VM, it first 
>>> get
>>> deallocated and then generalized.
>>>
>>
>> I'm sorry I did not get this. Can you please elaborate this further?
>> 
>>

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC2

2016-07-28 Thread Anuruddha Liyanarachchi

Hi,

Verified the following:

   1. License headers with the RAT plugin
   2. Tested product distribution
   3. APIM 1.10.0 fully distributed setup in a clustered mesos setup
   4. Tested Marathon LB configurations
   5. Tested Sticky sessions with Marathon LB
   6. Tested following product's distributed setup
   - WSO2ESB 4.9.0
   - WSO2AS 5.3.0
   - WSO2BRS 2.2.0

*[x] - Stable, go ahead and release.*


On Thu, Jul 28, 2016 at 8:23 PM, Akila Ravihansa Perera 
wrote:

> Verified the following:
>
>1. License validity with the RAT plugin
>2. Built and tested Docker images for all products
>3. Tested and verified WSO2 APIM 1.10.0 in Vagrant setup
>
> *[x] Stable - go ahead and release*
>
> On Thu, Jul 28, 2016 at 12:10 PM, Isuru Haththotuwa 
> wrote:
>
>> Verified the following:
>>
>>1. License validity with the RAT plugin
>>2. provisioned APIM 1.10.0, DAS 3.0.1 with vagrant setup and ran a
>>smoke test
>>3. Built the following Docker images with puppet provisioning using
>>the puppet modules from the tag v2.1.0-rc2, and ran a smoke test
>>   - ESB 4.9.0
>>   - CEP 4.0.0
>>   - MB 3.1.0
>>   - DSS 3.5.0
>>   - GREG 5.1.0
>>
>> *[x] Stable - go ahead and release*
>>
>> On Tue, Jul 26, 2016 at 2:07 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> [+1] Stable - Go ahead and release
>>>
>>> Verified the following:
>>>
>>>1. Distribution
>>>2. License Headers using RAT plugin
>>>3. README files
>>>4. Verified following products with docker images built with puppet
>>>provisioning for Mesos platform and tested basic functionalities:
>>>
>>>
>>>- WSO2 ES 2.0.0 (Distributed setup)
>>>- WSO2 AS 5.3.0 (Distributed setup)
>>>- WSO2 ESB 4.9.0 (Distributed setup)
>>>- WSO2 MB 3.1.0
>>>- WSO2 IS 5.1.0
>>>- WSO2 IS KM 5.1.0
>>>- WSO2 APIM 1.10.0
>>>
>>> 5. Tested above products in Mesos platform with secure vault
>>> enabled.
>>> 6. Tested SSO configuration with WSO2 IS 5.1.0 as identity
>>> provider and WSO2 ESB 4.9.0 and WSO2 AS 5.3.0 as service providers.
>>>
>>> Thanks.
>>>
>>> On Mon, Jul 25, 2016 at 6:39 PM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Devs,

 This is the second release candidate (RC2) of WSO2 Puppet Modules 2.1.0
 release. Please download, verify, and vote. Voting will be open for 72
 hours or as needed.

 This release fixes following issues:
 https://wso2.org/jira/browse/PMODULES-16?filter=13155

 Source and binary distribution files:
 https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2

 The tag to be voted upon:
 https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2

 Release verification guide:

 https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment

 Refer modules README files for more details.

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

 Thank you,
 WSO2 PaaS Team.

 --
 *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


>>>
>>>
>>> --
>>> Thanuja Uruththirakodeeswaran
>>> Software Engineer
>>> WSO2 Inc.;http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 774363167
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*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] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC2

2016-07-28 Thread Pubudu Gunatilaka

Hi,

Verified following.

1. License headers
2. Tested following products in default profile.
  - WSO2AM
  - WSO2AS
  - WSO2BPS
  - WSO2GREG
  - WSO2CEP

[x] - Stable, go ahead and release.

Thank you!


On Thu, Jul 28, 2016 at 8:23 PM, Akila Ravihansa Perera 
wrote:

> Verified the following:
>
>1. License validity with the RAT plugin
>2. Built and tested Docker images for all products
>3. Tested and verified WSO2 APIM 1.10.0 in Vagrant setup
>
> *[x] Stable - go ahead and release*
>
> On Thu, Jul 28, 2016 at 12:10 PM, Isuru Haththotuwa 
> wrote:
>
>> Verified the following:
>>
>>1. License validity with the RAT plugin
>>2. provisioned APIM 1.10.0, DAS 3.0.1 with vagrant setup and ran a
>>smoke test
>>3. Built the following Docker images with puppet provisioning using
>>the puppet modules from the tag v2.1.0-rc2, and ran a smoke test
>>   - ESB 4.9.0
>>   - CEP 4.0.0
>>   - MB 3.1.0
>>   - DSS 3.5.0
>>   - GREG 5.1.0
>>
>> *[x] Stable - go ahead and release*
>>
>> On Tue, Jul 26, 2016 at 2:07 PM, Thanuja Uruththirakodeeswaran <
>> thanu...@wso2.com> wrote:
>>
>>> [+1] Stable - Go ahead and release
>>>
>>> Verified the following:
>>>
>>>1. Distribution
>>>2. License Headers using RAT plugin
>>>3. README files
>>>4. Verified following products with docker images built with puppet
>>>provisioning for Mesos platform and tested basic functionalities:
>>>
>>>
>>>- WSO2 ES 2.0.0 (Distributed setup)
>>>- WSO2 AS 5.3.0 (Distributed setup)
>>>- WSO2 ESB 4.9.0 (Distributed setup)
>>>- WSO2 MB 3.1.0
>>>- WSO2 IS 5.1.0
>>>- WSO2 IS KM 5.1.0
>>>- WSO2 APIM 1.10.0
>>>
>>> 5. Tested above products in Mesos platform with secure vault
>>> enabled.
>>> 6. Tested SSO configuration with WSO2 IS 5.1.0 as identity
>>> provider and WSO2 ESB 4.9.0 and WSO2 AS 5.3.0 as service providers.
>>>
>>> Thanks.
>>>
>>> On Mon, Jul 25, 2016 at 6:39 PM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Devs,

 This is the second release candidate (RC2) of WSO2 Puppet Modules 2.1.0
 release. Please download, verify, and vote. Voting will be open for 72
 hours or as needed.

 This release fixes following issues:
 https://wso2.org/jira/browse/PMODULES-16?filter=13155

 Source and binary distribution files:
 https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2

 The tag to be voted upon:
 https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2

 Release verification guide:

 https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment

 Refer modules README files for more details.

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

 Thank you,
 WSO2 PaaS Team.

 --
 *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


>>>
>>>
>>> --
>>> Thanuja Uruththirakodeeswaran
>>> Software Engineer
>>> WSO2 Inc.;http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 774363167
>>>
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>
> ___
> 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>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSOC 16] Initial Project Progress

2016-07-28 Thread Isuru Haththotuwa

Hi Osura,

On Wed, Jul 27, 2016 at 9:17 AM, Osura Rathnayake 
wrote:

> Hi All,
>
> Following are the meeting notes of the hangout we had on 25th of July,
> 2016.
>
> *Centralized logging*
>
> Azure Log Analytics provides centralized logging which facilitates the
> users to get logs from a given location in a VM, to a centralized location
> so that they can analyse and query those logs as they need.
> *next task - Documentation in terms of a blog post or webinar
>
> *Auto scaling*
>
> Auto scaling is achieved through scale sets in Azure. Scale set is a set
> of VMs and auto scaling rules that defines auto scale metrics & actions and
> the specification of the VMs.
>
> *Limitations - Azure portal doesn't support addition of auto scale rules,
> it only allows to add a simple scale set with a given number of instances.
> Whereas azure CLI, Powershell and REST API supports full functionality.
>
> I have added the template to the github repo which I used to create the
> auto scale settings which includes the ability to add a custom VM image and
> auto scale rules. When you deploy from this template you should give the
> URI of the VM image. you can edit auto scale rules using CLI, Power shell
> or REST API. Azure Resource Explorer  can be
> used if you choose REST API to modify.
>
> *next tasks - 1) Have to figure out a way to pass application and user
> data such as usernames and passwords of database, to the VM image through
> the template. 2) Documentaion
>
>
> *Load balancing*
>
> Following are some key terms you need to know.
>
> · Backend pool: This is a pool of virtual machines that share the
> traffic
>
> · Probe: The load balancer can probe the health of the various
> server instances. When a probe fails to respond, the load balancer stops
> sending new connections to the unhealthy instances. Existing connections
> are not impacted.
>
> · Availability set: when you have a set of virtual machines for
> the same purpose, azure recommends to add them to an availability set.
>
> We can add load balancing rules such that requests coming from a given URL
>  are shared among the VMs in backend pool. if we configure the load
> balancer with auto scaling, VMs in the scale set can be added to the
> backend pool so if the auto scale rules are met, it can scale in or out.
>
> *next tasks - 1)  research more about Probe and service health checking.
> 2)  documentation 3) How to automate the whole deployment process.
>
Thanks for the notes.

>From the next steps you have mentioned here, deployment automation part is
very vital for the project completion. Basically we would need to use
either the CLI or the Rest API and create a few of scripts to do a complete
deployment on Azure. We can have a hangout today/Monday to discuss the
progress on the next tasks and the automation aspects.

>
> [1] https://github.com/osuran/Azure-templates
>
> Thank you,
>
>
> On Mon, Jul 25, 2016 at 11:46 AM, Osura Rathnayake 
> wrote:
>
>> Hi Isuru,
>>
>> Thank you. That will solve the issue.
>>
>> On Mon, Jul 25, 2016 at 11:44 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Osura,
>>>
>>> If you need any customizations/configurations done at the VM startup,
>>> you can use /etc/rc.local script to do it. Also, if you define the
>>> JAVA_HOME in a system wide bashrc file at /etc/bash.bashrc it won't get
>>> deleted when the user home is removed.
>>>
>>>
>>> On Mon, Jul 25, 2016 at 11:31 AM, Osura Rathnayake 
>>> wrote:
>>>
 Hi Imesh,

 You can only capture a generalized VM image, so when it's being
 generalized, all of the data in '/home' is erased. Since .bashrc is also in
 '/home/', it's also erased. Only the data that are not
 in '/home' is preserved.

 Okay I will try out these steps.

 Thanks,

 On Mon, Jul 25, 2016 at 10:14 AM, Imesh Gunaratne 
 wrote:

> Hi Osura,
>
> On Sun, Jul 24, 2016 at 6:30 PM, Osura Rathnayake 
> wrote:
>
>> Hi Mentors,
>>
>> I could successfully configure auto scaling with a VM which has a
>> WSO2 application server installed in it. When capturing a VM, it first 
>> get
>> deallocated and then generalized.
>>
>
> I'm sorry I did not get this. Can you please elaborate this further?
> 
>
>
>> So the Java home set in .bashrc is gone in the captured image of the
>> VM. So I had to reset the Java home and also I had to manually start the
>> server after the startup of the VM.
>>
>
> I think you are trying to create a VM image from a running VM
> instance and try to reuse that. Can you please try following:
>
>
>1. Create a VM instance from Ubuntu 14.04 VM image
>2. Extract JDK 1.7 (JAVA_HOME) and the WSO2 server distribution
>(CARBON_HOME) to /opt/ directory.
>

Re: [Dev] GSoC2016-Contact Development Team Feature

2016-07-28 Thread Nathiesha Maddage

Hi all,

Here are the minutes of the meeting I had yesterday (28/07/16) with
Jasintha and Kavith.

During the meeting the current project progress was discussed and
suggestions were made to improve and finalize the development of the
project. Listed below are the key points discussed during the meeting.

1.   Instructions were given on how to add pom.xml, to change its
fields to match with the project , to use Maven tycho plugin and to build
the project using maven.

2.   Suggestions were made on creating and improving interfaces like
ErrorPublisher and ReportGenerator, and how to call the publish method of
all the registered publishers using an iterator in the main controller
class.

3.   We planned to add another option for the user, where he does not
have any gmail and jira credentials, but a remote server would take care of
publishing the error using a common general account. For that I was asked
to write a REST web service that would handle this procedure, and to deploy
it in tomcat for testing. Possibility of using micro services for this was
also discussed.

4.   We planned to add multiple project keys for the jira create issue
option where required, and to assign the project key based on the plugin
that is responsible for the error. For that purpose, it was suggested to
create an extension point of the project, so other plugins can extend it
and define their own project key. Using this all the plugins that have
extended the error reporter plugin and their respective project keys can be
fetched, and a map can be maintained, to be used during the error reporting
process.

5.   To expose the Publisher classes, OSGI services will be introduced
to the project.

6.   It was suggested to create a feature by adding this plugin.

Furthermore instructions were given on the documentation required for the
project, and time frame for documentation was suggested. And I was asked to
send a project plan for the upcoming 3 weeks.

Thanks and regards

Nathiesha

On Tue, Jul 26, 2016 at 7:39 AM, Nathiesha Maddage <
nathieshamadd...@gmail.com> wrote:

> Hi Kavith,
>
> I accepted the invitation.
>
> Thanks and regards
> Nathiesha
>
> On Mon, Jul 25, 2016 at 8:42 PM, Kavith Lokuhewage 
> wrote:
>
>> Hi Nathiesha,
>>
>> I have sent the invitation for the meeting at 2pm-3pm on 28/07/2016 [1].
>>
>> Thanks,
>>
>> [1] https://goo.gl/PLEWQd
>>
>>
>> *Kavith Lokuhewage*
>> Senior Software Engineer
>> WSO2 Inc. - http://wso2.com
>> lean . enterprise . middleware
>> Mobile - +94779145123
>> Linkedin 
>> Twitter 
>>
>> On Mon, Jul 25, 2016 at 8:13 PM, Nathiesha Maddage <
>> nathieshamadd...@gmail.com> wrote:
>>
>>> Hi Kavith,
>>>
>>> How about Thursday evening, for the meeting? I am free after 1 pm.
>>>
>>> Thank you for the examples. I was going to refactor the code by
>>> introducing the interfaces as you suggested during the mid evaluation. But
>>> I was not sure how to do that. I will try to change the code as given in
>>> the examples before the next meeting.
>>>
>>> I think it is good to start converting the project to a maven project as
>>> only a few weeks remaining to finalize the project. We can discuss about
>>> that during the meeting.
>>>
>>> Thanks and regards
>>>
>>> Nathiesha
>>>
>>> On Mon, Jul 25, 2016 at 3:10 PM, Kavith Lokuhewage 
>>> wrote:
>>>
 Hi Nathiesha,

 I noticed that there are some more pending tasks to restructure the
 code base as per the discussion we had during last code review. Just
 putting them down here again, so that you are able to go through again and
 complete any missing parts.

 *Introduce interfaces for the each sub component  to decouple main
 controller logic from implementation specific things*

 For example, right now, the controller class (ErrorReporter) is hardly
 coupled with EmailSender and RemoteJiraConnector. We can think latter two
 as error report publishers and introduce an interface called ErrorPublisher
 as below.

 public interface ErrorPublisher{
 void publish(ReportGenerator reportGen) throws IOException;
 }

 And then EmailSender and RemoreJiraConnector classes can be refactored
 like below.

 public class EmailPublisher implements ErrorPublisher{

  void init () throws IOException{
//init : read preferences for SMTP connection params
  }

 // implement publish method
 void publish(ReportGenerator reportGen) throws IOException{
 init();
//send mail
 }
 }

 public class JiraPublisher implements ErrorPublisher{

  void init () throws IOException{
   //init : read preferences for JIRA resp API connection params
  }

// implement publish method
void publish(ReportGenerator

Re: [Dev] [IS] XML configuration to set the public certificate in IdP

2016-07-28 Thread Tharindu Edirisinghe

Hi Gayan,

Here's a sample command if the IDP is WSO2 Identity Server where you can
export the public certificate in PEM format.



*keytool -exportcert -alias wso2carbon -keypass wso2carbon -keystore
wso2carbon.jks -storepass wso2carbon -rfc -file ispublic_crt.pem*
Then, the certificate file, you  can open with a notepad so you see the
certificate value. Sample is below.

-BEGIN CERTIFICATE-









*MIICNTCCAZ6gAwIBAgIES343gjANBgkqhkiG9w0BAQUFADBVMQswCQYDVQQGEwJVUzELMAkGA1UECAwCQ0ExFjAUBgNVBAcMDU1vdW50YWluIFZpZXcxDTALBgNVBAoMBFdTTzIxEjAQBgNVBAMMCWxvY2FsaG9zdDAeFw0xMDAyMTkwNzAyMjZaFw0zNTAyMTMwNzAyMjZaMFUxCzAJBgNVBAYTAlVTMQswCQYDVQQIDAJDQTEWMBQGA1UEBwwNTW91bnRhaW4gVmlldzENMAsGA1UECgwEV1NPMjESMBAGA1UEAwwJbG9jYWxob3N0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCUp/oV1vWc8/TkQSiAvTousMzOM4asB2iltr2QKozni5aVFu818MpOLZIr8LMnTzWllJvvaA5RAAdpbECb+48FjbBe0hseUdN5HpwvnH/DW8ZccGvk53I6Orq7hLCv1ZHtuOCokghz/ATrhyPq+QktMfXnRS4HrKGJTzxaCcU7OQIDAQABoxIwEDAOBgNVHQ8BAf8EBAMCBPAwDQYJKoZIhvcNAQEFBQADgYEAW5wPR7cr1LAdq+IrR44iQlRG5ITCZXY9hI0PygLP2rHANh+PYfTmxbuOnykNGyhM6FjFLbW2uZHQTY1jMrPprjOrmyK5sjJRO4d1DeGHT/YnIjs9JogRKv4XHECwLtIVdAbIdWHEtVZJyMSktcyysFcvuhPQK8Qc/E/Wq8uHSCo=*
-END CERTIFICATE-

You can copy this certificate value (highlight above) and put in the file.

Note that above is only if the IDP is WSO2 IS. If the IDP is a third party
IDP, then you can get the certificate in PEM format and read the value.

Regards,
TharinduE

On Thu, Jul 28, 2016 at 7:22 PM, Gayan Yalpathwala  wrote:

> Hi devs,
>
> I have a file based IdP configuration in which I need to add the public
> certificate of the IdP. I have tried by adding the certificate content as
> it is, under the  tag, and also tried with the base64 encoded
> version of the same, with no luck. What is the correct way to add this
> configuration?
>
> Thanks,
>
> --
> *Gayan Kaushalya Yalpathwala*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> LK: +94 71 868 2704
> UK: +44 747 844 3609
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

Tharindu Edirisinghe
Senior Software Engineer | WSO2 Inc
Platform Security Team
Blog : tharindue.blogspot.com
mobile : +94 775181586
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

2016-07-28 Thread Chamila De Alwis

On Thu, Jul 28, 2016 at 4:19 AM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> 2. I am currently working on adding the ability to run smoke tests from
> the framework. The idea is to have the capability of having product
> specific smoke tests, then teams with more product knowledge can add smoke
> tests. I will add smoke tests for ESB at this point.
>

Would these be custom tests that are specific to WSO2 Dockerfiles context
or generic tests that aim to test the product code? It would be better if
we can reuse the generic tests, as new tests would not be attractive to the
developers.


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Senior Software Engineer | WSO2
Blog: https://medium.com/@chamilad
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

2016-07-28 Thread Imesh Gunaratne

Hi Abhishek,

On Thursday, July 28, 2016, Abhishek Tiwari 
wrote:

> Hi All,
>
> We had a meeting on the progress and next steps of Dockerfiles test
> framework. Here are the meeting minutes:
>
> 1. We are currently able to test default and puppet provisioning of WSO2
> products. I did a test of next Dockerfiles stable release 1.2.0 and did not
> find any issue.
>

I tried to use the latest code for verifying Dockerfiles latest release but
couldn't even compile the code. Will you be able to provide detailed steps
for doing this?

Thanks

>
> 2. I am currently working on adding the ability to run smoke tests from
> the framework. The idea is to have the capability of having product
> specific smoke tests, then teams with more product knowledge can add smoke
> tests. I will add smoke tests for ESB at this point.
>
> 3. I am going to try to have kubernetes setup on Mac using vagrant and
> will try to deploy ESB docker build on it. If all goes well, we will have a
> demo next week to a much larger audience and collect some feedback.
>
> 4. I will also add instructions to install golang locally on ubuntu on the
> git repo, so that other developers can use the test framework for future
> releases.
>
> Thanks
> Abhishek
>


-- 
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
lean. enterprise. middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [CARBON] Error after installing web app run time features

2016-07-28 Thread Lakshman Udayakantha

Hi,

I got error [1] after doing $subject on carbon 4.4.7 kernel. I installed
web app hosting feature and web app runtime features. It seems it could not
upload web apps. This error getting continuously. How do I prevent this
issue and upload web apps?

[1]

java.lang.NoSuchMethodError: org.apache.coyote.Request.getBytesRead()I

at org.apache.coyote.RequestInfo.updateCounters(RequestInfo.java:143)

at org.apache.coyote.Request.updateCounters(Request.java:533)

at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1140)

at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:625)

at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1749)

at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1708)

at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

at java.lang.Thread.run(Thread.java:745)


Thanks
-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC2

2016-07-28 Thread Akila Ravihansa Perera

Verified the following:

   1. License validity with the RAT plugin
   2. Built and tested Docker images for all products
   3. Tested and verified WSO2 APIM 1.10.0 in Vagrant setup

*[x] Stable - go ahead and release*

On Thu, Jul 28, 2016 at 12:10 PM, Isuru Haththotuwa  wrote:

> Verified the following:
>
>1. License validity with the RAT plugin
>2. provisioned APIM 1.10.0, DAS 3.0.1 with vagrant setup and ran a
>smoke test
>3. Built the following Docker images with puppet provisioning using
>the puppet modules from the tag v2.1.0-rc2, and ran a smoke test
>   - ESB 4.9.0
>   - CEP 4.0.0
>   - MB 3.1.0
>   - DSS 3.5.0
>   - GREG 5.1.0
>
> *[x] Stable - go ahead and release*
>
> On Tue, Jul 26, 2016 at 2:07 PM, Thanuja Uruththirakodeeswaran <
> thanu...@wso2.com> wrote:
>
>> [+1] Stable - Go ahead and release
>>
>> Verified the following:
>>
>>1. Distribution
>>2. License Headers using RAT plugin
>>3. README files
>>4. Verified following products with docker images built with puppet
>>provisioning for Mesos platform and tested basic functionalities:
>>
>>
>>- WSO2 ES 2.0.0 (Distributed setup)
>>- WSO2 AS 5.3.0 (Distributed setup)
>>- WSO2 ESB 4.9.0 (Distributed setup)
>>- WSO2 MB 3.1.0
>>- WSO2 IS 5.1.0
>>- WSO2 IS KM 5.1.0
>>- WSO2 APIM 1.10.0
>>
>> 5. Tested above products in Mesos platform with secure vault
>> enabled.
>> 6. Tested SSO configuration with WSO2 IS 5.1.0 as identity
>> provider and WSO2 ESB 4.9.0 and WSO2 AS 5.3.0 as service providers.
>>
>> Thanks.
>>
>> On Mon, Jul 25, 2016 at 6:39 PM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the second release candidate (RC2) of WSO2 Puppet Modules 2.1.0
>>> release. Please download, verify, and vote. Voting will be open for 72
>>> hours or as needed.
>>>
>>> This release fixes following issues:
>>> https://wso2.org/jira/browse/PMODULES-16?filter=13155
>>>
>>> Source and binary distribution files:
>>> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2
>>>
>>> The tag to be voted upon:
>>> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2
>>>
>>> Release verification guide:
>>>
>>> https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment
>>>
>>> Refer modules README files for more details.
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> Thank you,
>>> WSO2 PaaS Team.
>>>
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Akila Ravihansa Perera
WSO2 Inc.;  http://wso2.com/

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

[Dev] [Architecture] WSO2 Message Broker 3.2.0-M1 Released !

2016-07-28 Thread Indika Sampath

Hi All,

The WSO2 Message Broker team is pleased to announce the 1st milestone
release of WSO2 Message Broker (MB)  3.2.0.

Source & binary distribution files of WSO2 Message Broker :

 Runtime : https://github.com/wso2/product-mb/releases/tag/v3.2.0-M1
 Analytics :
https://github.com/wso2/analytics-mb/releases/tag/v3.2.0-M1

All the known issues identified are listed in JIRA.[1][2].

[1] https://wso2.org/jira/browse/MB
[2] https://wso2.org/jira/browse/ANLYMB

Regards,
~MB Team~

-- 
Indika Sampath
Senior Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 716 424 744
Blog: http://indikasampath.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [BPS] Secure vault for BPMN Analytics configuration

2016-07-28 Thread Waruna Jayaweera

Hi Rajith,
I tried to add the namespace to property but still getting the same
exception. It seems xml validation done by activiti level.

Thanks,
Waruna


On Thu, Jul 28, 2016 at 10:23 AM, Rajith Vitharana  wrote:

> Hi Waruna,
>
> Try adding namespace for "svns" to the property.
>
> Thanks,
>
> On Thu, Jul 28, 2016 at 10:09 AM, Waruna Jayaweera 
> wrote:
>
>> Hi,
>> I have enabled the secure vault for activiti.xml and but I am getting
>> exception [1] during server  start up.  Carbon secure vault implementation
>> will add svns:secretAlias to activiti.xml as follows.
>> > value="admin">password
>>
>> But
>> org.activiti.engine.impl.cfg.BeansConfigurationHelper.parseProcessEngineConfiguration
>> cannot parse the xml after that. Any idea how we can fix that?
>>
>> [1]  ERROR {org.wso2.carbon.bpmn.core.internal.BPMNServiceComponent} -
>>  Failed to initialize the BPMN core component.
>> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
>> Line 35 in XML document from resource loaded through InputStream is
>> invalid; nested exception is org.xml.sax.SAXParseException:
>> cvc-complex-type.3.2.2: Attribute 'svns:secretAlias' is not allowed to
>> appear in element 'property'.
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
>> at
>> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
>> at
>> org.activiti.engine.impl.cfg.BeansConfigurationHelper.parseProcessEngineConfiguration(BeansConfigurationHelper.java:35)
>> at
>> org.activiti.engine.impl.cfg.BeansConfigurationHelper.parseProcessEngineConfigurationFromInputStream(BeansConfigurationHelper.java:43)
>> at
>> org.activiti.engine.ProcessEngineConfiguration.createProcessEngineConfigurationFromInputStream(ProcessEngineConfiguration.java:244)
>> at
>> org.activiti.engine.ProcessEngineConfiguration.createProcessEngineConfigurationFromInputStream(ProcessEngineConfiguration.java:240)
>> at
>> org.wso2.carbon.bpmn.core.ActivitiEngineBuilder.buildEngine(ActivitiEngineBuilder.java:89)
>> at
>> org.wso2.carbon.bpmn.core.internal.BPMNServiceComponent.activate(BPMNServiceComponent.java:49)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:606)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:345)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>> at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>> at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:451)
>> at
>> org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.registerServices(DataSourceServiceComponent.java:126)
>> at
>> org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.initSuperTenantUserDataSources(DataSourceServiceComponent.java:221)
>> at
>> org.wso2.carbon.ndatasource.core.internal.DataSourceServiceComponent.checkInitTenantUserDataSources(DataSourceServiceComponent.java:206)
>> at
>>

[Dev] [IS] XML configuration to set the public certificate in IdP

2016-07-28 Thread Gayan Yalpathwala

Hi devs,

I have a file based IdP configuration in which I need to add the public
certificate of the IdP. I have tried by adding the certificate content as
it is, under the  tag, and also tried with the base64 encoded
version of the same, with no luck. What is the correct way to add this
configuration?

Thanks,

-- 
*Gayan Kaushalya Yalpathwala*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

LK: +94 71 868 2704
UK: +44 747 844 3609


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

[Dev] Manually create heapdump in IBM JDK

2016-07-28 Thread Himasha Guruge

Hi,

Has anyone performed $subject? I came across [1] , where you need to
process the kill command for the process id to get the heap dump. What I'm
looking for is a way to create it like a snapshot. Some command like how we
use jmap. ( jmap -dump:format=b,file=filename.hprof )

[1] http://www-01.ibm.com/support/docview.wss?uid=swg21597830

Thanks,
Himasha Guruge
*Software Engineer*
WS*O2* *Inc.*
Mobile: +94 777459299
himas...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Nuwan Dias

Hi all,

We've received 12 +1s and no -1s on this tread. We're closing this vote
hence and will be releasing RC5 as API Manager 2.0.0 GA. Thanks for all who
tested and voted.

Thanks,
NuwanD.

On Thu, Jul 28, 2016 at 4:18 PM, Harsha Kumara  wrote:

> Tested Throttling Levels of Resource Level, API Level, Subscription Level,
> Application Level in both tenant and super tenant mode. Tested Blocking
> conditions in both super tenant and tenant mode. Tested custom rules in
> super tenant mode. Tested creation of throttling policies in admin
> dashboard and applicability of them. Tested rate limiting and hard level
> throttling in super tenant and tenant mode. No issue found.
>
> +1 - Stable - go ahead and release.
>
> Thanks,
> Harsha
>
> On Thu, Jul 28, 2016 at 3:33 PM, Thilini Cooray  wrote:
>
>> Tested
>>
>>- API creation and publishing with creator and publisher user
>>permissions on multi-tenant environment
>>- SSO on API publisher and store with WSO2 IS 5.2.0 Beta
>>- Store REST API
>>
>> +1 - Stable - go ahead and release.
>>
>> Thanks.
>>
>>
>> On Thu, Jul 28, 2016 at 3:03 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> On Thu, Jul 28, 2016 at 2:58 PM, Chamin Dias  wrote:
>>>
 Tested funcions in Store and self registration.

 [+] Stable - go ahead and release.

 Thanks

 On Thu, Jul 28, 2016 at 2:56 PM, Malintha Amarasinghe <
 malint...@wso2.com> wrote:

> Tested in both ST and Tenant mode:
> 1. Basic APIM functionality
> 2. SSO with and without reverse proxy
> 3. Tested Store/Publisher/Admin CXF Rest APIs
> 4. response caching
>
> [+] Stable : go ahead and release
>
>
> On Thu, Jul 28, 2016 at 2:42 PM, Nirmal Fernando 
> wrote:
>
>> Tested API analytics
>> [+] Stable - go ahead and release.
>>
>> On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan <
>> abima...@wso2.com> wrote:
>>
>>> *WSO2 API Manager 2.0.0-RC5 Released*
>>>
>>> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>>>
>>> Source & binary distribution files of API Manager 2.0.0-RC5 :
>>>
>>>  Runtime : 
>>> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
>>> *
>>>  Analytics : 
>>> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
>>> *
>>>
>>> Please download, test the product and vote. Vote will be open for
>>> 72 hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>> 
>>>   
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Chamin Dias
 *Software Engineer*
 Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
 Email : cham...@wso2.com
 Blog : https://chamindias.wordpress.com/

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


>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>>

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Harsha Kumara

Tested Throttling Levels of Resource Level, API Level, Subscription Level,
Application Level in both tenant and super tenant mode. Tested Blocking
conditions in both super tenant and tenant mode. Tested custom rules in
super tenant mode. Tested creation of throttling policies in admin
dashboard and applicability of them. Tested rate limiting and hard level
throttling in super tenant and tenant mode. No issue found.

+1 - Stable - go ahead and release.

Thanks,
Harsha

On Thu, Jul 28, 2016 at 3:33 PM, Thilini Cooray  wrote:

> Tested
>
>- API creation and publishing with creator and publisher user
>permissions on multi-tenant environment
>- SSO on API publisher and store with WSO2 IS 5.2.0 Beta
>- Store REST API
>
> +1 - Stable - go ahead and release.
>
> Thanks.
>
>
> On Thu, Jul 28, 2016 at 3:03 PM, Abimaran Kugathasan 
> wrote:
>
>> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>>
>> [+] Stable - go ahead and release.
>>
>> On Thu, Jul 28, 2016 at 2:58 PM, Chamin Dias  wrote:
>>
>>> Tested funcions in Store and self registration.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks
>>>
>>> On Thu, Jul 28, 2016 at 2:56 PM, Malintha Amarasinghe <
>>> malint...@wso2.com> wrote:
>>>
 Tested in both ST and Tenant mode:
 1. Basic APIM functionality
 2. SSO with and without reverse proxy
 3. Tested Store/Publisher/Admin CXF Rest APIs
 4. response caching

 [+] Stable : go ahead and release


 On Thu, Jul 28, 2016 at 2:42 PM, Nirmal Fernando 
 wrote:

> Tested API analytics
> [+] Stable - go ahead and release.
>
> On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan <
> abima...@wso2.com> wrote:
>
>> *WSO2 API Manager 2.0.0-RC5 Released*
>>
>> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC5 :
>>
>>  Runtime : 
>> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
>> *
>>  Analytics : 
>> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
>> *
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer - API Technologies
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>>   
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 Mobile : +94 712383306

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


>>>
>>>
>>> --
>>> Chamin Dias
>>> *Software Engineer*
>>> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
>>> Email : cham...@wso2.com
>>> Blog : https://chamindias.wordpress.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer - API Technologies
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards,
>
> *Thilini Cooray*
> Software Engineer
> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
> E-mail : thili...@wso2.com
>
>

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Harsha Kumara

Tested Throttling Levels of Resource Level, API Level, Subscription Level,
Application Level in both tenant and super tenant mode. Tested Blocking
conditions in both super tenant and tenant mode. Tested custom rules in
super tenant mode. Tested creation of throttling policies in admin
dashboard and applicability of them. Tested rate limiting and hard level
throttling in super tenant and tenant mode. No issue found.

+1 - Stable - go ahead and release.

Thanks,
Harsha

On Thu, Jul 28, 2016 at 3:33 PM, Thilini Cooray  wrote:

> Tested
>
>- API creation and publishing with creator and publisher user
>permissions on multi-tenant environment
>- SSO on API publisher and store with WSO2 IS 5.2.0 Beta
>- Store REST API
>
> +1 - Stable - go ahead and release.
>
> Thanks.
>
>
> On Thu, Jul 28, 2016 at 3:03 PM, Abimaran Kugathasan 
> wrote:
>
>> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>>
>> [+] Stable - go ahead and release.
>>
>> On Thu, Jul 28, 2016 at 2:58 PM, Chamin Dias  wrote:
>>
>>> Tested funcions in Store and self registration.
>>>
>>> [+] Stable - go ahead and release.
>>>
>>> Thanks
>>>
>>> On Thu, Jul 28, 2016 at 2:56 PM, Malintha Amarasinghe <
>>> malint...@wso2.com> wrote:
>>>
 Tested in both ST and Tenant mode:
 1. Basic APIM functionality
 2. SSO with and without reverse proxy
 3. Tested Store/Publisher/Admin CXF Rest APIs
 4. response caching

 [+] Stable : go ahead and release


 On Thu, Jul 28, 2016 at 2:42 PM, Nirmal Fernando 
 wrote:

> Tested API analytics
> [+] Stable - go ahead and release.
>
> On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan <
> abima...@wso2.com> wrote:
>
>> *WSO2 API Manager 2.0.0-RC5 Released*
>>
>> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC5 :
>>
>>  Runtime : 
>> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
>> *
>>  Analytics : 
>> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
>> *
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer - API Technologies
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>>   
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 Mobile : +94 712383306

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


>>>
>>>
>>> --
>>> Chamin Dias
>>> *Software Engineer*
>>> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
>>> Email : cham...@wso2.com
>>> Blog : https://chamindias.wordpress.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer - API Technologies
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Best Regards,
>
> *Thilini Cooray*
> Software Engineer
> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
> E-mail : thili...@wso2.com
>
>

Re: [Dev] Fwd: Releasing an update for DevS kernel 4.1.0

2016-07-28 Thread Viraj Rajaguru

Hi Kavith,

I tested the update. It works. We can go ahead and publish it to product
dist.

Thanks,
Viraj.

On Thu, Jul 28, 2016 at 10:21 AM, Kavith Lokuhewage  wrote:

> Hi Viraj,
>
> Update is staged at [1] and available via common staging update URL [2]
> for kernel 4.1.0.
> Please verify the update, upon verification, we will get it published to
> product dist server.
>
> Thanks,
>
> [1]
> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/platform-bundles/updates/platform-p2-4.1.0-201607270157/
>
> [2]
> http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/updates/
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Tue, Jul 26, 2016 at 8:10 PM, Viraj Rajaguru  wrote:
>
>> Thanks Kavith !
>>
>> On Tue, Jul 26, 2016 at 8:08 PM, Kavith Lokuhewage 
>> wrote:
>>
>>> Hi Viraj,
>>>
>>> I will prepare platform update and let you know once it is published.
>>>
>>> Thanks,
>>>
>>> On 26 Jul 2016 8:02 p.m., "Viraj Rajaguru"  wrote:
>>>
 Hi Kavith,

 Sent a pull request[1].

 Thanks,
 Viraj.

 [1] - https://github.com/wso2/devstudio-tooling-platform/pull/1

 On Tue, Jul 26, 2016 at 2:17 PM, Kavith Lokuhewage 
 wrote:

> Hi Viraj,
>
> Please send the PR with the fix to master branch. We will release the
> update for 4.1.0.
>
> Thanks,
>
> *Kavith Lokuhewage*
> Senior Software Engineer
> WSO2 Inc. - http://wso2.com
> lean . enterprise . middleware
> Mobile - +94779145123
> Linkedin 
> Twitter 
>
> On Fri, Jul 22, 2016 at 3:47 PM, Viraj Rajaguru 
> wrote:
>
>>
>> -- Forwarded message --
>> From: Viraj Rajaguru 
>> Date: Fri, Jul 22, 2016 at 3:46 PM
>> Subject: Releasing an update for DevS kernel 4.1.0
>> To: Jasintha Dasanayake , Kavith Lokuhewage <
>> kav...@wso2.com>, Susinda Perera , Sohani
>> Weerasinghe , Nuwan Pallewela ,
>> Chanaka Fernando , Jagath Sisirakumara
>> Ariyarathne 
>>
>>
>> Hi DevS kernel team,
>>
>> We faced an issue while deploying CAR files when webContextRoot is
>> enabled in carbon.xml. See the public Jira[1]. This needs to be fixed in
>> "devstudio-tooling-platform". Can we have this fix as an update for 
>> Kernel
>> 4.1.0 since this is a blocker for ESB tolling release. Fix is attached to
>> the jira.
>>
>> BTW, is there any 4.1.0 update branch so that we can send pull
>> requests?
>>
>> Thanks,
>> Viraj.
>>
>> [1] - https://wso2.org/jira/browse/DEVTOOLESB-637
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>>
>>
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


 --
 Viraj Rajaguru
 Associate Technical Lead
 WSO2 Inc. : http://wso2.com

 Mobile: +94 77 3683068




>>
>>
>> --
>> Viraj Rajaguru
>> Associate Technical Lead
>> WSO2 Inc. : http://wso2.com
>>
>> Mobile: +94 77 3683068
>>
>>
>>
>>
>


-- 
Viraj Rajaguru
Associate Technical Lead
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Thilini Cooray

Tested

   - API creation and publishing with creator and publisher user
   permissions on multi-tenant environment
   - SSO on API publisher and store with WSO2 IS 5.2.0 Beta
   - Store REST API

+1 - Stable - go ahead and release.

Thanks.


On Thu, Jul 28, 2016 at 3:03 PM, Abimaran Kugathasan 
wrote:

> Tested Dynamic Endpoint, API Subscription/blocking/resubscription.
>
> [+] Stable - go ahead and release.
>
> On Thu, Jul 28, 2016 at 2:58 PM, Chamin Dias  wrote:
>
>> Tested funcions in Store and self registration.
>>
>> [+] Stable - go ahead and release.
>>
>> Thanks
>>
>> On Thu, Jul 28, 2016 at 2:56 PM, Malintha Amarasinghe > > wrote:
>>
>>> Tested in both ST and Tenant mode:
>>> 1. Basic APIM functionality
>>> 2. SSO with and without reverse proxy
>>> 3. Tested Store/Publisher/Admin CXF Rest APIs
>>> 4. response caching
>>>
>>> [+] Stable : go ahead and release
>>>
>>>
>>> On Thu, Jul 28, 2016 at 2:42 PM, Nirmal Fernando 
>>> wrote:
>>>
 Tested API analytics
 [+] Stable - go ahead and release.

 On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan  wrote:

> *WSO2 API Manager 2.0.0-RC5 Released*
>
> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC5 :
>
>  Runtime : 
> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
> *
>  Analytics : 
> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
> *
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


 --

 Thanks & regards,
 Nirmal

 Team Lead - WSO2 Machine Learner
 Associate Technical Lead - Data Technologies Team, WSO2 Inc.
 Mobile: +94715779733
 Blog: http://nirmalfdo.blogspot.com/



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


>>>
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Chamin Dias
>> *Software Engineer*
>> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
>> Email : cham...@wso2.com
>> Blog : https://chamindias.wordpress.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Best Regards,

*Thilini Cooray*
Software Engineer
Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
E-mail : thili...@wso2.com

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC Dockerfiles] Meeting minutes

2016-07-28 Thread Vishanth Balasubramaniam

Hi,

Good work so far Abhishek. We'll focus on getting the Kubernetes setup done
soon and test it on that.

Regards,
Vishanth

On Thu, Jul 28, 2016 at 2:49 PM, Abhishek Tiwari <
abhishek.tiwari0...@gmail.com> wrote:

> Hi All,
>
> We had a meeting on the progress and next steps of Dockerfiles test
> framework. Here are the meeting minutes:
>
> 1. We are currently able to test default and puppet provisioning of WSO2
> products. I did a test of next Dockerfiles stable release 1.2.0 and did not
> find any issue.
>
> 2. I am currently working on adding the ability to run smoke tests from
> the framework. The idea is to have the capability of having product
> specific smoke tests, then teams with more product knowledge can add smoke
> tests. I will add smoke tests for ESB at this point.
>
> 3. I am going to try to have kubernetes setup on Mac using vagrant and
> will try to deploy ESB docker build on it. If all goes well, we will have a
> demo next week to a much larger audience and collect some feedback.
>
> 4. I will also add instructions to install golang locally on ubuntu on the
> git repo, so that other developers can use the test framework for future
> releases.
>
> Thanks
> Abhishek
>



-- 
*Vishanth Balasubramaniam*
Committer & PMC Member, Apache Stratos,
Software Engineer, WSO2 Inc.; http://wso2.com

mobile: *+94 77 17 377 18*
about me: *http://about.me/vishanth *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Abimaran Kugathasan

Tested Dynamic Endpoint, API Subscription/blocking/resubscription.

[+] Stable - go ahead and release.

On Thu, Jul 28, 2016 at 2:58 PM, Chamin Dias  wrote:

> Tested funcions in Store and self registration.
>
> [+] Stable - go ahead and release.
>
> Thanks
>
> On Thu, Jul 28, 2016 at 2:56 PM, Malintha Amarasinghe 
> wrote:
>
>> Tested in both ST and Tenant mode:
>> 1. Basic APIM functionality
>> 2. SSO with and without reverse proxy
>> 3. Tested Store/Publisher/Admin CXF Rest APIs
>> 4. response caching
>>
>> [+] Stable : go ahead and release
>>
>>
>> On Thu, Jul 28, 2016 at 2:42 PM, Nirmal Fernando  wrote:
>>
>>> Tested API analytics
>>> [+] Stable - go ahead and release.
>>>
>>> On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan 
>>> wrote:
>>>
 *WSO2 API Manager 2.0.0-RC5 Released*

 This is the 5th Release Candidate of the WSO2 API Manager 2.0.0

 Source & binary distribution files of API Manager 2.0.0-RC5 :

  Runtime : 
 *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
 *
  Analytics : 
 *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
 *

 Please download, test the product and vote. Vote will be open for 72
 hours or as needed.
 Refer to github readme for guides.

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

 --
 Thanks
 Abimaran Kugathasan
 Senior Software Engineer - API Technologies

 Email : abima...@wso2.com
 Mobile : +94 773922820

 
 
   
 


 ___
 Architecture mailing list
 architect...@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Team Lead - WSO2 Machine Learner
>>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Chamin Dias
> *Software Engineer*
> Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
> Email : cham...@wso2.com
> Blog : https://chamindias.wordpress.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


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

Re: [Dev] When to use NO_ENTITY_BODY

2016-07-28 Thread Vijitha Ekanayake

[adding commit revision]
https://github.com/VijithaEkanayake/wso2-synapse-1/commit/ba2ba967079de74971454064f126360a38a9c878

On Thu, Jul 28, 2016 at 3:02 PM, Vijitha Ekanayake 
wrote:

> Hi Udara,
>
> We need to remove NO_ENTITY_BODY property if we want to generate a
> response from the ESB itself to a request without an entity body, for
> example, GET request. According to commit[1], NO_ENTITY_BODY property
> programmatically removed from the code as an improvement in PayloadFactory
> mediator. Therefore no need to add property[1] if we are using payload
> factory mediator in synapse configurations.
>
> [1]. 
>
> Thanks.
>
> On Thu, Jul 28, 2016 at 2:29 PM, Udara Liyanage  wrote:
>
>> Hi,
>>
>> According to [1], NO_ENTITY_BODY property is set if the client want to
>> get response with entities for requests which does not have an entity body
>> such as GET and DELETE.
>>
>> 1) My first question according to [1] by default ESB will not send a
>> response for requests without body. That is OK for DELETE, but how about
>> GET. GET are supposed to get a response.
>>
>> 2) I have below api definition. with a simple GET which generates a
>> simple response.
>> I get a response for GET even I do or don't remove NO_ENTITY_BODY
>> property. Behavior is same for DELETE too.
>>
>> http://ws.apache.org/ns/synapse; name="GetTickets"
>> context="/tickets">
>>
>>   
>>  
>> {"fname":"udara","lname":liyanage""}
>> 
>>  
>>  
>>   
>>
>> 
>>
>> *Request and response*
>> curl -X GET -H "Authorization: Token" "http://localhost:8280/tickets/;
>> {"name":"udara","age":"10"}
>>
>> [1]
>> https://docs.wso2.com/display/ESB403/HTTP+Transport+Specific+Properties
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> Blog: http://udaraliyanage.wordpress.com
>>
>
>
>
> --
> Vijitha Ekanayake
> Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>



-- 
Vijitha Ekanayake
Software Engineer*, *WSO2, Inc.; http://wso2.com/
Mobile : +94 777 24 73 39 | +94 718 74 44 08
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] When to use NO_ENTITY_BODY

2016-07-28 Thread Vijitha Ekanayake

Hi Udara,

We need to remove NO_ENTITY_BODY property if we want to generate a response
from the ESB itself to a request without an entity body, for example, GET
request. According to commit[1], NO_ENTITY_BODY property programmatically
removed from the code as an improvement in PayloadFactory mediator.
Therefore no need to add property[1] if we are using payload factory
mediator in synapse configurations.

[1]. 

Thanks.

On Thu, Jul 28, 2016 at 2:29 PM, Udara Liyanage  wrote:

> Hi,
>
> According to [1], NO_ENTITY_BODY property is set if the client want to get
> response with entities for requests which does not have an entity body such
> as GET and DELETE.
>
> 1) My first question according to [1] by default ESB will not send a
> response for requests without body. That is OK for DELETE, but how about
> GET. GET are supposed to get a response.
>
> 2) I have below api definition. with a simple GET which generates a simple
> response.
> I get a response for GET even I do or don't remove NO_ENTITY_BODY
> property. Behavior is same for DELETE too.
>
> http://ws.apache.org/ns/synapse; name="GetTickets"
> context="/tickets">
>
>   
>  
> {"fname":"udara","lname":liyanage""}
> 
>  
>  
>   
>
> 
>
> *Request and response*
> curl -X GET -H "Authorization: Token" "http://localhost:8280/tickets/;
> {"name":"udara","age":"10"}
>
> [1]
> https://docs.wso2.com/display/ESB403/HTTP+Transport+Specific+Properties
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> Blog: http://udaraliyanage.wordpress.com
>



-- 
Vijitha Ekanayake
Software Engineer*, *WSO2, Inc.; http://wso2.com/
Mobile : +94 777 24 73 39 | +94 718 74 44 08
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Chamin Dias

Tested funcions in Store and self registration.

[+] Stable - go ahead and release.

Thanks

On Thu, Jul 28, 2016 at 2:56 PM, Malintha Amarasinghe 
wrote:

> Tested in both ST and Tenant mode:
> 1. Basic APIM functionality
> 2. SSO with and without reverse proxy
> 3. Tested Store/Publisher/Admin CXF Rest APIs
> 4. response caching
>
> [+] Stable : go ahead and release
>
>
> On Thu, Jul 28, 2016 at 2:42 PM, Nirmal Fernando  wrote:
>
>> Tested API analytics
>> [+] Stable - go ahead and release.
>>
>> On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan 
>> wrote:
>>
>>> *WSO2 API Manager 2.0.0-RC5 Released*
>>>
>>> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>>>
>>> Source & binary distribution files of API Manager 2.0.0-RC5 :
>>>
>>>  Runtime : 
>>> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
>>> *
>>>  Analytics : 
>>> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
>>> *
>>>
>>> Please download, test the product and vote. Vote will be open for 72
>>> hours or as needed.
>>> Refer to github readme for guides.
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (please explain why)
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chamin Dias
*Software Engineer*
Mobile : +94 (0) 716 097455 <%2B94%20%280%29%20773%20451194>
Email : cham...@wso2.com
Blog : https://chamindias.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Malintha Amarasinghe

Tested in both ST and Tenant mode:
1. Basic APIM functionality
2. SSO with and without reverse proxy
3. Tested Store/Publisher/Admin CXF Rest APIs
4. response caching

[+] Stable : go ahead and release


On Thu, Jul 28, 2016 at 2:42 PM, Nirmal Fernando  wrote:

> Tested API analytics
> [+] Stable - go ahead and release.
>
> On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan 
> wrote:
>
>> *WSO2 API Manager 2.0.0-RC5 Released*
>>
>> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC5 :
>>
>>  Runtime : 
>> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
>> *
>>  Analytics : 
>> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
>> *
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer - API Technologies
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

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

[Dev] [GSoC Dockerfiles] Meeting minutes

2016-07-28 Thread Abhishek Tiwari

Hi All,

We had a meeting on the progress and next steps of Dockerfiles test
framework. Here are the meeting minutes:

1. We are currently able to test default and puppet provisioning of WSO2
products. I did a test of next Dockerfiles stable release 1.2.0 and did not
find any issue.

2. I am currently working on adding the ability to run smoke tests from the
framework. The idea is to have the capability of having product specific
smoke tests, then teams with more product knowledge can add smoke tests. I
will add smoke tests for ESB at this point.

3. I am going to try to have kubernetes setup on Mac using vagrant and will
try to deploy ESB docker build on it. If all goes well, we will have a demo
next week to a much larger audience and collect some feedback.

4. I will also add instructions to install golang locally on ubuntu on the
git repo, so that other developers can use the test framework for future
releases.

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

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Nirmal Fernando

Tested API analytics
[+] Stable - go ahead and release.

On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan 
wrote:

> *WSO2 API Manager 2.0.0-RC5 Released*
>
> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC5 :
>
>  Runtime : 
> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
> *
>  Analytics : 
> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
> *
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, 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] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Sam Sivayogam

Test New API Notifications and Custom Rules

No issues found.

[+] Stable - go ahead and release

On Thu, Jul 28, 2016 at 2:35 PM, Amila De Silva  wrote:

> Tested workflows. No issues found.
>
> [+] Stable - go ahead and release
>
> On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan 
> wrote:
>
>> *WSO2 API Manager 2.0.0-RC5 Released*
>>
>> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC5 :
>>
>>  Runtime : 
>> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
>> *
>>  Analytics : 
>> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
>> *
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer - API Technologies
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Amila De Silva*
>
> WSO2 Inc.
> mobile :(+94) 775119302
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sam Sivayogam*

Software Engineer
Mobile  : +94 772 906 439
Office   : +94 112 145 345
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Joseph Fonseka

Tested the following

1. Store & Publisher functionality.
2. Swagger Editor & Swagger UI with YAML import.
3. Latest security fixes.
4. Scopes and Grant-types.

No Issues found.

[+] Stable - go ahead and release.

On Thu, Jul 28, 2016 at 2:34 PM, Chamalee De Silva 
wrote:

> Hi,
> I have done following tests.
>
>  Basic API Flow
>  SAML2 Grant type with IS 5.2.0 beta2
>
>
> No issues found.
>
> [+] Stable - go ahead and release
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>

-- 

-- 
*Joseph Fonseka*
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 772 512 430
skype: jpfonseka

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

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Roshan Wijesena

Tested below,

1. SSO security fix.
2. SSO with IS 5.1.0
3. Basic APIM flow.
4. CSRF functionality in admin portal.

No issues found.

[+] Stable - go ahead and release.


On Thu, Jul 28, 2016 at 2:25 PM, Uvindra Dias Jayasinha 
wrote:

> Tested below with secure vault with custom key store
>
> 1. API creation and publication with different user roles and invocation
> tenant/super tenant
> 2. Stats tenant/super tenant(Store and Publisher)
> 3. Log Analyzer tenant/super tenant
> 4. API creation and publication with different user roles for tenant/super
> tenant
>
> No issues found
>
> [+] Stable - go ahead and release.
>
> On 28 July 2016 at 02:02, Abimaran Kugathasan  wrote:
>
>> *WSO2 API Manager 2.0.0-RC5 Released*
>>
>> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>>
>> Source & binary distribution files of API Manager 2.0.0-RC5 :
>>
>>  Runtime : 
>> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
>> *
>>  Analytics : 
>> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
>> *
>>
>> Please download, test the product and vote. Vote will be open for 72
>> hours or as needed.
>> Refer to github readme for guides.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer - API Technologies
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820
>>
>> 
>> 
>>   
>> 
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94719154640*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Amila De Silva

Tested workflows. No issues found.

[+] Stable - go ahead and release

On Thu, Jul 28, 2016 at 2:02 AM, Abimaran Kugathasan 
wrote:

> *WSO2 API Manager 2.0.0-RC5 Released*
>
> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC5 :
>
>  Runtime : 
> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
> *
>  Analytics : 
> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
> *
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Amila De Silva*

WSO2 Inc.
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Chamalee De Silva

Hi,
I have done following tests.

 Basic API Flow
 SAML2 Grant type with IS 5.2.0 beta2


No issues found.

[+] Stable - go ahead and release
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] When to use NO_ENTITY_BODY

2016-07-28 Thread Udara Liyanage

Hi,

According to [1], NO_ENTITY_BODY property is set if the client want to get
response with entities for requests which does not have an entity body such
as GET and DELETE.

1) My first question according to [1] by default ESB will not send a
response for requests without body. That is OK for DELETE, but how about
GET. GET are supposed to get a response.

2) I have below api definition. with a simple GET which generates a simple
response.
I get a response for GET even I do or don't remove NO_ENTITY_BODY
property. Behavior is same for DELETE too.

http://ws.apache.org/ns/synapse; name="GetTickets"
context="/tickets">
   
  
 
{"fname":"udara","lname":liyanage""}

 
 
  
   


*Request and response*
curl -X GET -H "Authorization: Token" "http://localhost:8280/tickets/;
{"name":"udara","age":"10"}

[1] https://docs.wso2.com/display/ESB403/HTTP+Transport+Specific+Properties
-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

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

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

2016-07-28 Thread Uvindra Dias Jayasinha

Tested below with secure vault with custom key store

1. API creation and publication with different user roles and invocation
tenant/super tenant
2. Stats tenant/super tenant(Store and Publisher)
3. Log Analyzer tenant/super tenant
4. API creation and publication with different user roles for tenant/super
tenant

No issues found

[+] Stable - go ahead and release.

On 28 July 2016 at 02:02, Abimaran Kugathasan  wrote:

> *WSO2 API Manager 2.0.0-RC5 Released*
>
> This is the 5th Release Candidate of the WSO2 API Manager 2.0.0
>
> Source & binary distribution files of API Manager 2.0.0-RC5 :
>
>  Runtime : 
> *https://github.com/wso2/product-apim/releases/tag/v2.0.0-rc5
> *
>  Analytics : 
> *https://github.com/wso2/analytics-apim/releases/tag/v2.0.0-rc5
> *
>
> Please download, test the product and vote. Vote will be open for 72
> hours or as needed.
> Refer to github readme for guides.
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-]  Broken - do not release (please explain why)
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Regards,
Uvindra

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

Re: [Dev] [Gsoc2016] [PC] Web (Javascript / D3) based BPMN editor to support a subset of commonly used BPMN constructs

2016-07-28 Thread Hasitha Aravinda

Heshan,

Could you please update this mail with your current progress ? Also can you
update the git repo with latest code base. It was last updated 23 days ago.

Thanks,
Hasitha.

On Thu, Jul 14, 2016 at 9:25 AM, Heshan Jayasinghe 
wrote:

> Hi,
> I added following element to BPMN tool box.I added only boundary events
> instead of Intermediate event because both look like same and last
> discussion we plan to come up with only boundary events.
> Intermediate event have
>   time catching event
>   Signal catching event
>   Message catching Event,etc.
> Boundary event have
>  Time Boundary Event
>  Error Boundary Event
>  Message Boundary Event
>  Signal Boundary Event,etc.
> Do I need to add both intermediate event and boundary event or only
> boundary event is enough?
> If there any changes in tool box please let me know.
>
> Start Event
>
>-  Start Event
>-  Time Event
>-  Message Start Event
>-  Error Start Event
>
> End Event
>
>-  End Event
>-  Error End Event
>-  Terminate End Even
>-  Cancel End Event
>
> Task
>
>-   User Task
>-   Script Task
>-   Mail Task
>-   Receive Task
>
> Boundary Event
>
>-  Time Boundary Event
>-  Error Boundary Event
>-  Message Boundary Event
>-  Signal Boundary Event
>
> Gateway
>
>-  Parallel Gateway
>-   Exclusive Gateway
>-   Inclusive Gateway
>-   Event Gateway
>
> Connections
>
>-   Sequence Flow
>
>
> Thank you!
> regards,
> Heshan jayasinghe
>
> On Thu, Jul 7, 2016 at 8:50 AM, Isuru Wijesinghe  wrote:
>
>> Hi Heshan,
>>
>> Please add only *general*, *main config* and *form* properties for each
>> component as you mentioned in your proposal.
>>
>> Thanks,
>> Isuru.
>>
>> On Wed, Jul 6, 2016 at 9:42 AM, Heshan Jayasinghe 
>> wrote:
>>
>>> Hi,
>>> As we discussed in last meeting this week we plan to finish
>>>
>>>- flow reposition when BPMN element position changes.
>>>- task resizing
>>>- text attaching
>>>- changing task/event/gateway type using property (element icon
>>>changed with property)
>>>
>>>
>>> I created "flow reposition when BPMN element position changes" and "task
>>> resizing" but not totally completed.I think i can finish it with in this
>>> week.Can you please send me what are the properties you need for each
>>> element.Then i can complete it with in this week.
>>>
>>> github url = https://github.com/heshanjse/BPMNEditor  ( last week
>>> update)
>>>
>>> Thank You!
>>> regards,
>>> Heshan Jayasinghe
>>>
>>> On Tue, Jun 21, 2016 at 6:59 AM, Heshan Jayasinghe 
>>> wrote:
>>>
 github url - https://github.com/heshanjse/BPMNEditor

 On Tue, Jun 21, 2016 at 6:57 AM, Heshan Jayasinghe 
 wrote:

> Hi Isuru,
>
> This is the milestone plan we discussed in the last week.
>
> 24/6  - draw flows when moving a node
>  - add properties to the flow
>  - create delete functionality to every node.
>  - add arrow and text to the toolbox
> 1/7- add text to the task
>  - task resizing
>  - change task/event/gateway icon according to the selected
> property type
> 8/7- change flow shape from start and end point
>  - add mutiple connection points in the nodes
> 15/7  - add zoom event to svg and scroll
> 29/7  - create property list
> 5/8- export json in to BPMN
> 19/8  - redraw element using json array after upload a BPMN file
>
> Thanks
> regards,
> Heshan Jayasinghe
>
>
>
> On Mon, Jun 20, 2016 at 2:32 PM, Isuru Wijesinghe 
> wrote:
>
>> Hi Heshan,
>>
>> Please update the meeting notes. In addition to that can you please
>> share with us the milestone plan as we discussed in the last week.
>>
>> Thanks,
>> Isuru.
>>
>> On Thu, May 26, 2016 at 11:04 PM, Heshan Jayasinghe <
>> shanu...@gmail.com> wrote:
>>
>>> github url - https://github.com/heshanjse/BPMNEditor
>>>
>>> On Thu, May 19, 2016 at 12:52 PM, Heshan Jayasinghe <
>>> shanu...@gmail.com> wrote:
>>>
 Hi Isuru,
 I completed Start Event,End Event,Gateways and Task.Currently
 these component can move in the canvas.As we discussed in our last 
 meeting
 I am working for packaging the current source code,drawing 
 flows,component
 re-sizing,creating property window and adding text areas to Task
 component.After I applying packaging structure i will share my
 github code.Hope I can send it soon.
 Thank you,
 Regards,
 Heshan Jayasinghe

 On Wed, May 18, 2016 at 10:04 AM, Isuru Wijesinghe <
 isur...@wso2.com> wrote:

> Hi Heshan,

[Dev] When ESB add "xformValues" to outgoing http url

2016-07-28 Thread Udara Liyanage

Hi,

I don't set any of the properties to x-www-form-urlencoded in my configs.
However when I set messageType to application/json correct url is seen in
outgoing message from ESB

[2016-07-28 12:04:23,049] DEBUG - wire << "GET* /abc?abc=123*
HTTP/1.1[\r][\n]"
[2016-07-28 12:04:23,049] DEBUG - wire << "Authorization: Token[\r][\n]"
[2016-07-28 12:04:23,049] DEBUG - wire << "Accept: */*[\r][\n]"
[2016-07-28 12:04:23,049] DEBUG - wire << "Content-Type:
application/json[\r][\n]"
[2016-07-28 12:04:23,050] DEBUG - wire << "Host: localhost:[\r][\n]"
[2016-07-28 12:04:23,050] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
[2016-07-28 12:04:23,050] DEBUG - wire << "User-Agent:
Synapse-PT-HttpComponents-NIO[\r][\n]"
[2016-07-28 12:04:23,050] DEBUG - wire << "[\r][\n]"
[2016-07-28 12:04:23,050]  WARN - TargetHandler Connecti


-- Forwarded message --
From: Udara Liyanage 
Date: Thu, Jul 28, 2016 at 12:00 PM
Subject: Re: What is this xformValues
To: Vijitha Ekanayake 


Hi,

Did you mean in transport receiver or in our configs?. we did n't set it in
our configs.

However when I set messageType and Content-Type to application/json it
works as expected

On Thu, Jul 28, 2016 at 11:48 AM, Vijitha Ekanayake 
wrote:

> It seems you are having x-www-form-urlencoded Data to the backend. Check
> whether below to properties has set in the somewhere in the InFlow of the
> message.
>
> scope="axis2" type="STRING"/>
> scope="axis2" type="STRING"/>
>
>
> On Thu, Jul 28, 2016 at 11:26 AM, Udara Liyanage  wrote:
>
>> Hi,
>>
>> What is this GET */xformValues in *ESB outgoing message
>>
>> Request
>>  curl -X POST -H "Authorization: Token" "
>> http://ampdevcmsst-wso2api.amp.endeavourdemo.com:8280/users/; -v
>>
>>
>> http://ws.apache.org/ns/synapse; name="localendpoint">
>>http://localhost:/abc?abc=123; method="get">
>>   
>>  1.0
>>   
>>   
>>  0
>>  0
>>   
>>
>> 
>>
>> [2016-07-28 11:21:30,680] DEBUG - wire >> "POST /users/ HTTP/1.1[\r][\n]"
>> [2016-07-28 11:21:30,681] DEBUG - wire >> "Host:
>> ampdevcmsst-wso2api.amp.endeavourdemo.com:8280[\r][\n]"
>> [2016-07-28 11:21:30,681] DEBUG - wire >> "User-Agent:
>> curl/7.43.0[\r][\n]"
>> [2016-07-28 11:21:30,681] DEBUG - wire >> "Accept: */*[\r][\n]"
>> [2016-07-28 11:21:30,681] DEBUG - wire >> "Authorization: Token[\r][\n]"
>> [2016-07-28 11:21:30,681] DEBUG - wire >> "[\r][\n]"
>> [2016-07-28 11:21:30,740]  INFO - LogMediator To: /users/, MessageID:
>> urn:uuid:380a10da-a751-4f0b-8397-203e7079525b, Direction: request, auth
>> header2 = Token
>> [2016-07-28 11:21:30,748]  INFO - TimeoutHandler This engine will expire
>> all callbacks after : 120 seconds, irrespective of the timeout action,
>> after the specified or optional timeout
>> [2016-07-28 11:21:30,770] DEBUG - wire << "GET */xformValues*
>> HTTP/1.1[\r][\n]"
>> [2016-07-28 11:21:30,770] DEBUG - wire << "Authorization: Token[\r][\n]"
>> [2016-07-28 11:21:30,770] DEBUG - wire << "Accept: */*[\r][\n]"
>> [2016-07-28 11:21:30,770] DEBUG - wire << "Host: localhost:[\r][\n]"
>> [2016-07-28 11:21:30,770] DEBUG - wire << "Connection: Keep-Alive[\r][\n]"
>> [2016-07-28 11:21:30,770] DEBUG - wire << "User-Agent:
>> Synapse-PT-HttpComponents-NIO[\r][\n]"
>> [2016-07-28 11:21:30,770] DEBUG - wire << "[\r][\n]"
>>
>> --
>>
>> Udara Liyanage
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean. enterprise. middleware
>>
>> Blog: http://udaraliyanage.wordpress.com
>>
>
>
>
> --
> Vijitha Ekanayake
> Software Engineer*, *WSO2, Inc.; http://wso2.com/
> Mobile : +94 777 24 73 39 | +94 718 74 44 08
> lean.enterprise.middleware
>



-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

Blog: http://udaraliyanage.wordpress.com



-- 

Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

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

Re: [Dev] [VOTE] Release WSO2 Puppet Modules 2.1.0 RC2

2016-07-28 Thread Isuru Haththotuwa

Verified the following:

   1. License validity with the RAT plugin
   2. provisioned APIM 1.10.0, DAS 3.0.1 with vagrant setup and ran a smoke
   test
   3. Built the following Docker images with puppet provisioning using the
   puppet modules from the tag v2.1.0-rc2, and ran a smoke test
  - ESB 4.9.0
  - CEP 4.0.0
  - MB 3.1.0
  - DSS 3.5.0
  - GREG 5.1.0

*[x] Stable - go ahead and release*

On Tue, Jul 26, 2016 at 2:07 PM, Thanuja Uruththirakodeeswaran <
thanu...@wso2.com> wrote:

> [+1] Stable - Go ahead and release
>
> Verified the following:
>
>1. Distribution
>2. License Headers using RAT plugin
>3. README files
>4. Verified following products with docker images built with puppet
>provisioning for Mesos platform and tested basic functionalities:
>
>
>- WSO2 ES 2.0.0 (Distributed setup)
>- WSO2 AS 5.3.0 (Distributed setup)
>- WSO2 ESB 4.9.0 (Distributed setup)
>- WSO2 MB 3.1.0
>- WSO2 IS 5.1.0
>- WSO2 IS KM 5.1.0
>- WSO2 APIM 1.10.0
>
> 5. Tested above products in Mesos platform with secure vault
> enabled.
> 6. Tested SSO configuration with WSO2 IS 5.1.0 as identity
> provider and WSO2 ESB 4.9.0 and WSO2 AS 5.3.0 as service providers.
>
> Thanks.
>
> On Mon, Jul 25, 2016 at 6:39 PM, Pubudu Gunatilaka 
> wrote:
>
>> Hi Devs,
>>
>> This is the second release candidate (RC2) of WSO2 Puppet Modules 2.1.0
>> release. Please download, verify, and vote. Voting will be open for 72
>> hours or as needed.
>>
>> This release fixes following issues:
>> https://wso2.org/jira/browse/PMODULES-16?filter=13155
>>
>> Source and binary distribution files:
>> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2
>>
>> The tag to be voted upon:
>> https://github.com/wso2/puppet-modules/releases/tag/v2.1.0-rc2
>>
>> Release verification guide:
>> https://docs.wso2.com/display/PM210/Setting+up+the+Development+Environment
>>
>> Refer modules README files for more details.
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (please explain why)
>>
>> Thank you,
>> WSO2 PaaS Team.
>>
>> --
>> *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
>>
>>
>
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks and Regards,

Isuru H.
+94 716 358 048* *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Dockerfiles 1.2.0 Released !

2016-07-28 Thread Abhishek Tiwari

+1

Tested WSO2 Dockerfile with the new test framework for WSO2ESB and WSO2MB
products.
Carbon server starts fine for both the products and no errors were found in
Carbon logs.

Thanks,
Abhishek

On Tue, Jul 26, 2016 at 5:41 PM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> WSO2 PaaS team is pleased to announce the release of *WSO2 Dockerfiles
> 1.2.0*
>
>
> WSO2 Dockerfiles 1.2.0 is the successor of 1.1.0.
>
> *The main changes for this release:*
>
>-
>
>Created a WSO2 base image with the common packages installed.
>-
>
>Validated the profile and platform before building the Docker image.
>-
>
>Added a SVN Docker image.
>-
>
>Changed all ENTRYPOINTs in all Dockerfiles to use the exec form.
>-
>
>Added a script to push the Docker images to a specified registry.
>-
>
>Added the wso2cep init extension scripts.
>-
>
>Included the net-tools package into the wso2base image.
>-
>
>Added debug support for WSO2 servers.
>-
>
>Replaced localMemberPort with dynamic proxy port for the Mesos
>platform.
>-
>
>Added the platform name as a postfix to the Docker image name.
>-
>
>Introduced artifacts folder
>-
>
>Append host node IP to symlink path to create a unique path across a
>cluster in Mesos platform 
>
>
> *Release artifacts:*
>
> https://github.com/wso2/dockerfiles/releases/tag/v1.2.0
>
> *Documentation:*
>
> https://docs.wso2.com/display/DF120/WSO2+Dockerfiles+Documentation
>
>
> *Fixed Issues:*
> https://wso2.org/jira/issues/?filter=13159
>
> *Known Issues:*
>
> https://wso2.org/jira/issues/?filter=13160
>
> --
>
> Regards,
> WSO2 PaaS team
>
>
>
> ___
> 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

38 matches

Mail list logo