Re: [Dev] Maven profile for building distributions for Puppet Forge

[Imesh Gunaratne]

On Fri, Sep 2, 2016 at 10:22 AM, Anuruddha Liyanarachchi <
anurudd...@wso2.com> wrote:

> Hi Imesh,
>
> Yes, I'm on the same page. We had an offline discussion on this before
>> triggering this thread and
>
> our thoughts were the same, that's why we thought of going with puppet
>> module build command. I just wanted to check possibilities of running this
>> on OSX. Will use a debian container do that.
>
>
> I was able to install puppet agent on OSX using [1] and able to run
> puppet build command successfully.
>

​Thanks! It works!
I thought puppet module commands are only available with puppet server.​



> [1] https://docs.puppet.com/puppet/latest/reference/install_osx.html
>
> On Fri, Sep 2, 2016 at 9:53 AM, Imesh Gunaratne  wrote:
>
>> Correction: s/container do that/container to do that/g
>>
>> On Fri, Sep 2, 2016 at 9:49 AM, Imesh Gunaratne  wrote:
>>
>>>
>>>
>>> On Fri, Sep 2, 2016 at 9:30 AM, Chamila De Alwis 
>>> wrote:
>>>

 On Thu, Sep 1, 2016 at 10:52 PM, Imesh Gunaratne 
 wrote:

> ​The problem is with OSX. As I can see there are no official
> installations for OSX:
>

 IMO creating a distribution is a special case and might have to be done
 on special platforms (ex: build servers).

 Another -1 to go with the Assembly plugin is that we would be
 reinventing the wheel by rewriting the puppet build logic. And as Saijth
 mentioned, this would be hard to maintain as Puppet Forge protocols change.

 WDYT?

>>>
>>> ​Yes, I'm on the same page. We had an offline discussion on this before
>>> triggering this thread and
>>> our thoughts were the same, that's why we thought of going with puppet
>>> module build command. I just wanted to check possibilities of running this
>>> on OSX.​ Will use a debian container do that.
>>>
>>> Thanks
>>>


 Regards,
 Chamila de Alwis
 Committer and PMC Member - Apache Stratos
 Senior Software Engineer | WSO2
 Blog: https://medium.com/@chamilad



>>>
>>>
>>> --
>>> *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
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel  : +94 112 145 345
> a nurudd...@wso2.com
>



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

Re: [Dev] [Architecture] OSGI Service to provision users and roles based on the SAML response.

[Ishara Cooray]

Hi All,

I thought of introducing a new Authenticator config to
repository/conf/security/authenticators.xml
And it will use only below properties to do the $Subject.


9

http://wso2.org/claims/role

,
true

PRIMARY



Any objections?

Thanks & Regards,
Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

On Wed, Aug 31, 2016 at 1:43 PM, Ishara Cooray  wrote:

> + Prabath, Johann
>
> Thanks & Regards,
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>
> On Wed, Aug 31, 2016 at 1:27 PM, Pamod Sylvester  wrote:
>
>> Would it make sense to have it under "user-mgt.xml" ?
>>
>> On Wed, Aug 31, 2016 at 1:00 PM, Ishara Cooray  wrote:
>>
>>> Hi,
>>> I am working on the $Subject.
>>>
>>> *Motivation:*
>>> I have a use case where i want to authorize users who are logged into
>>> API publisher/ store but APIM does not have the access to underline user
>>> store.
>>>
>>> *Plan:*
>>> The plan is to write an osgi service that should do the Just In Time
>>> provisioning before the permission check to authorize the user. And it will
>>> get the roles from the SAML response and do the provisioning.
>>>
>>> But we will have to do the same role/permission mapping manually for now.
>>>
>>> If we write a generic service  we can plug it into any wso2 product that
>>> need JIT provision initiated by the Service provider.
>>> However we need to maintain few configurations here.
>>>
>>>1. isServiceProvierInitiatedJITProvisioningEnabled
>>>2. User store to be provisioned
>>>3. Implementation class (extension point)
>>>
>>> What could be the best place to maintain this configuration if the
>>> component is written as a generic component to any wso2 product?
>>>
>>>
>>> Thanks & Regards,
>>> Ishara Cooray
>>> Senior Software Engineer
>>> Mobile : +9477 262 9512
>>> WSO2, Inc. | http://wso2.com/
>>> Lean . Enterprise . Middleware
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Pamod Sylvester *
>>
>> *WSO2 Inc.; http://wso2.com *
>> cell: +94 77 7779495
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DS] Please review and merge this PR

[Ramindu De Silva]

Hi DS team,

Could you please review and merger PR[1].
This was due to the new provider implemented to access DAS tables using
query params in the dashboard.
Since the "registerCallBackForPush" method calls for the "update" method in
the gadget, the gadget's view is not getting created using the schema since
there's no data . So I had to add extra parameter in-order to make the
gadget work.

1. https://github.com/wso2/carbon-dashboards/pull/368

Best Regards,

-- 
*Ramindu De Silva*
Software Engineer
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

email: ramin...@wso2.com 
mob: +94 772339350
mob: +94 719678895
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maven profile for building distributions for Puppet Forge

[Anuruddha Liyanarachchi]

Hi Imesh,

Yes, I'm on the same page. We had an offline discussion on this before
> triggering this thread and

our thoughts were the same, that's why we thought of going with puppet
> module build command. I just wanted to check possibilities of running this
> on OSX. Will use a debian container do that.


I was able to install puppet agent on OSX using [1] and able to run puppet
build command successfully.

[1] https://docs.puppet.com/puppet/latest/reference/install_osx.html

On Fri, Sep 2, 2016 at 9:53 AM, Imesh Gunaratne  wrote:

> Correction: s/container do that/container to do that/g
>
> On Fri, Sep 2, 2016 at 9:49 AM, Imesh Gunaratne  wrote:
>
>>
>>
>> On Fri, Sep 2, 2016 at 9:30 AM, Chamila De Alwis 
>> wrote:
>>
>>>
>>> On Thu, Sep 1, 2016 at 10:52 PM, Imesh Gunaratne  wrote:
>>>
 ​The problem is with OSX. As I can see there are no official
 installations for OSX:

>>>
>>> IMO creating a distribution is a special case and might have to be done
>>> on special platforms (ex: build servers).
>>>
>>> Another -1 to go with the Assembly plugin is that we would be
>>> reinventing the wheel by rewriting the puppet build logic. And as Saijth
>>> mentioned, this would be hard to maintain as Puppet Forge protocols change.
>>>
>>> WDYT?
>>>
>>
>> ​Yes, I'm on the same page. We had an offline discussion on this before
>> triggering this thread and
>> our thoughts were the same, that's why we thought of going with puppet
>> module build command. I just wanted to check possibilities of running this
>> on OSX.​ Will use a debian container do that.
>>
>> Thanks
>>
>>>
>>>
>>> Regards,
>>> Chamila de Alwis
>>> Committer and PMC Member - Apache Stratos
>>> Senior Software Engineer | WSO2
>>> Blog: https://medium.com/@chamilad
>>>
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> *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
>
>


-- 
*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] Hieradata location for puppet modules

[Anuruddha Liyanarachchi]

Hi,

We have decided to use hybrid approach of option2 and option3 as below.

Common hieradata are added to puppet base repository
[1] with .pmtignore file.
Default platform hieradata are added to product specific
puppet repositories [2] with .pmtignore file .
Platform specific hieradata data are added to product platform artifacts
repositories [3][4].



[1] https://github.com/wso2/puppet-base
[2] https://github.com/wso2/puppet-as
[3] https://github.com/wso2/mesos-artifacts-as
[4] https://github.com/wso2/kubernetes-artifacts-as


On Fri, Sep 2, 2016 at 6:19 AM, Isuru Haththotuwa  wrote:

> Hi Anurudhdha,
>
> Are we not keeping default platform hieradata in the puppet module repo
> itself?
>
> On Fri, Aug 26, 2016 at 9:44 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi,
>>
>> There is one catch with option 2; we need to track which Hiera
>> distribution (in platform specific artifacts repo) goes with which Puppet
>> release. This won't be a big issue but just wanted point out.
>>
>> Thanks.
>>
>> On Fri, Aug 26, 2016 at 9:05 AM, Rasanjaya Subasinghe > > wrote:
>>
>>> Hi all,
>>>
>>> The option 2 would be good for do the MC deployment. And other
>>> users  can be used default profile with released puppet forge module.
>>>
>>> Thanks
>>>
>>>
>>> On Thursday, August 25, 2016, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi Devs,

 We are in the process of restructuring and splitting the puppet modules
 per product. As per the initial discussions, we have created separate
 repositories per product puppet module and one common repository for puppet
 base module.

 In order to publish puppet modules to puppet forge, we have decoupled
 hieradata from puppet modules using profiles. Now the puppet modules are
 capable of running without hieradata for the default profile.

 However, it is easier to do deployment using hieradata. The intention
 of this mail is to discuss and finalize hieradata location.

 Appreciate your feedback on selecting an available option.

 Following are the available options:

 *1. Use one repository to keep all product hieradata.*
 Pros:
 - Easy to manage since all the hieradata are in one place.
 - No data duplication

 Cons:
 - Releasing hieradata with a product is not possible.
 - Difficult to track changes.


 *2. Keep hieradata with platform specific artifact repositories.
 (kubernetes, mesos )*
 Pros:
 - Hieradata can be released with a product.

 Cons:
 - Possible data duplication.
 - Hieradata is a part of puppet and it is not related to mesos or
 kubernetes
 - Have to create repositories to store default hieradata.


 *3. Create separate repositories per product to store hieradata. *
 Pros:
 - Product level hieradata separation.
 - Easier to release and track changes.

 Cons:
 - No of repositories are high.
 - User experience will be not good as users will have to clone from
 multiple locations.



 *4. Keep hieradata in the product puppet module repos with
 .pmtignore file. *Pros:
 - Minimum changes required.
 - Can be released with product puppet modules.

 Cons:
 - Most of the puppet repos don't contain hieradata
 - Puppet recommends keeping  hieradata separately from modules.



 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 anurudd...@wso2.com

>>>
>>>
>>> --
>>> -
>>> Rasanjaya Subasinghe
>>> Software Engineer, Dev/Ops, WSO2 Inc.
>>> +94772250358
>>> rasanj...@wso2.com
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
*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] Hieradata location for puppet modules

[Nipuna Chandradasa]

Hi All,

I like 3rd option. Release managing and tracking wise it is very efficient.
Because each product will have a separate repo. Can't we add these
hieradata as a submodule in git so user don't have to clone multiple. Only
need to run git submodule init when needed. Even 2nd option might be bit
less user friendly but 3rd has more pros to developers and will be bit more
user friendly if we can use submodule approach.

Thank you,

On Fri, Sep 2, 2016 at 6:19 AM, Isuru Haththotuwa  wrote:

> Hi Anurudhdha,
>
> Are we not keeping default platform hieradata in the puppet module repo
> itself?
>
> On Fri, Aug 26, 2016 at 9:44 AM, Akila Ravihansa Perera <
> raviha...@wso2.com> wrote:
>
>> Hi,
>>
>> There is one catch with option 2; we need to track which Hiera
>> distribution (in platform specific artifacts repo) goes with which Puppet
>> release. This won't be a big issue but just wanted point out.
>>
>> Thanks.
>>
>> On Fri, Aug 26, 2016 at 9:05 AM, Rasanjaya Subasinghe > > wrote:
>>
>>> Hi all,
>>>
>>> The option 2 would be good for do the MC deployment. And other
>>> users  can be used default profile with released puppet forge module.
>>>
>>> Thanks
>>>
>>>
>>> On Thursday, August 25, 2016, Anuruddha Liyanarachchi <
>>> anurudd...@wso2.com> wrote:
>>>
 Hi Devs,

 We are in the process of restructuring and splitting the puppet modules
 per product. As per the initial discussions, we have created separate
 repositories per product puppet module and one common repository for puppet
 base module.

 In order to publish puppet modules to puppet forge, we have decoupled
 hieradata from puppet modules using profiles. Now the puppet modules are
 capable of running without hieradata for the default profile.

 However, it is easier to do deployment using hieradata. The intention
 of this mail is to discuss and finalize hieradata location.

 Appreciate your feedback on selecting an available option.

 Following are the available options:

 *1. Use one repository to keep all product hieradata.*
 Pros:
 - Easy to manage since all the hieradata are in one place.
 - No data duplication

 Cons:
 - Releasing hieradata with a product is not possible.
 - Difficult to track changes.


 *2. Keep hieradata with platform specific artifact repositories.
 (kubernetes, mesos )*
 Pros:
 - Hieradata can be released with a product.

 Cons:
 - Possible data duplication.
 - Hieradata is a part of puppet and it is not related to mesos or
 kubernetes
 - Have to create repositories to store default hieradata.


 *3. Create separate repositories per product to store hieradata. *
 Pros:
 - Product level hieradata separation.
 - Easier to release and track changes.

 Cons:
 - No of repositories are high.
 - User experience will be not good as users will have to clone from
 multiple locations.



 *4. Keep hieradata in the product puppet module repos with
 .pmtignore file. *Pros:
 - Minimum changes required.
 - Can be released with product puppet modules.

 Cons:
 - Most of the puppet repos don't contain hieradata
 - Puppet recommends keeping  hieradata separately from modules.



 --
 *Thanks and Regards,*
 Anuruddha Lanka Liyanarachchi
 Software Engineer - WSO2
 Mobile : +94 (0) 712762611
 Tel  : +94 112 145 345
 anurudd...@wso2.com

>>>
>>>
>>> --
>>> -
>>> Rasanjaya Subasinghe
>>> Software Engineer, Dev/Ops, WSO2 Inc.
>>> +94772250358
>>> rasanj...@wso2.com
>>>
>>>
>>
>>
>> --
>> Akila Ravihansa Perera
>> WSO2 Inc.;  http://wso2.com/
>>
>> Blog: http://ravihansa3000.blogspot.com
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nipuna Marcus
*Software Engineer*
WSO2 Inc.
http://wso2.com/ - "lean . enterprise . middleware"
Mobile : +94 (0) 713 667906
nipu...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maven profile for building distributions for Puppet Forge

[Imesh Gunaratne]

Correction: s/container do that/container to do that/g

On Fri, Sep 2, 2016 at 9:49 AM, Imesh Gunaratne  wrote:

>
>
> On Fri, Sep 2, 2016 at 9:30 AM, Chamila De Alwis 
> wrote:
>
>>
>> On Thu, Sep 1, 2016 at 10:52 PM, Imesh Gunaratne  wrote:
>>
>>> ​The problem is with OSX. As I can see there are no official
>>> installations for OSX:
>>>
>>
>> IMO creating a distribution is a special case and might have to be done
>> on special platforms (ex: build servers).
>>
>> Another -1 to go with the Assembly plugin is that we would be reinventing
>> the wheel by rewriting the puppet build logic. And as Saijth mentioned,
>> this would be hard to maintain as Puppet Forge protocols change.
>>
>> WDYT?
>>
>
> ​Yes, I'm on the same page. We had an offline discussion on this before
> triggering this thread and
> our thoughts were the same, that's why we thought of going with puppet
> module build command. I just wanted to check possibilities of running this
> on OSX.​ Will use a debian container do that.
>
> Thanks
>
>>
>>
>> Regards,
>> Chamila de Alwis
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer | WSO2
>> Blog: https://medium.com/@chamilad
>>
>>
>>
>
>
> --
> *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
>
>


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

Re: [Dev] Maven profile for building distributions for Puppet Forge

[Imesh Gunaratne]

On Fri, Sep 2, 2016 at 9:30 AM, Chamila De Alwis  wrote:

>
> On Thu, Sep 1, 2016 at 10:52 PM, Imesh Gunaratne  wrote:
>
>> ​The problem is with OSX. As I can see there are no official
>> installations for OSX:
>>
>
> IMO creating a distribution is a special case and might have to be done on
> special platforms (ex: build servers).
>
> Another -1 to go with the Assembly plugin is that we would be reinventing
> the wheel by rewriting the puppet build logic. And as Saijth mentioned,
> this would be hard to maintain as Puppet Forge protocols change.
>
> WDYT?
>

​Yes, I'm on the same page. We had an offline discussion on this before
triggering this thread and
our thoughts were the same, that's why we thought of going with puppet
module build command. I just wanted to check possibilities of running this
on OSX.​ Will use a debian container do that.

Thanks

>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer | WSO2
> Blog: https://medium.com/@chamilad
>
>
>


-- 
*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] [IoTS] Errors when creating the device plugin with carbon-device-mgt-maven-plugin and deploy in IoTS alpha release

[云展智创]

Hi team,

When I used the carbon-device-mgt-maven-plugin to create a new device type and 
deployed in IoTS alpha release, I got the following errors:

It seems that the new maven-archetype-tools created device type need 
carbon.device.mgt.version to be 1.1.1 but alpha release only support 1.1.0?

Could you help me how to solve this problem? Thanks.


－－
Zhanwen Zhou (Jason),
+86 13922218435
zhanwen.z...@smartcloudex.com
Guangzhou Smart Cloudex Technology Co., Ltd.
Business: IOT, API Management

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

Re: [Dev] Maven profile for building distributions for Puppet Forge

[Chamila De Alwis]

On Thu, Sep 1, 2016 at 10:52 PM, Imesh Gunaratne  wrote:

> ​The problem is with OSX. As I can see there are no official installations
> for OSX:
>

IMO creating a distribution is a special case and might have to be done on
special platforms (ex: build servers).

Another -1 to go with the Assembly plugin is that we would be reinventing
the wheel by rewriting the puppet build logic. And as Saijth mentioned,
this would be hard to maintain as Puppet Forge protocols change.

WDYT?

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] Maven profile for building distributions for Puppet Forge

[Imesh Gunaratne]

On Fri, Sep 2, 2016 at 9:00 AM, Chamila De Alwis  wrote:

> Hi Isuru,
>
> Wouldn't it be safe to assume that any host that would run the above
> command would already have Puppet installed? It's not a common use case to
> be used by every potential developer.
>

​The problem is with OSX. As I can see there are no official installations
for OSX:
https://docs.puppet.com/puppetserver/2.5/install_from_packages.html#platforms-with-packages

Thanks

>
>
> Regards,
> Chamila de Alwis
> Committer and PMC Member - Apache Stratos
> Senior Software Engineer | WSO2
> Blog: https://medium.com/@chamilad
>
>
>
> On Thu, Sep 1, 2016 at 9:11 PM, Sajith Kariyawasam 
> wrote:
>
>> Hi Isuru,
>>
>> Yes you are correct, this profile needs puppet to be installed.
>> Generating the distribution just as a tarball would not be enough, since
>> the puppet build command generates the exact distribution compatible with
>> puppet forge. However, the difference seems to be that, 'puppet module
>> build' adds a new file, checksums.json, with checksums of all the files. We
>> could use the assembly plugin and generate the checksums and packaged into
>> the distribution, but I don't think that way is scalable because, if they
>> do a change in the future to include some other files, we will have to
>> change our pom files as well.
>>
>> Thanks,
>> Sajith
>>
>> On Fri, Sep 2, 2016 at 6:09 AM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Sajith,
>>>
>>> Please correct me if I'm wrong, AFAIU This profile requires puppet to be
>>> installed to run the 'puppet module build' command. Can't we use mvn
>>> assembly plugin to generate puppet module distribution?
>>>
>>>
>>> On Thu, Sep 1, 2016 at 6:40 PM, Sajith Kariyawasam 
>>> wrote:
>>>
 Hi Devs,

 For a puppet module to be published into puppet forge [1], puppet
 module need to be built using 'puppet module build' command to create the
 distribution.

 I was looking for a 'maven-puppet' plugin to do the task, but couldn't
 find any suitable plugin, therefore I have introduced a Maven profile [2],
 which uses exec-plugin
 and executes the puppet command, and generate the distribution
 (wso2-wso2bps-3.5.1.tar.gz) if that profile has enabled.

 For eg, *"mvn clean install -P puppet-build "*

 Appreciate your thoughts on this !

 [1] https://forge.puppet.com/
 [2] https://github.com/wso2/puppet-bps/blob/master/pom.xml#L80-L110


 Thanks,
 Sajith


 --
 Sajith Kariyawasam
 *Committer and PMC member, Apache Stratos, *
 *WSO2 Inc.; http://wso2.com *
 *Mobile: 0772269575 <0772269575>*

>>>
>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* *
>>>
>>>
>>>
>>
>>
>> --
>> Sajith Kariyawasam
>> *Associate Tech Lead*
>> *WSO2 Inc.; http://wso2.com *
>> *Committer and PMC member, Apache Stratos *
>> *AMIE (SL)*
>> *Mobile: 0772269575*
>>
>> ___
>> 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
>
>


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

Re: [Dev] Maven profile for building distributions for Puppet Forge

[Chamila De Alwis]

Hi Isuru,

Wouldn't it be safe to assume that any host that would run the above
command would already have Puppet installed? It's not a common use case to
be used by every potential developer.


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Senior Software Engineer | WSO2
Blog: https://medium.com/@chamilad



On Thu, Sep 1, 2016 at 9:11 PM, Sajith Kariyawasam  wrote:

> Hi Isuru,
>
> Yes you are correct, this profile needs puppet to be installed.
> Generating the distribution just as a tarball would not be enough, since
> the puppet build command generates the exact distribution compatible with
> puppet forge. However, the difference seems to be that, 'puppet module
> build' adds a new file, checksums.json, with checksums of all the files. We
> could use the assembly plugin and generate the checksums and packaged into
> the distribution, but I don't think that way is scalable because, if they
> do a change in the future to include some other files, we will have to
> change our pom files as well.
>
> Thanks,
> Sajith
>
> On Fri, Sep 2, 2016 at 6:09 AM, Isuru Haththotuwa  wrote:
>
>> Hi Sajith,
>>
>> Please correct me if I'm wrong, AFAIU This profile requires puppet to be
>> installed to run the 'puppet module build' command. Can't we use mvn
>> assembly plugin to generate puppet module distribution?
>>
>>
>> On Thu, Sep 1, 2016 at 6:40 PM, Sajith Kariyawasam 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> For a puppet module to be published into puppet forge [1], puppet module
>>> need to be built using 'puppet module build' command to create the
>>> distribution.
>>>
>>> I was looking for a 'maven-puppet' plugin to do the task, but couldn't
>>> find any suitable plugin, therefore I have introduced a Maven profile [2],
>>> which uses exec-plugin
>>> and executes the puppet command, and generate the distribution
>>> (wso2-wso2bps-3.5.1.tar.gz) if that profile has enabled.
>>>
>>> For eg, *"mvn clean install -P puppet-build "*
>>>
>>> Appreciate your thoughts on this !
>>>
>>> [1] https://forge.puppet.com/
>>> [2] https://github.com/wso2/puppet-bps/blob/master/pom.xml#L80-L110
>>>
>>>
>>> Thanks,
>>> Sajith
>>>
>>>
>>> --
>>> Sajith Kariyawasam
>>> *Committer and PMC member, Apache Stratos, *
>>> *WSO2 Inc.; http://wso2.com *
>>> *Mobile: 0772269575 <0772269575>*
>>>
>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> Sajith Kariyawasam
> *Associate Tech Lead*
> *WSO2 Inc.; http://wso2.com *
> *Committer and PMC member, Apache Stratos *
> *AMIE (SL)*
> *Mobile: 0772269575*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Maven profile for building distributions for Puppet Forge

[Sajith Kariyawasam]

Hi Isuru,

Yes you are correct, this profile needs puppet to be installed.
Generating the distribution just as a tarball would not be enough, since
the puppet build command generates the exact distribution compatible with
puppet forge. However, the difference seems to be that, 'puppet module
build' adds a new file, checksums.json, with checksums of all the files. We
could use the assembly plugin and generate the checksums and packaged into
the distribution, but I don't think that way is scalable because, if they
do a change in the future to include some other files, we will have to
change our pom files as well.

Thanks,
Sajith

On Fri, Sep 2, 2016 at 6:09 AM, Isuru Haththotuwa  wrote:

> Hi Sajith,
>
> Please correct me if I'm wrong, AFAIU This profile requires puppet to be
> installed to run the 'puppet module build' command. Can't we use mvn
> assembly plugin to generate puppet module distribution?
>
>
> On Thu, Sep 1, 2016 at 6:40 PM, Sajith Kariyawasam 
> wrote:
>
>> Hi Devs,
>>
>> For a puppet module to be published into puppet forge [1], puppet module
>> need to be built using 'puppet module build' command to create the
>> distribution.
>>
>> I was looking for a 'maven-puppet' plugin to do the task, but couldn't
>> find any suitable plugin, therefore I have introduced a Maven profile [2],
>> which uses exec-plugin
>> and executes the puppet command, and generate the distribution
>> (wso2-wso2bps-3.5.1.tar.gz) if that profile has enabled.
>>
>> For eg, *"mvn clean install -P puppet-build "*
>>
>> Appreciate your thoughts on this !
>>
>> [1] https://forge.puppet.com/
>> [2] https://github.com/wso2/puppet-bps/blob/master/pom.xml#L80-L110
>>
>>
>> Thanks,
>> Sajith
>>
>>
>> --
>> Sajith Kariyawasam
>> *Committer and PMC member, Apache Stratos, *
>> *WSO2 Inc.; http://wso2.com *
>> *Mobile: 0772269575 <0772269575>*
>>
>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


-- 
Sajith Kariyawasam
*Associate Tech Lead*
*WSO2 Inc.; http://wso2.com *
*Committer and PMC member, Apache Stratos *
*AMIE (SL)*
*Mobile: 0772269575*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Hieradata location for puppet modules

[Isuru Haththotuwa]

Hi Anurudhdha,

Are we not keeping default platform hieradata in the puppet module repo
itself?

On Fri, Aug 26, 2016 at 9:44 AM, Akila Ravihansa Perera 
wrote:

> Hi,
>
> There is one catch with option 2; we need to track which Hiera
> distribution (in platform specific artifacts repo) goes with which Puppet
> release. This won't be a big issue but just wanted point out.
>
> Thanks.
>
> On Fri, Aug 26, 2016 at 9:05 AM, Rasanjaya Subasinghe 
> wrote:
>
>> Hi all,
>>
>> The option 2 would be good for do the MC deployment. And other users  can
>> be used default profile with released puppet forge module.
>>
>> Thanks
>>
>>
>> On Thursday, August 25, 2016, Anuruddha Liyanarachchi <
>> anurudd...@wso2.com> wrote:
>>
>>> Hi Devs,
>>>
>>> We are in the process of restructuring and splitting the puppet modules
>>> per product. As per the initial discussions, we have created separate
>>> repositories per product puppet module and one common repository for puppet
>>> base module.
>>>
>>> In order to publish puppet modules to puppet forge, we have decoupled
>>> hieradata from puppet modules using profiles. Now the puppet modules are
>>> capable of running without hieradata for the default profile.
>>>
>>> However, it is easier to do deployment using hieradata. The intention of
>>> this mail is to discuss and finalize hieradata location.
>>>
>>> Appreciate your feedback on selecting an available option.
>>>
>>> Following are the available options:
>>>
>>> *1. Use one repository to keep all product hieradata.*
>>> Pros:
>>> - Easy to manage since all the hieradata are in one place.
>>> - No data duplication
>>>
>>> Cons:
>>> - Releasing hieradata with a product is not possible.
>>> - Difficult to track changes.
>>>
>>>
>>> *2. Keep hieradata with platform specific artifact repositories.
>>> (kubernetes, mesos )*
>>> Pros:
>>> - Hieradata can be released with a product.
>>>
>>> Cons:
>>> - Possible data duplication.
>>> - Hieradata is a part of puppet and it is not related to mesos or
>>> kubernetes
>>> - Have to create repositories to store default hieradata.
>>>
>>>
>>> *3. Create separate repositories per product to store hieradata. *
>>> Pros:
>>> - Product level hieradata separation.
>>> - Easier to release and track changes.
>>>
>>> Cons:
>>> - No of repositories are high.
>>> - User experience will be not good as users will have to clone from
>>> multiple locations.
>>>
>>>
>>>
>>> *4. Keep hieradata in the product puppet module repos with
>>> .pmtignore file. *Pros:
>>> - Minimum changes required.
>>> - Can be released with product puppet modules.
>>>
>>> Cons:
>>> - Most of the puppet repos don't contain hieradata
>>> - Puppet recommends keeping  hieradata separately from modules.
>>>
>>>
>>>
>>> --
>>> *Thanks and Regards,*
>>> Anuruddha Lanka Liyanarachchi
>>> Software Engineer - WSO2
>>> Mobile : +94 (0) 712762611
>>> Tel  : +94 112 145 345
>>> anurudd...@wso2.com
>>>
>>
>>
>> --
>> -
>> Rasanjaya Subasinghe
>> Software Engineer, Dev/Ops, WSO2 Inc.
>> +94772250358
>> rasanj...@wso2.com
>>
>>
>
>
> --
> Akila Ravihansa Perera
> WSO2 Inc.;  http://wso2.com/
>
> Blog: http://ravihansa3000.blogspot.com
>



-- 
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] Maven profile for building distributions for Puppet Forge

[Isuru Haththotuwa]

Hi Sajith,

Please correct me if I'm wrong, AFAIU This profile requires puppet to be
installed to run the 'puppet module build' command. Can't we use mvn
assembly plugin to generate puppet module distribution?


On Thu, Sep 1, 2016 at 6:40 PM, Sajith Kariyawasam  wrote:

> Hi Devs,
>
> For a puppet module to be published into puppet forge [1], puppet module
> need to be built using 'puppet module build' command to create the
> distribution.
>
> I was looking for a 'maven-puppet' plugin to do the task, but couldn't
> find any suitable plugin, therefore I have introduced a Maven profile [2],
> which uses exec-plugin
> and executes the puppet command, and generate the distribution
> (wso2-wso2bps-3.5.1.tar.gz) if that profile has enabled.
>
> For eg, *"mvn clean install -P puppet-build "*
>
> Appreciate your thoughts on this !
>
> [1] https://forge.puppet.com/
> [2] https://github.com/wso2/puppet-bps/blob/master/pom.xml#L80-L110
>
>
> Thanks,
> Sajith
>
>
> --
> Sajith Kariyawasam
> *Committer and PMC member, Apache Stratos, *
> *WSO2 Inc.; http://wso2.com *
> *Mobile: 0772269575 <0772269575>*
>



-- 
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] IS 5.1.0 Resend Account Confirmation code

[Damith Wickramasinghe]

Hi Isura,

Thanks for the clarifications.

Regards,
Damith

On Thu, Sep 1, 2016 at 7:25 PM, Isura Karunaratne  wrote:

> Hi Damitha,
>
> Yes. Existing API can be used only when "NoticiationSendingInternallyManger
> = false". For 5.3.0 m4, we changed the API and now, it is not required the
> code as a parameter. [1]
>
> [1] https://github.com/wso2-extensions/identity-governance/blob/master/
> components/org.wso2.carbon.identity.user.endpoint/src/
> main/java/org/wso2/carbon/identity/user/endpoint/impl/
> ResendCodeApiServiceImpl.java
>
> Thanks
> Isura.
>
>
> *Isura Dilhara Karunaratne*
> Senior Software Engineer | WSO2
> Email: is...@wso2.com
> Mob : +94 772 254 810
> Blog : http://isurad.blogspot.com/
>
>
>
>
> On Thu, Sep 1, 2016 at 6:04 AM, Damith Wickramasinghe 
> wrote:
>
>>
>> Hi Devs,
>>
>> To resend the account confirmation code by admin via email as per[1] we
>> can use reSendSignUpConfirmationCode. But in order it to work we need to
>> send the code as well. But if a user did not received an email then he will
>> not have this code. Ideally IMO this should be invoked with out a code.
>>
>> Any idea on how this API can be used to invoke to achieve above.
>>
>> [1]https://docs.wso2.com/display/IS510/User+Information+
>> Recovery+Service#UserInformationRecoveryService-
>> resendSignUpConfiramtionCode
>>
>> Thanks,
>> Damith
>> --
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> 
>> lean.enterprise.middleware
>>
>> mobile: *+94728671315 <%2B94728671315>*
>>
>>
>


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

lean.enterprise.middleware

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

Re: [Dev] Couple of WARN logs are printed in console when logging to latest EMM pack

[Rasika Perera]

Hi Sajith,

The warn log is printed when a 404 error occurs for a static file. By
> looking at the attached logs, seems that 'Roboto-*' fonts are missing and
> they are referred in a CSS file in the 'uuf.unit.lib.form-validation'
> unit. Remove that reference form the CSS file to resolve this.

That's the issue. "uuf.unit.lib.form-validation" unit does not have any
references for such 'Roboto-*' fonts. I did a grep for "'Roboto-*' and it
is only mentioned in a css in "uuf.unit.theme" unit.

Thanks,
Rasika

On Thu, Sep 1, 2016 at 11:13 PM, SajithAR Ariyarathna 
wrote:

> Hi Rasika,
>
> The warn log is printed when a 404 error occurs for a static file. By
> looking at the attached logs, seems that 'Roboto-*' fonts are missing and
> they are referred in a CSS file in the 'uuf.unit.lib.form-validation'
> unit. Remove that reference form the CSS file to resolve this.
>
> Thanks.
>
> On Thu, Sep 1, 2016 at 10:15 PM, Rasika Perera  wrote:
>
>> [+SajithAR]
>>
>> Hi Harshan,
>>
>> I can see the following WARN logs related to UI components when logging
>>> to the latest EMM pack (noticed after merging UUF work). Did anyone forgot
>>> to commit some files related to UI?
>>
>> I have also noticed this. After some analysis it is found that
>> "uuf.unit.lib.form-validation" unit does import none-of-above web fonts.
>> Only "uuf.unit.theme" unit is adding a css which has relative paths to
>> above web-font files.
>>
>> However, WARN logs got faded away with adding "combine=false" into the
>> "uuf.unit.lib.form-validation"'s css file import. This seems like a bug
>> for me.
>>
>> @Sajith
>> Would you shed some light on resolving this issue.
>>
>> Thanks,
>> Rasika
>>
>>>
>>> On Mon, Aug 29, 2016 at 4:57 PM, Harshan Liyanage 
>>> wrote:
>>>
 +1 @dev


 Harshan Liyanage
 Senior Software Engineer
 Mobile: *+94765672894*
 Email: hars...@wso2.com
 Blog : http://harshanliyanage.blogspot.com/
 *WSO2, Inc. :** wso2.com *
 lean.enterprise.middleware.

 On Mon, Aug 29, 2016 at 4:51 PM, Harshan Liyanage 
 wrote:

> Hi,
>
> I can see the following WARN logs related to UI components when
> logging to the latest EMM pack (noticed after merging UUF work). Did 
> anyone
> forgot to commit some files related to UI?
>
> [2016-08-29 16:36:16,991]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Light.woff2' does not exists
> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
> [2016-08-29 16:36:17,000]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Thin.woff2' does not exists
> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
> [2016-08-29 16:36:17,001]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Regular.woff2' does not
> exists in UI Component 'uuf.unit.lib.form-validation' or its parents [].
> [2016-08-29 16:36:17,190]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Light.woff' does not exists
> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
> [2016-08-29 16:36:17,218]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Regular.woff' does not
> exists in UI Component 'uuf.unit.lib.form-validation' or its parents [].
> [2016-08-29 16:36:17,224]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Light.ttf' does not exists
> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
> [2016-08-29 16:36:17,223]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Thin.woff' does not exists
> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
> [2016-08-29 16:36:17,252]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Regular.ttf' does not exists
> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
> [2016-08-29 16:36:17,258]  WARN {static-file-router} -  Requested
> resource 'public/css/fonts/Roboto/Roboto-Thin.ttf' does not exists in
> UI Component 'uuf.unit.lib.form-validation' or its parents [].
>
> Thanks,
>
> Harshan Liyanage
> Senior Software Engineer
> Mobile: *+94765672894*
> Email: hars...@wso2.com
> Blog : http://harshanliyanage.blogspot.com/
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>


>>>
>>>
>>> --
>>> With Regards,
>>>
>>> *Rasika Perera*
>>> Software Engineer
>>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>>
>>> [image: wso2-signature-general.png] 
>>>
>>> WSO2 Inc. www.wso2.com
>>> lean.enterprise.middleware
>>>
>>
>>
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software 

[Dev] [Release][BPS] WSO2 Business Process Server 3.6.0 Released

[Milinda Perera]

WSO2 Business Process Server (WSO2 BPS) 3.6.0 Released

WSO2 Business Process Server team is pleased to announce the release of
WSO2 Business Process Server 3.6.0.
Release NoteAugust 2016

WSO2 Business Process Server (BPS) is an easy-to-use Open Source Business
Process Server that executes business processes written following BPMN 2.0
 or WS-BPEL and WS-Humantask standards.

BPMN 2.0 supports business process management for both technical users and
business users by providing a notation that is intuitive to business users,
yet able to represent complex semantics. With BPMN 2.0, you can model and
execute workflows to accomplish your process automation tasks within your
SOA.

WS-BPEL is the defacto standard for composing multiple synchronous and
asynchronous web services into collaborative and transactional process
flows which increase the flexibility and agility of your Service Oriented
Architecture.

WS-Humantask allows people activities to be integrated with business
processes.

WSO2 BPS is powered by Activiti  BPMN Engine and Apache
ODE BPEL  engine and is available under Apache
Software License v2.0 .
WSO2 BPS provides a complete Web based graphical console to deploy, manage
and monitor business process and process instances.

WSO2 BPS is an open source product available under the Apache Software
License (v2.0) . This
includes all of the extra integration and management functionality as well.

For more information about WSO2 BPS and to download the product please
visit: http://wso2.com/products/business-process-server/
Key Features

   -

   Deploying Business Processes written in compliance with a frequently
   used subset of BPMN 2.0 standard.
   -

   Deploying Business Processes written in compliance with WS-BPEL 2.0
   Standard and BPEL4WS 1.1 standard.
   -

   Support for Human Interactions in BPEL Processes with WS-Humantask and
   BPEL4People.
   -

   Managing BPEL / BPMN packages, processes and process instances.
   -

   BPEL Extensions and XPath extensions support
   -

   Instance recovery(Only supports 'Invoke' activity) support through
   management console
   -

   WS-Security support for business processes.
   -

   Support for invoking secured(Using WS-Security) partner services.
   -

   Support for Humantask Coordination
   -

   BPEL / BPMN Package hot update which facilitate Versioning
   -

   Humantask versioning support
   -

   E4X based data manipulation support for BPEL assignments
   -

   Configure external database system as the BPEL / BPMN engine's
   persistence storage
   -

   Transport management.
   -

   Internationalized web based management console.
   -

   System monitoring.
   -

   Try-it for business processes.
   -

   SOAP Message Tracing.
   -

   Endpoint configuration mechanism based on WSO2 Unified Endpoints.
   -

   Customizable server - You can customize the BPS to fit into your exact
   requirements, by removing certain features or by adding new optional
   features.
   -

   Clustering support.
   -

   Process monitoring with WSO2 Data Analytics Server.
   -

   JMX monitoring support
   -

   Comprehensive and customizable web application (Humantask Explorer ) for
   managing human tasks.
   -

   Comprehensive and customizable web application (BPMN Explorer ) for
   managing BPMN Processes/Instances and user tasks
   -

   Humantask UI form Generation support
   -

   Reporting dashboards for BPMN
   -

   Data manipulation support for BPMN with JSON and XML
   -

   WS-Humantask Editor  and Drag-n and Drop visual Editors for BPMN and
   BPEL with Developer Studio
   -

   BPMN Process Instance Search/Monitoring capability
   -

   BPMN Task user substitution feature
   -

   Enhanced REST service invoker extension for BPMN
   -

   SOAP service invoker extension for BPMN
   -

   Process cleanup tool to remove RETIRED versions of bpel processes

New Features In This Release

   -

   BPMN rest api improvements
   -

   Data manipulation support for BPMN with JSON and XML
   -

   WS-Humantask Editor with Developer Studio
   -

   BPMN Process Instance Search/Monitoring capability
   -

   BPMN Task user substitution feature
   -

   Enhanced REST service invoker extension for BPMN
   -

   SOAP service invoker extension for BPMN
   -

   Many other bug fixes

Issues Fixed for this release

   -

   BPS Runtime
   
   -

   BPS Tooling 

XML & WS-* Standards Support

   -

   BPMN 2.0
   -

   BPEL4WS 1.1
   -

   WS-BPEL 2.0
   -

   WS-Humantask 1.1
   -

   BPEL4People 1.1
   -

   SOAP 1.1/1.2
   -

   WSDL 1.1
   -

   WSDL 2.0
   -

   MTOM, XOP & SOAP with Attachments
   -

   WS-Addressing
   -

   WS-Security 1.0/1.1
   -

   WS-Trust
   -

   WS-SecurityPolicy
   -

   

Re: [Dev] Couple of WARN logs are printed in console when logging to latest EMM pack

[SajithAR Ariyarathna]

Hi Rasika,

The warn log is printed when a 404 error occurs for a static file. By
looking at the attached logs, seems that 'Roboto-*' fonts are missing and
they are referred in a CSS file in the 'uuf.unit.lib.form-validation' unit.
Remove that reference form the CSS file to resolve this.

Thanks.

On Thu, Sep 1, 2016 at 10:15 PM, Rasika Perera  wrote:

> [+SajithAR]
>
> Hi Harshan,
>
> I can see the following WARN logs related to UI components when logging to
>> the latest EMM pack (noticed after merging UUF work). Did anyone forgot to
>> commit some files related to UI?
>
> I have also noticed this. After some analysis it is found that
> "uuf.unit.lib.form-validation" unit does import none-of-above web fonts.
> Only "uuf.unit.theme" unit is adding a css which has relative paths to
> above web-font files.
>
> However, WARN logs got faded away with adding "combine=false" into the
> "uuf.unit.lib.form-validation"'s css file import. This seems like a bug
> for me.
>
> @Sajith
> Would you shed some light on resolving this issue.
>
> Thanks,
> Rasika
>
>>
>> On Mon, Aug 29, 2016 at 4:57 PM, Harshan Liyanage 
>> wrote:
>>
>>> +1 @dev
>>>
>>>
>>> Harshan Liyanage
>>> Senior Software Engineer
>>> Mobile: *+94765672894*
>>> Email: hars...@wso2.com
>>> Blog : http://harshanliyanage.blogspot.com/
>>> *WSO2, Inc. :** wso2.com *
>>> lean.enterprise.middleware.
>>>
>>> On Mon, Aug 29, 2016 at 4:51 PM, Harshan Liyanage 
>>> wrote:
>>>
 Hi,

 I can see the following WARN logs related to UI components when logging
 to the latest EMM pack (noticed after merging UUF work). Did anyone forgot
 to commit some files related to UI?

 [2016-08-29 16:36:16,991]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Light.woff2' does not exists
 in UI Component 'uuf.unit.lib.form-validation' or its parents [].
 [2016-08-29 16:36:17,000]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Thin.woff2' does not exists
 in UI Component 'uuf.unit.lib.form-validation' or its parents [].
 [2016-08-29 16:36:17,001]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Regular.woff2' does not
 exists in UI Component 'uuf.unit.lib.form-validation' or its parents [].
 [2016-08-29 16:36:17,190]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Light.woff' does not exists
 in UI Component 'uuf.unit.lib.form-validation' or its parents [].
 [2016-08-29 16:36:17,218]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Regular.woff' does not exists
 in UI Component 'uuf.unit.lib.form-validation' or its parents [].
 [2016-08-29 16:36:17,224]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Light.ttf' does not exists in
 UI Component 'uuf.unit.lib.form-validation' or its parents [].
 [2016-08-29 16:36:17,223]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Thin.woff' does not exists in
 UI Component 'uuf.unit.lib.form-validation' or its parents [].
 [2016-08-29 16:36:17,252]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Regular.ttf' does not exists
 in UI Component 'uuf.unit.lib.form-validation' or its parents [].
 [2016-08-29 16:36:17,258]  WARN {static-file-router} -  Requested
 resource 'public/css/fonts/Roboto/Roboto-Thin.ttf' does not exists in
 UI Component 'uuf.unit.lib.form-validation' or its parents [].

 Thanks,

 Harshan Liyanage
 Senior Software Engineer
 Mobile: *+94765672894*
 Email: hars...@wso2.com
 Blog : http://harshanliyanage.blogspot.com/
 *WSO2, Inc. :** wso2.com *
 lean.enterprise.middleware.

>>>
>>>
>>
>>
>> --
>> With Regards,
>>
>> *Rasika Perera*
>> Software Engineer
>> LinkedIn: http://lk.linkedin.com/in/rasika90
>>
>> [image: wso2-signature-general.png] 
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> [image: wso2-signature-general.png] 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
Sajith Janaprasad Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/

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

Re: [Dev] Couple of WARN logs are printed in console when logging to latest EMM pack

[Rasika Perera]

[+SajithAR]

Hi Harshan,

I can see the following WARN logs related to UI components when logging to
> the latest EMM pack (noticed after merging UUF work). Did anyone forgot to
> commit some files related to UI?

I have also noticed this. After some analysis it is found that
"uuf.unit.lib.form-validation" unit does import none-of-above web fonts.
Only "uuf.unit.theme" unit is adding a css which has relative paths to
above web-font files.

However, WARN logs got faded away with adding "combine=false" into the
"uuf.unit.lib.form-validation"'s css file import. This seems like a bug for
me.

@Sajith
Would you shed some light on resolving this issue.

Thanks,
Rasika

>
> On Mon, Aug 29, 2016 at 4:57 PM, Harshan Liyanage 
> wrote:
>
>> +1 @dev
>>
>>
>> Harshan Liyanage
>> Senior Software Engineer
>> Mobile: *+94765672894*
>> Email: hars...@wso2.com
>> Blog : http://harshanliyanage.blogspot.com/
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>> On Mon, Aug 29, 2016 at 4:51 PM, Harshan Liyanage 
>> wrote:
>>
>>> Hi,
>>>
>>> I can see the following WARN logs related to UI components when logging
>>> to the latest EMM pack (noticed after merging UUF work). Did anyone forgot
>>> to commit some files related to UI?
>>>
>>> [2016-08-29 16:36:16,991]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Light.woff2' does not exists
>>> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>> [2016-08-29 16:36:17,000]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Thin.woff2' does not exists in
>>> UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>> [2016-08-29 16:36:17,001]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Regular.woff2' does not exists
>>> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>> [2016-08-29 16:36:17,190]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Light.woff' does not exists in
>>> UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>> [2016-08-29 16:36:17,218]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Regular.woff' does not exists
>>> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>> [2016-08-29 16:36:17,224]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Light.ttf' does not exists in
>>> UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>> [2016-08-29 16:36:17,223]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Thin.woff' does not exists in
>>> UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>> [2016-08-29 16:36:17,252]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Regular.ttf' does not exists
>>> in UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>> [2016-08-29 16:36:17,258]  WARN {static-file-router} -  Requested
>>> resource 'public/css/fonts/Roboto/Roboto-Thin.ttf' does not exists in
>>> UI Component 'uuf.unit.lib.form-validation' or its parents [].
>>>
>>> Thanks,
>>>
>>> Harshan Liyanage
>>> Senior Software Engineer
>>> Mobile: *+94765672894*
>>> Email: hars...@wso2.com
>>> Blog : http://harshanliyanage.blogspot.com/
>>> *WSO2, Inc. :** wso2.com *
>>> lean.enterprise.middleware.
>>>
>>
>>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> [image: wso2-signature-general.png] 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>



-- 
With Regards,

*Rasika Perera*
Software Engineer
LinkedIn: http://lk.linkedin.com/in/rasika90

[image: wso2-signature-general.png] 

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

Re: [Dev] IS 5.1.0 Resend Account Confirmation code

[Isura Karunaratne]

Hi Damitha,

Yes. Existing API can be used only when "NoticiationSendingInternallyManger
= false". For 5.3.0 m4, we changed the API and now, it is not required the
code as a parameter. [1]

[1]
https://github.com/wso2-extensions/identity-governance/blob/master/components/org.wso2.carbon.identity.user.endpoint/src/main/java/org/wso2/carbon/identity/user/endpoint/impl/ResendCodeApiServiceImpl.java

Thanks
Isura.


*Isura Dilhara Karunaratne*
Senior Software Engineer | WSO2
Email: is...@wso2.com
Mob : +94 772 254 810
Blog : http://isurad.blogspot.com/




On Thu, Sep 1, 2016 at 6:04 AM, Damith Wickramasinghe 
wrote:

>
> Hi Devs,
>
> To resend the account confirmation code by admin via email as per[1] we
> can use reSendSignUpConfirmationCode. But in order it to work we need to
> send the code as well. But if a user did not received an email then he will
> not have this code. Ideally IMO this should be invoked with out a code.
>
> Any idea on how this API can be used to invoke to achieve above.
>
> [1]https://docs.wso2.com/display/IS510/User+Information+Recovery+Service#
> UserInformationRecoveryService-resendSignUpConfiramtionCode
>
> Thanks,
> Damith
> --
> Software Engineer
> WSO2 Inc.; http://wso2.com
> 
> lean.enterprise.middleware
>
> mobile: *+94728671315 <%2B94728671315>*
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Clarification regarding primary keys of LOGANALYZER table

[Inosh Goonewardena]

+1 for removing primary keys which prevents from storing all the log
entries.

Btw, you can avoid deadlocks from happening in this kind of scenario by
setting transaction isolation level to Read Uncommitted in datasource
configuration (dirty reads may occur due to this but it won't be an issue
in this use case).


On Thu, Sep 1, 2016 at 5:53 PM, Ruwan Abeykoon  wrote:

> Hi Tishan,
> Thanks for the findings.
>
> +1 for option 2 :Remove primary keys and just keep indexes.
> I guess there will be few issues if we ever want to do log-tail
> submission. But we can find a solution for that too later, as log-tail is
> not going to be used as of now.
>
> Cheers,
> Ruwan
>
>
>
> On Thu, Sep 1, 2016 at 5:48 PM, Tishan Dahanayakage 
> wrote:
>
>> Hi all,
>>
>> While doing performance tests on log analyzer I came across a DB deadlock
>> issue when bursting event.
>> Root cause for the issue is as follows.
>> - I have different set of log entries(~10) which I loop around
>> continously and publish with current timestamp.
>> - Currently _class, _content, _level, _eventTimeStamp are set as primary
>> keys of LOGANALYZER table
>> - So when sending above log events in high frequency events with same
>> timestamp hence same primary key will be sent to DAS
>> - When DAS try to persist this in batches deadlock happens.
>>
>> I got around this by modifying log content with loop variable for the
>> moment which will make sure that events with same primary key will not be
>> sent to DAS. But I have following question for clarification.
>>
>> 1. Making above attributes as primary keys we assume that a log with same
>> class, content and level cannot happen within the same millisecond. Will
>> this be always true even for a multi GW high throughput setup? Because if
>> it is true we will not only get this exception time to time but also we
>> will be replacing actually occurred log entries.
>>
>> 2. Is there any special reason to define these primary keys? Else shall
>> we remove primary keys and just keep indexes.
>>
>> Thanks
>> /Tishan
>>
>> --
>> Tishan Dahanayakage
>> Senior Software Engineer
>> WSO2, Inc.
>> Mobile:+94 716481328
>>
>> Disclaimer: This communication may contain privileged or other
>> confidential information and is intended exclusively for the addressee/s.
>> If you are not the intended recipient/s, or believe that you may have
>> received this communication in error, please reply to the sender indicating
>> that fact and delete the copy you received and in addition, you should not
>> print, copy, re-transmit, disseminate, or otherwise use the information
>> contained in this communication. Internet communications cannot be
>> guaranteed to be timely, secure, error or virus-free. The sender does not
>> accept liability for any errors or omissions.
>>
>
>
>
> --
>
> *Ruwan Abeykoon*
> *Associate Director/Architect**,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Maven profile for building distributions for Puppet Forge

[Sajith Kariyawasam]

Hi Devs,

For a puppet module to be published into puppet forge [1], puppet module
need to be built using 'puppet module build' command to create the
distribution.

I was looking for a 'maven-puppet' plugin to do the task, but couldn't find
any suitable plugin, therefore I have introduced a Maven profile [2], which
uses exec-plugin
and executes the puppet command, and generate the distribution
(wso2-wso2bps-3.5.1.tar.gz) if that profile has enabled.

For eg, *"mvn clean install -P puppet-build "*

Appreciate your thoughts on this !

[1] https://forge.puppet.com/
[2] https://github.com/wso2/puppet-bps/blob/master/pom.xml#L80-L110


Thanks,
Sajith


-- 
Sajith Kariyawasam
*Committer and PMC member, Apache Stratos, *
*WSO2 Inc.; http://wso2.com *
*Mobile: 0772269575*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] ESB error when login to admin console

[Danushka Fernando]

Saying this just looking at the error. This could be probably due to ur
nginx config request comes to esb has two '/'s which causes to not to match
the path for  csrf whitelisted paths in carbon.xml.
You can check this by directly accessing ESB I guess.
If this is the case you can either add your list to carbon.xml or you can
remove it from nginx config.

Thanks & Regards
Danushka Fernando
Senior Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729

On Thu, Sep 1, 2016 at 3:59 PM, Jithendra Sirimanne 
wrote:

> Hi,
>
> I have configured fresh ESB pack with Nginx reverse proxy. Now when I try
> to log into ESB console I get a "Error 403 - Forbidden". In the carbon log
> it shows
>
> TID: [-1234] [] [2016-09-01 15:46:17,417]  WARN 
> {org.owasp.csrfguard.log.JavaLogger}
> -  potential cross-site request forgery (CSRF) attack thwarted
> (user:, ip:127.0.0.1, method:POST, 
> uri:/carbon//admin/js/csrfPrevention.js,
> error:required token is missing from the request) {org.owasp.csrfguard.log.
> JavaLogger}
> TID: [-1234] [] [2016-09-01 15:46:21,821]  WARN 
> {org.owasp.csrfguard.log.JavaLogger}
> -  potential cross-site request forgery (CSRF) attack thwarted
> (user:, ip:127.0.0.1, method:POST, 
> uri:/carbon//admin/login_action.jsp,
> error:required token is missing from the request) {org.owasp.csrfguard.log.
> JavaLogger}
>
> Any ideas to fix this?
>
> Best Regards
> Jithendra
>
> --
> Jithendra Sirimanne
> *Systems Engineer*
> Mobile: +94 (0) 716 374696 <+94+(0)+716+374696>
> Tel  : +94 112 145 345
> Email  : jithen...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Roshan Wijesena]

Hi All,

Thanks for testing and verifying WSO2 APIM tooling 2.0.0 RC3. We are
closing the vote now. We are proceeding with  WSO2 APIM  tooling 2.0.0
release.

Thanks,
WSO2 APIM Team.

On Thu, Sep 1, 2016 at 5:45 PM, Roshan Wijesena  wrote:

> Hi Isabelle,
>
> On Thu, Sep 1, 2016 at 5:40 PM, Isabelle Mauny  wrote:
>
>> Needs to be tested against API Cloud. Is that done ?
>>
>
> Yes, we have tested this with wso2 API cloud.
>
> Regards
> Roshan.
>
>
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>



-- 
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] Clarification regarding primary keys of LOGANALYZER table

[Ruwan Abeykoon]

Hi Tishan,
Thanks for the findings.

+1 for option 2 :Remove primary keys and just keep indexes.
I guess there will be few issues if we ever want to do log-tail submission.
But we can find a solution for that too later, as log-tail is not going to
be used as of now.

Cheers,
Ruwan



On Thu, Sep 1, 2016 at 5:48 PM, Tishan Dahanayakage  wrote:

> Hi all,
>
> While doing performance tests on log analyzer I came across a DB deadlock
> issue when bursting event.
> Root cause for the issue is as follows.
> - I have different set of log entries(~10) which I loop around continously
> and publish with current timestamp.
> - Currently _class, _content, _level, _eventTimeStamp are set as primary
> keys of LOGANALYZER table
> - So when sending above log events in high frequency events with same
> timestamp hence same primary key will be sent to DAS
> - When DAS try to persist this in batches deadlock happens.
>
> I got around this by modifying log content with loop variable for the
> moment which will make sure that events with same primary key will not be
> sent to DAS. But I have following question for clarification.
>
> 1. Making above attributes as primary keys we assume that a log with same
> class, content and level cannot happen within the same millisecond. Will
> this be always true even for a multi GW high throughput setup? Because if
> it is true we will not only get this exception time to time but also we
> will be replacing actually occurred log entries.
>
> 2. Is there any special reason to define these primary keys? Else shall we
> remove primary keys and just keep indexes.
>
> Thanks
> /Tishan
>
> --
> Tishan Dahanayakage
> Senior Software Engineer
> WSO2, Inc.
> Mobile:+94 716481328
>
> Disclaimer: This communication may contain privileged or other
> confidential information and is intended exclusively for the addressee/s.
> If you are not the intended recipient/s, or believe that you may have
> received this communication in error, please reply to the sender indicating
> that fact and delete the copy you received and in addition, you should not
> print, copy, re-transmit, disseminate, or otherwise use the information
> contained in this communication. Internet communications cannot be
> guaranteed to be timely, secure, error or virus-free. The sender does not
> accept liability for any errors or omissions.
>



-- 

*Ruwan Abeykoon*
*Associate Director/Architect**,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Roshan Wijesena]

Hi Isabelle,

On Thu, Sep 1, 2016 at 5:40 PM, Isabelle Mauny  wrote:

> Needs to be tested against API Cloud. Is that done ?
>

Yes, we have tested this with wso2 API cloud.

Regards
Roshan.


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

[Dev] Clarification regarding primary keys of LOGANALYZER table

[Tishan Dahanayakage]

Hi all,

While doing performance tests on log analyzer I came across a DB deadlock
issue when bursting event.
Root cause for the issue is as follows.
- I have different set of log entries(~10) which I loop around continously
and publish with current timestamp.
- Currently _class, _content, _level, _eventTimeStamp are set as primary
keys of LOGANALYZER table
- So when sending above log events in high frequency events with same
timestamp hence same primary key will be sent to DAS
- When DAS try to persist this in batches deadlock happens.

I got around this by modifying log content with loop variable for the
moment which will make sure that events with same primary key will not be
sent to DAS. But I have following question for clarification.

1. Making above attributes as primary keys we assume that a log with same
class, content and level cannot happen within the same millisecond. Will
this be always true even for a multi GW high throughput setup? Because if
it is true we will not only get this exception time to time but also we
will be replacing actually occurred log entries.

2. Is there any special reason to define these primary keys? Else shall we
remove primary keys and just keep indexes.

Thanks
/Tishan

-- 
Tishan Dahanayakage
Senior Software Engineer
WSO2, Inc.
Mobile:+94 716481328

Disclaimer: This communication may contain privileged or other confidential
information and is intended exclusively for the addressee/s. If you are not
the intended recipient/s, or believe that you may have received this
communication in error, please reply to the sender indicating that fact and
delete the copy you received and in addition, you should not print, copy,
re-transmit, disseminate, or otherwise use the information contained in
this communication. Internet communications cannot be guaranteed to be
timely, secure, error or virus-free. The sender does not accept liability
for any errors or omissions.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Isabelle Mauny]

Needs to be tested against API Cloud. Is that done ?
__

Isabelle Mauny
VP, Product Strategy; WSO2, Inc.;  http://wso2.com/
email: isabe...@wso2.com - mobile (Spain) : +34 616050684 - mobile (Sri Lanka) 
+94 (0)774777663
Landline:  +1 (650) 745 4499  (USA)  or +94 (11) 214 534 (SL) Extension : 7302

> On Sep 1, 2016, at 1:57 PM, Malintha Amarasinghe  wrote:
> 
> Tested basic functionality in Ubuntu 15.10
> 
> [+]  Stable   - go ahead and release.
> 
> On Thu, Sep 1, 2016 at 4:56 PM, Harsha Kumara  > wrote:
> Tested basic functionality on Ubuntu 14.04.5 LTS. 
> 
> [+]  Stable  -  go ahead and release.
> 
> On Thu, Sep 1, 2016 at 3:46 PM, Sam Sivayogam  > wrote:
> Tested in Mac. Was able add custom sequences to APIM through dev studio.
> [+]  Stable  -  go ahead and release.
> 
> On Tue, Aug 30, 2016 at 5:28 PM, Roshan Wijesena  > wrote:
> Hi All,
> 
> This is the 3rd Release Candidate of WSO2 API Manager mediation policy 
> tooling 2.0.0.
> 
> Please download, test the product and vote. The vote will be open for 72 
> hours or as needed.
> 
> Source and distribution
> 
> Tooling  : 
> https://github.com/wso2/devstudio-tooling-apim/releases/tag/Released-release-2.0.3-RC3-2016-08-30-105251
>  
> 
> 
> 
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
> 
> Thanks,
> WSO2 APIM team.
> 
> -- 
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: +94719154640 
> Email: ros...@wso2.com 
>  <>
> WSO2, Inc. : wso2.com 
> lean.enterprise.middleware.
> 
> 
> 
> -- 
> Sam Sivayogam
> 
> Senior 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 
> 
> 
> 
> 
> 
> -- 
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 
> Blog:harshcreationz.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 mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] IS 5.1.0 Resend Account Confirmation code

[Damith Wickramasinghe]

Hi Devs,

To resend the account confirmation code by admin via email as per[1] we can
use reSendSignUpConfirmationCode. But in order it to work we need to send
the code as well. But if a user did not received an email then he will not
have this code. Ideally IMO this should be invoked with out a code.

Any idea on how this API can be used to invoke to achieve above.

[1]
https://docs.wso2.com/display/IS510/User+Information+Recovery+Service#UserInformationRecoveryService-resendSignUpConfiramtionCode

Thanks,
Damith
-- 
Software Engineer
WSO2 Inc.; http://wso2.com

lean.enterprise.middleware

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

Re: [Dev] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Malintha Amarasinghe]

Tested basic functionality in Ubuntu 15.10

[+]  Stable   - go ahead and release.

On Thu, Sep 1, 2016 at 4:56 PM, Harsha Kumara  wrote:

> Tested basic functionality on Ubuntu 14.04.5 LTS.
>
> [+]  Stable  -  go ahead and release.
>
> On Thu, Sep 1, 2016 at 3:46 PM, Sam Sivayogam  wrote:
>
>> Tested in Mac. Was able add custom sequences to APIM through dev studio.
>> [+]  Stable  -  go ahead and release.
>>
>> On Tue, Aug 30, 2016 at 5:28 PM, Roshan Wijesena  wrote:
>>
>>> Hi All,
>>>
>>> This is the 3rd Release Candidate of WSO2 API Manager mediation policy
>>> tooling 2.0.0.
>>>
>>> Please download, test the product and vote. The vote will be open for 72
>>> hours or as needed.
>>>
>>> *Source and distribution*
>>>
>>> *Tooling*  : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>>> g/Released-release-2.0.3-RC3-2016-08-30-105251
>>>
>>>
>>> Please vote as follows.
>>> [+] Stable - go ahead and release
>>> [-] Broken - do not release (explain why)
>>>
>>> Thanks,
>>> WSO2 APIM team.
>>>
>>> --
>>> Roshan Wijesena.
>>> Senior Software Engineer-WSO2 Inc.
>>> Mobile: *+94719154640 <%2B94719154640>*
>>> Email: ros...@wso2.com
>>> *WSO2, Inc. :** wso2.com *
>>> lean.enterprise.middleware.
>>>
>>
>>
>>
>> --
>> *Sam Sivayogam*
>>
>> Senior 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
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618
> Blog:harshcreationz.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

Re: [Dev] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Harsha Kumara]

Tested basic functionality on Ubuntu 14.04.5 LTS.

[+]  Stable  -  go ahead and release.

On Thu, Sep 1, 2016 at 3:46 PM, Sam Sivayogam  wrote:

> Tested in Mac. Was able add custom sequences to APIM through dev studio.
> [+]  Stable  -  go ahead and release.
>
> On Tue, Aug 30, 2016 at 5:28 PM, Roshan Wijesena  wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 API Manager mediation policy
>> tooling 2.0.0.
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> *Source and distribution*
>>
>> *Tooling*  : https://github.com/wso2/devstudio-tooling-apim/releases/
>> tag/Released-release-2.0.3-RC3-2016-08-30-105251
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> WSO2 APIM team.
>>
>> --
>> Roshan Wijesena.
>> Senior Software Engineer-WSO2 Inc.
>> Mobile: *+94719154640 <%2B94719154640>*
>> Email: ros...@wso2.com
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>
>
>
> --
> *Sam Sivayogam*
>
> Senior 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
>
>


-- 
Harsha Kumara
Software Engineer, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] ESB error when login to admin console

[Jithendra Sirimanne]

Hi,

I have configured fresh ESB pack with Nginx reverse proxy. Now when I try
to log into ESB console I get a "Error 403 - Forbidden". In the carbon log
it shows

TID: [-1234] [] [2016-09-01 15:46:17,417]  WARN
{org.owasp.csrfguard.log.JavaLogger} -  potential cross-site request
forgery (CSRF) attack thwarted (user:, ip:127.0.0.1,
method:POST, uri:/carbon//admin/js/csrfPrevention.js, error:required token
is missing from the request) {org.owasp.csrfguard.log.JavaLogger}
TID: [-1234] [] [2016-09-01 15:46:21,821]  WARN
{org.owasp.csrfguard.log.JavaLogger} -  potential cross-site request
forgery (CSRF) attack thwarted (user:, ip:127.0.0.1,
method:POST, uri:/carbon//admin/login_action.jsp, error:required token is
missing from the request) {org.owasp.csrfguard.log.JavaLogger}

Any ideas to fix this?

Best Regards
Jithendra

--
Jithendra Sirimanne
*Systems Engineer*
Mobile: +94 (0) 716 374696 <+94+(0)+716+374696>
Tel  : +94 112 145 345
Email  : jithen...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Unable to make the provider writeable on publisher

[Shakila Sivagnanarajah]

Hi,

I tried to change the provider while adding the asset. I did following
change in both [1] and [2].

asset.configure = function() {
return {
table:{
overview:{
fields: {
provider:{

*readonly:false,auto:false*
}
}
}
}
};
};

[1]
wso2es-2.1.0/repository/deployment/server/jaggeryapps/store/extensions/assets/default/asset.js
[2]
wso2es-2.1.0/repository/deployment/server/jaggeryapps/store/extensions/assets/esbconnector/asset.js

But still no improvement. Did I miss any step for this?
[image: Inline image 1]

Thanks

-- 
Shakila Sivagnanarajah
Software Engineer
Mobile :+94 (0) 768 856837
shak...@wso2.com
WSO2, Inc.
lean . enterprise . middleware
http://www.wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Sam Sivayogam]

Tested in Mac. Was able add custom sequences to APIM through dev studio.
[+]  Stable  -  go ahead and release.

On Tue, Aug 30, 2016 at 5:28 PM, Roshan Wijesena  wrote:

> Hi All,
>
> This is the 3rd Release Candidate of WSO2 API Manager mediation policy
> tooling 2.0.0.
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> *Source and distribution*
>
> *Tooling*  : https://github.com/wso2/devstudio-tooling-apim/
> releases/tag/Released-release-2.0.3-RC3-2016-08-30-105251
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> WSO2 APIM team.
>
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>



-- 
*Sam Sivayogam*

Senior 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] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Chamin Dias]

[+] Stable -  go ahead and release.


On Thu, Sep 1, 2016 at 2:50 PM, Uvindra Dias Jayasinha 
wrote:

> [+] Stable - go ahead and release
>
> On 30 August 2016 at 17:28, Roshan Wijesena  wrote:
>
>> Hi All,
>>
>> This is the 3rd Release Candidate of WSO2 API Manager mediation policy
>> tooling 2.0.0.
>>
>> Please download, test the product and vote. The vote will be open for 72
>> hours or as needed.
>>
>> *Source and distribution*
>>
>> *Tooling*  : https://github.com/wso2/devstudio-tooling-apim/releases/ta
>> g/Released-release-2.0.3-RC3-2016-08-30-105251
>>
>>
>> Please vote as follows.
>> [+] Stable - go ahead and release
>> [-] Broken - do not release (explain why)
>>
>> Thanks,
>> WSO2 APIM team.
>>
>> --
>> Roshan Wijesena.
>> Senior Software Engineer-WSO2 Inc.
>> Mobile: *+94719154640 <%2B94719154640>*
>> Email: ros...@wso2.com
>> *WSO2, Inc. :** wso2.com *
>> lean.enterprise.middleware.
>>
>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 33962
>
> ___
> 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] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Uvindra Dias Jayasinha]

[+] Stable - go ahead and release

On 30 August 2016 at 17:28, Roshan Wijesena  wrote:

> Hi All,
>
> This is the 3rd Release Candidate of WSO2 API Manager mediation policy
> tooling 2.0.0.
>
> Please download, test the product and vote. The vote will be open for 72
> hours or as needed.
>
> *Source and distribution*
>
> *Tooling*  : https://github.com/wso2/devstudio-tooling-apim/
> releases/tag/Released-release-2.0.3-RC3-2016-08-30-105251
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> WSO2 APIM team.
>
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>



-- 
Regards,
Uvindra

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

Re: [Dev] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[Nuwan Dias]

[+] Stable - go ahead and release

On Wed, Aug 31, 2016 at 7:47 PM, Dulanja Liyanage  wrote:

> Herewith I withdraw the -1 after the internal discussion we had on this.
> Thanks.
>
> On Wed, Aug 31, 2016 at 5:40 PM, Nuwan Dias  wrote:
>
>> Hi Dulanja,
>>
>> This is dev-studio tooling. A client side (desktop) application. What
>> kind of vulnerabilities do we expect to uncover in those?
>>
>> And also this is more or less the exact code base of ESB tooling. AFAIK
>> we haven't forced security analysis on ESB tooling code base. Do we still
>> need to call off this vote?
>>
>> Thanks,
>> NuwanD.
>>
>> On Wed, Aug 31, 2016 at 5:16 PM, Dulanja Liyanage 
>> wrote:
>>
>>> -1
>>>
>>> Security analysis reports not provided.
>>>
>>> On 31 Aug 2016 11:40 a.m., "Jasintha Dasanayake" 
>>> wrote:
>>>
 Hi Roshan

 I tested basic functionalities with API cloud and those working fine,

 hence +1 for release

 Thanks and Regards
 /Jasintha


 On Tue, Aug 30, 2016 at 5:28 PM, Roshan Wijesena 
 wrote:

> Hi All,
>
> This is the 3rd Release Candidate of WSO2 API Manager mediation policy
> tooling 2.0.0.
>
> Please download, test the product and vote. The vote will be open for
> 72 hours or as needed.
>
> *Source and distribution*
>
> *Tooling*  : https://github.com/wso2/devs
> tudio-tooling-apim/releases/tag/Released-release-2.0.3-RC3-2
> 016-08-30-105251
>
>
> Please vote as follows.
> [+] Stable - go ahead and release
> [-] Broken - do not release (explain why)
>
> Thanks,
> WSO2 APIM team.
>
> --
> Roshan Wijesena.
> Senior Software Engineer-WSO2 Inc.
> Mobile: *+94719154640 <%2B94719154640>*
> Email: ros...@wso2.com
> *WSO2, Inc. :** wso2.com *
> lean.enterprise.middleware.
>



 --

 *Jasintha Dasanayake**Associate Technical Lead*

 *WSO2 Inc. | http://wso2.com lean . enterprise .
 middleware*


 *mobile :- 0711-368-118 <0711-368-118>*

 ___
 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
>>>
>>>
>>
>>
>> --
>> Nuwan Dias
>>
>> Software Architect - WSO2, Inc. http://wso2.com
>> email : nuw...@wso2.com
>> Phone : +94 777 775 729
>>
>
>
>
> --
> Thanks & Regards,
> Dulanja Liyanage
> Lead, Platform Security Team
> WSO2 Inc.
>



-- 
Nuwan Dias

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

Re: [Dev] Improving MB Slot Coordinator to Work in a NATed/Containerized Environment

[Isuru Haththotuwa]

Thanks Imesh. Seems there are some new API changes in the related methods
now. Will send a modified PR with the changes.

On Thu, Sep 1, 2016 at 12:02 PM, Imesh Gunaratne  wrote:

>
>
> On Wed, Aug 31, 2016 at 7:17 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Imesh and Ramith,
>>
>> Replied to your comments in the original PR, please check.
>>
>
> ​Great work Isuru! It looks good to me now!​
>
>
>>
>> On Tue, Aug 30, 2016 at 7:58 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Hasitha,
>>>
>>> Please find the PR for adding the new properties to the broker.xml file
>>> [1].
>>>
>>> [1]. https://github.com/wso2/carbon-business-messaging/pull/336
>>>
>>> On Sun, Aug 28, 2016 at 8:23 PM, Isuru Haththotuwa 
>>> wrote:
>>>
 Hi Hasitha,

 On Sun,  Aug 28, 2016 at 7:30 AM, Hasitha Hiranya 
 wrote:

> Hi,
>
> Thank You, Isuru...!!
>
> If you add a new property to broker.xml config file, that file needs a
> update as well. So broker.xml of carbon-business-messaging [1] has to be
> changed I guess. Please add a proper description to the property in the
> file for the parameter you are adding.
>
 Thanks, will do and send a PR.

>
> [1]. https://github.com/wso2/carbon-business-messaging/blob/
> master/features/andes/org.wso2.carbon.andes.server.feature/r
> esources/conf/broker.xml
>
> Thanks
>
> On Fri, Aug 26, 2016 at 8:15 PM, Imesh Gunaratne 
> wrote:
>
>> [+ Ramith]
>>
>> Great work Isuru!! Well written!!
>> I think it might be useful for explaining why this feature was needed
>> in the PR description.
>>
>> Thanks!
>>
>> On Fri, Aug 26, 2016 at 5:37 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi MB team,
>>>
>>> Please review the P/R for $subject [1], for the jira ticket reported
>>> at [2]. I'm yet to write a test for this, will send a separate P/R once
>>> done.
>>>
>>> [1]. https://github.com/wso2/andes/pull/685
>>>
>>> [2]. https://wso2.org/jira/browse/MB-1736
>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *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
>>
>>
>
>
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>


 --
 Thanks and Regards,

 Isuru H.
 +94 716 358 048* *



>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* *
>>>
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> *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
>
>


-- 
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] Adding BPS Tooling p2 Repos to product-dist

[Jasintha Dasanayake]

Hi Heshitha

I have published the BPS tools in[1] , please verify it first before push
into our public p2 repository

Thanks and Regards
/Jasintha

[1] -
http://builder1.us1.wso2.org/~developerstudio/developer-studio-kernel/4.1.0/bps-tooling/releases/

On Wed, Aug 31, 2016 at 4:36 PM, Heshitha Hettihewa 
wrote:

> Hi all,
>
> Can you add the following P2 Repos(Composite [1] and main [2]) of BPS
> Tooling in to the product dist?
>
> [1]. https://github.com/wso2/devstudio-tooling-bps/
> releases/download/v3.6.0/wso2-developer-studio-kernel-bps-
> composite-p2-3.6.0.zip
> [2]. https://github.com/wso2/devstudio-tooling-bps/
> releases/download/v3.6.0/wso2-developer-studio-kernel-bps-
> main-p2-3.6.0.zip
>
> Thanks.
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>



-- 

*Jasintha Dasanayake**Associate Technical Lead*

*WSO2 Inc. | http://wso2.com lean . enterprise .
middleware*


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

Re: [Dev] Improving MB Slot Coordinator to Work in a NATed/Containerized Environment

[Imesh Gunaratne]

On Wed, Aug 31, 2016 at 7:17 PM, Isuru Haththotuwa  wrote:

> Hi Imesh and Ramith,
>
> Replied to your comments in the original PR, please check.
>

​Great work Isuru! It looks good to me now!​


>
> On Tue, Aug 30, 2016 at 7:58 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi Hasitha,
>>
>> Please find the PR for adding the new properties to the broker.xml file
>> [1].
>>
>> [1]. https://github.com/wso2/carbon-business-messaging/pull/336
>>
>> On Sun, Aug 28, 2016 at 8:23 PM, Isuru Haththotuwa 
>> wrote:
>>
>>> Hi Hasitha,
>>>
>>> On Sun,  Aug 28, 2016 at 7:30 AM, Hasitha Hiranya 
>>> wrote:
>>>
 Hi,

 Thank You, Isuru...!!

 If you add a new property to broker.xml config file, that file needs a
 update as well. So broker.xml of carbon-business-messaging [1] has to be
 changed I guess. Please add a proper description to the property in the
 file for the parameter you are adding.

>>> Thanks, will do and send a PR.
>>>

 [1]. https://github.com/wso2/carbon-business-messaging/blob/
 master/features/andes/org.wso2.carbon.andes.server.feature/r
 esources/conf/broker.xml

 Thanks

 On Fri, Aug 26, 2016 at 8:15 PM, Imesh Gunaratne 
 wrote:

> [+ Ramith]
>
> Great work Isuru!! Well written!!
> I think it might be useful for explaining why this feature was needed
> in the PR description.
>
> Thanks!
>
> On Fri, Aug 26, 2016 at 5:37 PM, Isuru Haththotuwa 
> wrote:
>
>> Hi MB team,
>>
>> Please review the P/R for $subject [1], for the jira ticket reported
>> at [2]. I'm yet to write a test for this, will send a separate P/R once
>> done.
>>
>> [1]. https://github.com/wso2/andes/pull/685
>>
>> [2]. https://wso2.org/jira/browse/MB-1736
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *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
>
>


 --
 *Hasitha Abeykoon*
 Senior Software Engineer; WSO2, Inc.; http://wso2.com
 *cell:* *+94 719363063*
 *blog: **abeykoon.blogspot.com* 


>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>> +94 716 358 048* *
>>>
>>>
>>>
>>
>>
>> --
>> Thanks and Regards,
>>
>> Isuru H.
>> +94 716 358 048* *
>>
>>
>>
>
>
> --
> Thanks and Regards,
>
> Isuru H.
> +94 716 358 048* *
>
>
>


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