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

[Isuru Haththotuwa]

Hi Osura,

On Tue, Jul 5, 2016 at 9:49 AM, Osura Rathnayake  wrote:

> Hi Akila,
>
> Please find more about tenantId here [1].
>
Seems the tenantId you are referring to a detail specific to Azure. Please
confirm. Since there is a tenancy concept in Carbon as well, shall we
re-name the variable and constant to something more meaningful (ex.: azure
TenantId for the variable name)?

>
> Regarding the last point, what I do is, I collect all the ip addresses and
> update the hazelcast config. in that case how can i get localMemberPort for
> each member since localMemberPOrt is defined in each member's axis2.xml.
> Also I observed that when the same localMemberPort is assigned to all the
> members, cluster discovery works fine but when different ports are assigned
> it doesn't work.
>
There should be a way to get this information (clustering port of members)
from the API, as we do for the IP addresses currently. If not, IMHO we can
keep the current implementation (where it assumes clustering port is 4000)
and document it clearly.

>
> Yes I'm still implementing the test cases and will update soon.
>
> [1]
> https://azure.microsoft.com/en-gb/documentation/articles/resource-group-create-service-principal-portal/
>
>
> thanks,
>
> On Mon, Jul 4, 2016 at 9:41 PM, Akila Ravihansa Perera  > wrote:
>
>> Hi Osura,
>>
>> I'm still not clear on tenantId. Perhaps you can explain in detail during
>> the code review meeting. Regarding the last point, yes it should be
>> localMemberPort. Sorry, it was a typo.
>>
>> One more thing, I noticed that test cases are empty [1]. Are you still
>> working on implementing those?
>>
>> [1]
>> https://github.com/osuran/azure-membership-scheme/blob/master/src/test/java/org/wso2/carbon/clustering/azure/AppTest.java
>>
>> Thanks.
>>
>
>
>
> --
> Regards,
> Osura Rathnayake
>



-- 
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 Connector] Concur- getExchangeRate issue

[Keerthika Mahendralingam]

+dev

On Tue, Jul 5, 2016 at 9:57 AM, Keerthika Mahendralingam  wrote:

> Yes Malaka, We can only get the exchange rate with the expense(as in [1] )
> which is already added to the expense as in [2].
>
> @Godwin, AFAIK we don't have any connector method to get the exchange rate.
>
> [1].
> https://developer.concur.com/api-reference-deprecated/version-one-one/expense-entry/get-expense-entry.html
> [2].
> https://developer.concur.com/api-reference-deprecated/version-one-one/expense-entry/post-expense-entry.html
>
> Thanks,
> Keerthika.
>
> On Tue, Jul 5, 2016 at 9:52 AM, Godwin Shrimal  wrote:
>
>> [Warning : Moving to internal]
>>
>> Please remove the Get Exchange Rate sections in Concur connector
>> documentation since its no longer exist.
>>
>>
>>
>> Thanks
>> Godwin
>>
>>
>> On Sun, Jul 3, 2016 at 11:20 PM, Malaka Silva  wrote:
>>
>>> Thx Rajjaz,
>>>
>>> AFAIK you can only get exchange rate with the expense.
>>>
>>> @Rajjaz / keertika - Please confirm.
>>>
>>> [1]
>>> https://developer.concur.com/api-reference-deprecated/version-one-one/expense-entry/get-expense-entry.html
>>>
>>> On Sun, Jul 3, 2016 at 9:22 AM, Rajjaz Mohammed  wrote:
>>>
 Hi,

 Method removed from the connector and will add a new version in the
 store. Other then getExchangeRate method other methods are works fine[1].

 [1] https://wso2.org/jira/browse/ESBCONNECT-107

 On Sat, Jul 2, 2016 at 11:18 AM, Keerthika Mahendralingam <
 keerth...@wso2.com> wrote:

> Hi Godwin,
>
> According to the documentation [1], this method is not available in
> the API. I have created a public JIRA[2] to remove this method from the
> connector.
>
> [1].
> https://developer.concur.com/api-reference/expense/expense-report/expense-form.html
>
> [2]. https://wso2.org/jira/browse/ESBCONNECT-107
>
> Thanks,
> Keerthika.
>
> On Sat, Jul 2, 2016 at 1:10 AM, Godwin Shrimal 
> wrote:
>
>> Hi All,
>>
>> I am trying to get exchange rate using WSO2 Concur connector and
>> getting below response.
>>
>> 
>> Not Found
>> 2016-07-01T15:31:40
>> 26D1A0AC-E21C-4626-85A3-2BB5380505DF
>> 
>>
>> Once we enable wire log it has an outbound as *GET
>> /api/v3.0/expense/exchangerates/?forDate=01/01/2016& HTTP/1.1 , *So
>> we try the relevant rest endpoint   which is in [1] also give the same
>> result. Concur shows the particular error in [2].
>>
>> Any thought ?
>>
>>
>> [1]
>> https://www.concursolutions.com/api/v3.0/expense/exchangerates/?forDate=05/05/2016
>> [2]
>> https://developer.concur.com/tools-support/reference/http-codes.html
>>
>> *Note: My token is valid since when I try some other endpoint those
>> are working properly.*
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>>
>
>
>
> --
> 
> Keerthika Mahendralingam
> Software Engineer
> Mobile :+94 (0) 776 121144
> keerth...@wso2.com
> WSO2, Inc.
> lean . enterprise . middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Thank you
 Best Regards

 *Rajjaz HM*
 Associate Software Engineer
 Platform Extension Team
 WSO2 Inc. 
 lean | enterprise | middleware
 Mobile | +94752833834|+94777226874
 Email   | raj...@wso2.com
 LinkedIn  | Blogger
  | WSO2 Profile
 

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


>>>
>>>
>>> --
>>>
>>> Best Regards,
>>>
>>> Malaka Silva
>>> Senior Technical Lead
>>> M: +94 777 219 791
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>> Skype : malaka.sampath.silva
>>> LinkedIn : http://www.linkedin.com/pub/malaka-silva/6/33/77
>>> Blog : http://mrmalakasilva.blogspot.com/
>>>
>>> WSO2, Inc.
>>> lean . enterprise . middleware
>>> http://www.wso2.com/
>>> http://www.wso2.com/about/team/malaka-silva/
>>> 
>>> https://store.wso2.com/store/
>>>
>>> Save a tree -Conserve nature & Save the world for your future. Print
>>> this email only if it is absolutely necessary.
>>>
>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> 

[Dev] Regarding APPM-1160

[Dinusha Senanayaka]

Hi Chathura,

Does multi-tenancy supports in EMM for device management ? If yes, we need
to fix [1] as well, which means we cannot keep this configuration in the
app-manager.xml. Need to take it to registry.

[1] https://wso2.org/jira/browse/APPM-1160

Regards,
Dinsuha.

-- 
Dinusha Dilrukshi
Associate Technical Lead
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Axis2] Response status code 202 for No content message body

[Malintha Amarasinghe]

Agree with Manuri and Madhawa. 202 Accepted is used in long running
processes [1]. 204 is the better status code to say when there's no content
body but the request is processed.

[1] http://farazdagi.com/blog/2014/rest-long-running-jobs/

On Tue, Jul 5, 2016 at 10:00 AM, Manuri Amaya Perera 
wrote:

> AFAIU 202 should not be sent when request is already processed.
> [1] clearly states that 202 is for a situation like, "The request has been
> accepted for processing, but the processing has not been completed. The
> request might or might not eventually be acted upon, as it might be
> disallowed when processing actually takes place. There is no facility for
> re-sending a status code from an asynchronous operation such as this."
>
> So I think if the request is successfully fulfilled and there is no entity
> body 204 should be sent.
>
>
> [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
>
> Thanks,
> Manuri
>
> On Tue, Jun 28, 2016 at 6:03 PM, Madhawa Gunasekara 
> wrote:
>
>> Hi Niranjan,
>>
>> Yes, but the point is that, we can use accepted status code for the
>> requests which has been accepted for processing, but the processing has not
>> been completed [1]. This works for asynchronous requests.
>>
>> But when it comes synchronous requests, we send the response after
>> processing is completed. so AFAIU, we can't use accepted status code for
>> those kind of scenarios.
>>
>> [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
>>
>> Thanks,
>> Madhawa
>>
>>
>>
>> On Tue, Jun 28, 2016 at 5:34 PM, Niranjan Karunanandham <
>> niran...@wso2.com> wrote:
>>
>>> Hi Madhawa,
>>>
>>> AFAIK, even 202 can have with and without body.
>>>
>>> Regards,
>>> Nira
>>>
>>> On Tue, Jun 28, 2016 at 4:52 PM, Madhawa Gunasekara 
>>> wrote:
>>>
 Hi All,

 We set 202 (Accepted) status code for the response when there isn't
 content message body. but AFAIU We have to set 204 (No Content) for
 successful responses where there isn't a content message body [1].

 This issue is reported in [2].

 Highly appreciated your thoughts on this.

 [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
 [2] https://wso2.org/jira/browse/DS-886

 Thanks,
 Madhawa

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

 mobile: +94 719411002 <+94+719411002>
 blog: *http://madhawa-gunasekara.blogspot.com
 *
 linkedin: *http://lk.linkedin.com/in/mgunasekara
 *

>>>
>>>
>>>
>>> --
>>>
>>>
>>> *Niranjan Karunanandham*
>>> Associate Technical Lead - WSO2 Inc.
>>> WSO2 Inc.: http://www.wso2.com
>>>
>>
>>
>>
>> --
>> *Madhawa Gunasekara*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 719411002 <+94+719411002>
>> blog: *http://madhawa-gunasekara.blogspot.com
>> *
>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Manuri Amaya Perera*
>
> *Software Engineer*
>
> *WSO2 Inc.*
>
> *Blog: http://manuriamayaperera.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] [Axis2] Response status code 202 for No content message body

[Manuri Amaya Perera]

AFAIU 202 should not be sent when request is already processed.
[1] clearly states that 202 is for a situation like, "The request has been
accepted for processing, but the processing has not been completed. The
request might or might not eventually be acted upon, as it might be
disallowed when processing actually takes place. There is no facility for
re-sending a status code from an asynchronous operation such as this."

So I think if the request is successfully fulfilled and there is no entity
body 204 should be sent.


[1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Thanks,
Manuri

On Tue, Jun 28, 2016 at 6:03 PM, Madhawa Gunasekara 
wrote:

> Hi Niranjan,
>
> Yes, but the point is that, we can use accepted status code for the
> requests which has been accepted for processing, but the processing has not
> been completed [1]. This works for asynchronous requests.
>
> But when it comes synchronous requests, we send the response after
> processing is completed. so AFAIU, we can't use accepted status code for
> those kind of scenarios.
>
> [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
>
> Thanks,
> Madhawa
>
>
>
> On Tue, Jun 28, 2016 at 5:34 PM, Niranjan Karunanandham  > wrote:
>
>> Hi Madhawa,
>>
>> AFAIK, even 202 can have with and without body.
>>
>> Regards,
>> Nira
>>
>> On Tue, Jun 28, 2016 at 4:52 PM, Madhawa Gunasekara 
>> wrote:
>>
>>> Hi All,
>>>
>>> We set 202 (Accepted) status code for the response when there isn't
>>> content message body. but AFAIU We have to set 204 (No Content) for
>>> successful responses where there isn't a content message body [1].
>>>
>>> This issue is reported in [2].
>>>
>>> Highly appreciated your thoughts on this.
>>>
>>> [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html
>>> [2] https://wso2.org/jira/browse/DS-886
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> --
>>> *Madhawa Gunasekara*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 719411002 <+94+719411002>
>>> blog: *http://madhawa-gunasekara.blogspot.com
>>> *
>>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>>> *
>>>
>>
>>
>>
>> --
>>
>>
>> *Niranjan Karunanandham*
>> Associate Technical Lead - WSO2 Inc.
>> WSO2 Inc.: http://www.wso2.com
>>
>
>
>
> --
> *Madhawa Gunasekara*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 719411002 <+94+719411002>
> blog: *http://madhawa-gunasekara.blogspot.com
> *
> linkedin: *http://lk.linkedin.com/in/mgunasekara
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Manuri Amaya Perera*

*Software Engineer*

*WSO2 Inc.*

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

Re: [Dev] [Dockerfile] WSO2IS docker image build fails due to missing file

[Udara Liyanage]

Hi,

The issue was IS unzipped directory was there at files directory.
Thanks Thanuja for the offline help.

On Mon, Jul 4, 2016 at 6:41 AM, Udara Liyanage  wrote:

> Hi,
>
> WSO2 IS as KM docker image build fails due to a missing file. This file is
> not found even in original pack.
>
> bash build.sh -v 5.1.0 -s mesos -r puppet
>
> 172.17.0.3 - - [04/Jul/2016 06:21:27] "GET
> /modules/wso2is_km/files/wso2is_km-5.1.0/modules/ws/ HTTP/1.1" 200 -
> 2016-07-04 10:21:27 URL:
> http://172.17.0.1:8002/modules/wso2is_km/files/wso2is_km-5.1.0/modules/ws/
> [320/320] ->
> "modules/wso2is_km/files/wso2is_km-5.1.0/modules/ws/index.html" [1]
> 172.17.0.3 - - [04/Jul/2016 06:21:27] code 404, message File not found
> 172.17.0.3 - - [04/Jul/2016 06:21:27] "GET
> /modules/wso2is_km/files/wso2is_km-5.1.0/css/is-docs.css HTTP/1.1" 404 -
>
> http://172.17.0.1:8002/modules/wso2is_km/files/wso2is_km-5.1.0/css/is-docs.css
> :
> *2016-07-04 10:21:27 ERROR 404: File not found.*
> 172.17.0.3 - - [04/Jul/2016 06:21:27] "GET /mod
> ERROR: Docker image
> cdtsdvo108p.rxcorp.com:8443/wso2/devl/wso2is_km-mesos:5.1.0 creation
> failed
>
> --
>
> Udara Liyanage
> Software Engineer
> WSO2, Inc.: http://wso2.com
> lean. enterprise. middleware
>
> web: http://udaraliyanage.wordpress.com
> phone: +94 71 443 6897
>



-- 

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

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Tooling]-Developer Studio Kernel 4.2.0 alpha released !

[Jasintha Dasanayake]

Hi all,

We are pleased to announce the alpha release of
*WSO2 Developer Studio Kernel 4.2.0 *

P2 repository of WSO2 developer Studio kernel 4.2.0-Alpha is available here
.
Source
and Tag Location for this release is available here

.

Developer Studio 4.2.0 Kernel is Eclipse Mars (Eclipse 4.5) based Eclipse
Rich Client Platform, commonly know as Eclipse RCP, which is widely used to
ship commercial tooling with commercial branding.From the initial efforts, With
the use of banding capabilities of Eclipse RCP, we did some UI adjustments
to components such as splash screens, icons, about dialogs, and dashboard.

In this alpha release, we have Introduced Eclipse RCP feature and added
below set of new features to it.

   - Developer Studio RCP branding feature
   - JS based dynamic dashboard  feature
   - XULRunner embedding Features

*How to Contribute*

Please report issues at WSO2 JIRA 
Send your pull requests to developer-studio-kernel


*Contact us*

WSO2 developers can be contacted via the mailing lists:

WSO2 Developers List : dev@wso2.org
WSO2 Architecture List : architect...@wso2.org

Thanks go everyone who made this checkpoint possible.

Thanks,
Developer Studio Team

-- 

*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] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Hasitha Aravinda]

Tested with BPS 3.6.0-SNAPSHOT. No issue found.

[x] Stable - go ahead and release.

Thanks,
Hasitha.

On Mon, Jul 4, 2016 at 6:42 PM, Kasun Bandara  wrote:

> Hi all,
>
> I could successfully run IS test suit with the upgraded Kernel 4.4.7- RC1.
> Hence +1 for the release.
>
> Thanks,
> Kasun
>
> On Mon, Jul 4, 2016 at 5:35 PM, Chamalee De Silva 
> wrote:
>
>> P.S. Test done base done API Manager 2.0.0 beta-2
>>
>> On Mon, Jul 4, 2016 at 5:33 PM, Chamalee De Silva 
>> wrote:
>>
>>> Hi,
>>> I tested the kernel 4.4.7 RC1 with
>>>
>>> MySQL 5.6 and  5.7,
>>> Oracle 11g,
>>> PostgreSQL 9.3
>>>
>>> and they worked without an issue.
>>>
>>> [x] Stable - go ahead and release.
>>>
>>>
>>>
>>> Thanks,
>>> Chamalee
>>>
>>> On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage 
>>> wrote:
>>>
 Hi,

 I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
 issue related to this RC.

 *Note :* Feature repo not shown issue [1], introduced with kernel
 4.4.6 is observed. Hope this will be fixed in a future release.

 [1] https://wso2.org/jira/browse/CARBON-15973

 Regards,
 Anupama

 On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne  wrote:

> Hi,
>
> I tested the kernal with following databases and no issues observed.
>
> Test Area:
> Add/ Delete resource (inline text) and collection
> Add/Remove user and role
>
> Databases:
> mysql 5.5.
> mysql 5.7
> postgres 9.3
> oracle 12c
>
> Regards,
> Shashika
>
> Shashika Ubhayaratne
> Associate Technical Lead - QA
> WSO2 Inc: http://www.wso2.com/
> Mobile: *+94773383831*
>
> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna 
> wrote:
>
>> Hi all,
>>
>> I've tested the kernel with following databases and found no issues.
>> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
>> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>>
>> [x] Stable - go ahead and release.
>>
>> Regards,
>> Aruna
>> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake > > wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=13113
>>>
>>> Please download and test your products with kernel 4.4.7 RC1 and
>>> vote. Vote will be open for 72 hours or as longer as needed.
>>>
>>> Source and binary distribution files:
>>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>>>
>>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>>>
>>> Maven staging repository
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>>>
>>> The tag to be voted upon :
>>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thank you
>>> Carbon Team​
>>>
>>>
>>> *Jayanga Dissanayake*
>>> Associate Technical Lead
>>> WSO2 Inc. - http://wso2.com/
>>> lean . enterprise . middleware
>>> email: jaya...@wso2.com
>>> mobile: +94772207259
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.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
>
>


 --
 Anupama Pathirage
 Associate Technical Lead
 WSO2, Inc.  http://wso2.com/
 Email: anup...@wso2.com
 Mobile:+94 71 8273 979



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


>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Chamalee De Silva*
>>> Software Engineer
>>> *WS**O2* Inc. .:http://wso2.com
>>>
>>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>>
>>>
>>> * *
>>>
>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. .:http://wso2.com
>>
>> Office   :- *+94 11 

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

[Akila Ravihansa Perera]

Hi Osura,

I'm still not clear on tenantId. Perhaps you can explain in detail during
the code review meeting. Regarding the last point, yes it should be
localMemberPort. Sorry, it was a typo.

One more thing, I noticed that test cases are empty [1]. Are you still
working on implementing those?

[1]
https://github.com/osuran/azure-membership-scheme/blob/master/src/test/java/org/wso2/carbon/clustering/azure/AppTest.java

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

Re: [Dev] How can we keep wait a docker container to start

[Gayan Gunarathne]

Yeah.Currently this is not supported with Docker Compose.So we are using
sleep for this.

But there is a health check feature listed under next version[1][2].May be
with that version we able to use that to determine if a container is
"alive".

[1]https://github.com/docker/docker/issues/21142
[2]https://github.com/docker/compose/issues/374

Thanks,
Gayan

On Mon, Jul 4, 2016 at 8:17 PM, Lakmal Warusawithana 
wrote:

> Its only work for container start time , not wait for app start time
> inside the container. We have introduced sleep environment variable in our
> products, if we define sleep in compose, our startup script wait sleep time
> before start the server.
>
>
> On Monday, July 4, 2016, Tharindu Dharmarathna  wrote:
>
>> Hi All,
>>
>> Is there any way to wait the start of containers which depends on other
>> container get started successfully.
>>
>> I had tried with [1] . But it didn't get worked as well.
>>
>> [1] - https://docs.docker.com/compose/startup-order/
>>
>> --
>>
>> *Tharindu Dharmarathna*Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94779109091 <%2B94779109091>*
>>
>
>
> --
> Sent from Gmail Mobile
>



-- 

Gayan Gunarathne
Technical Lead, WSO2 Inc. (http://wso2.com)
Committer & PMC Member, Apache Stratos
email : gay...@wso2.com  | mobile : +94 775030545 <%2B94%20766819985>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] [GSoC] Meeting minutes from Dockerfiles test framework demo

[Imesh Gunaratne]

Hi Abhishek,

Were you able to check the possibility of verifying Docker images using K8S
artifacts?

Thanks

On Wed, Jun 29, 2016 at 12:01 PM, Vishanth Balasubramaniam <
vishan...@wso2.com> wrote:

> Great work Abhishek. We need to prioritize the work and discuss the final
> deliverables. We can probably do that in our next meeting. It would be
> great if you could do an effort estimation in your milestone plan sheet,
> where you can identify how many days it would take to finish off these
> tasks.
>
> Regards,
> Vishanth
>
> On Wed, Jun 29, 2016 at 11:55 AM, Abhishek Tiwari <
> abhishek.tiwari0...@gmail.com> wrote:
>
>> Hi All,
>>
>> Thanks so much for attending the demo and providing great feedback.
>> Following are the meeting minutes:
>>
>> 1. Demo of testing WSO2ESB 4.9.0 with default profile, discussed output
>> log and few implementation details.
>>
>> 2. Feedback:
>> a) Test framework should add the ability to check docker logs as well.
>> b) Checking for exposed ports should happen periodically with a timeout,
>> instead of a static sleep.
>> c) Look into feasibility of classifying errors (in build or run) in terms
>> of specific module (e.g. build failed due to an issue with hieradata).
>> d) Check status code returned from build and run scripts.
>> e) Look into integrating the test results into Jenkins, to allow nightly
>> runs.
>> f) Support of Kubernetes platform as well as product profiles (worker,
>> manager nodes)
>>
>> Please add if I missed something.
>>
>> Thanks
>> Abhishek
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *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
>
>


-- 
*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
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Osura Rathnayake]

Hi Akila,

Thank you for the feedback.
tenantId is used because it is needed in the url which is used to
authenticate. WIthout the tenantId the url would be incomplete.
I have fixed [1] all the issues you have mentioned in the previous email
except for the Netflix Feign standard and I'm looking into it. About the
last point, is it localMemberHostPort or localMemberPort ?

[1] https://github.com/osuran/azure-membership-scheme

thanks,

On Thu, Jun 30, 2016 at 11:22 AM, Akila Ravihansa Perera  wrote:

> Hi Osura,
>
> Good progress :)
>
> Netflix Feign [1] is a highly customizable and easy to use REST API client
> framework. The GitHub page itself contains many samples. We have written
> Mesos membership scheme [2] using that which you can use as a reference
> guideline. Please refactor your code to use this client. Let me know if you
> run into any issues.
>
> I noticed few more issues in the code;
>  - No need to define a variable and assign a const [3]. You can directly
> use the const.
>  - Why do you need to append tenantId to authorization endpoint? Just
> asking to clarify why tenantId is needed here.
>
> - You can move common operations to common method. In [4], instead of
> checking for empty values and in [5] reading from System.env. Move all that
> to getParameterValue method. This will reduce the amount of code you have
> to write.
>
>  - You don't have to log and throw [6]. This will only clutter the log
> file.
>
>  - You don't need a for loop here [7]. Simply use a for-each iterator.
>
>  - Don't put ":" in front of the placeholder [8]
>
>  - Don't put spaces around square brackets [9]
>
>  - You need to separate variables by commas [10]
>
>  - Use proper case for log msg labels [11]. Should be "VM-IP" or simply
> "IP Address" is enough. This should contain both IP and local port. Read
> below for more info on local port.
>
> * This is very important *
>  - Use localMemberHostPort defined in axis2.xml when adding the member IPs
> in [12]. This is the port that all WSO2 server instances are listening on
> for Hazelcast connections. By default it is 4000 that's why it works now.
> But for some reason if someone changes it, then this code will break.
>
> [1] https://github.com/Netflix/feign
> [2]
> https://github.com/wso2/mesos-artifacts/tree/master/common/mesos-membership-scheme
> [3]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L101
> [4]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L113
> [5]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L110
> [6]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L182
> [7]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L200
> [8]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L263
> [9]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L282
> [10]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L171
> [11]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L177
> [12]
> https://github.com/osuran/azure-membership-scheme/blob/master/src/main/java/org/wso2/carbon/clustering/azure/AzureMembershipScheme.java#L176
>
> Thanks.
>
>


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

Re: [Dev] [APIM 2.0] [clarification] [api manager xml] all server url's local ip has hard coded as 'localhost'

[Sam Sivayogam]

We did this change due to the issue discussed in mail thread [1]

[1] APIM Getting SSLPeerUnverifiedException after upgrading to kernel 4.4.4

Thanks,
Sam

On Mon, Jul 4, 2016 at 2:19 PM, Bhathiya Jayasekara 
wrote:

> Yes, we had to do this after kernel upgrade.
>
> Thanks,
> Bhathiya
>
> On Mon, Jul 4, 2016 at 2:15 PM, Kavitha Subramaniyam 
> wrote:
>
>> Hi apim team,
>>  I have observed $subject in 17th pack & beta2 pack[1] and we want to
>> make sure whether this change has been done purposely since earlier packs
>> had parameter reference for the server url.
>> Please confirm..
>>
>> [1] https://localhost:
>> ${mgt.transport.https.port}${carbon.context}services/
>>
>>
>> Thanks,
>> --
>> Kavitha.S
>> *Software Engineer -QA*
>> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
>> kavi...@wso2.com 
>>
>
>
>
> --
> *Bhathiya Jayasekara*
> *Senior Software Engineer,*
> *WSO2 inc., http://wso2.com *
>
> *Phone: +94715478185 <%2B94715478185>*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> *
> *Twitter: https://twitter.com/bhathiyax *
> *Blog: http://movingaheadblog.blogspot.com
> *
>
> ___
> 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] How can we keep wait a docker container to start

[Lakmal Warusawithana]

Its only work for container start time , not wait for app start time inside
the container. We have introduced sleep environment variable in our
products, if we define sleep in compose, our startup script wait sleep time
before start the server.

On Monday, July 4, 2016, Tharindu Dharmarathna  wrote:

> Hi All,
>
> Is there any way to wait the start of containers which depends on other
> container get started successfully.
>
> I had tried with [1] . But it didn't get worked as well.
>
> [1] - https://docs.docker.com/compose/startup-order/
>
> --
>
> *Tharindu Dharmarathna*Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94779109091*
>


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

Re: [Dev] [IS] RESTful Fine Grained Authorization-as-a-Service (AZaaS)

[Manujith Pallewatte]

Hi all,

So to start working on the points discussed in the mid evaluation, first is
to align the service with the REST profile of XACML 3.0 [1]
But according to the spec only the following 2 resources are defined

1) home - entry point for REST service, returns links to other resources
2) pdp - resource that given a XACML request presents the XACML response

but since the existing SOAP entitlement service exposes additional services
such as
getBooleanDecision, getDecisionByAttributes etc. there arises 2 issues

1) how to name those additional resources?
2) how to let the clients accessing the service know of the required
structure of each of these requests that are not defined in the XACML spec?

Please provide your suggestions on this

Thank You
Best Regards,
Manujith

[1]
http://docs.oasis-open.org/xacml/xacml-rest/v1.0/csprd03/xacml-rest-v1.0-csprd03.html

On Thu, Jun 23, 2016 at 3:42 PM, Omindu Rathnaweera  wrote:

> Good Work Manujith!
>
> Adding to this. Figure out a way to drop null values from the JSON
> response with Jackson level configurations. Also have a look at XACML JSON
> profile [1]. It will have guidelines on dealing with JSON inputs/outputs.
>
> [1] -
> http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/xacml-json-http-v1.0.html
>
> Regards,
> Omindu.
>
> On Thu, Jun 23, 2016 at 3:31 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi all,
>>
>> We had the mid-evaluation review, and I've summarized the key points
>> discussed here
>>
>> 1) Prioritize on the complete JSON implementation for all 5 services
>> methods
>> 2) Comply the service fully with XACML 3.0 REST specification (Read on
>> the spec and get a firm understanding on all key concepts)
>> 3) Leave the hard coded authenticators as it is for now
>> 4) Using custom client / server exception to be returned in a case of an
>> exception
>> 5) Follow the code quality guidelines (specially in the cases of improper
>> exception handling)
>>
>> Special thanks to everyone for their time in reviewing.
>>
>> Thank You,
>> Manujith
>>
>> On Sun, Jun 12, 2016 at 10:43 PM, Manujith Pallewatte <
>> manujith...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> After refactoring and reviewing code using above suggestions, I added a
>>> PR, which can be found at [1]
>>>
>>> Regards,
>>> Manujith
>>>
>>> [1] https://github.com/wso2/carbon-identity-framework/pull/282
>>>
>>> On Sat, Jun 11, 2016 at 12:52 PM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi Manuranga,

 I did referred to the guidelines, but was not successful in figuring
 out suitable end point names. So Pushpalanka suggested to take community's
 ideas in naming them. Any pointers as for which I can improve the names?
 According to the guide it says to identify the resources first
 Going on that, I identified the Policy Decision, Entitlement Attributes
 and Entitlements as resources, but since some resources have only one
 methods call in it, having a separate path seem redundant. And didnt follow
 much from there, please let me know your ideas on the resource
 identification

 Thank You
 Regards,
 Manujith

 On Sat, Jun 11, 2016 at 12:21 AM, Manuranga Perera 
 wrote:

> Hi Manujith,
>
> Please have a look at WSO2 REST API guideline [1]. This will help you
> to improve the URL nameing.
>
> [1] http://wso2.com/whitepapers/wso2-rest-apis-design-guidelines/
>
> On Thu, Jun 9, 2016 at 3:49 PM, Manujith Pallewatte <
> manujith...@gmail.com> wrote:
>
>> Hi Pushpalanka,
>>
>> Was confused in the PR procedure, and figured that I forgot to
>> initialize the github repo as you have mentioned in a previous message.
>> So the new location of the codebase is at [1]
>> Over the weekend, I'll fix any remaining issues and send the PR
>> For now I have used the wso2-codestyle given by Omindu and
>> reformatted the code
>> and added Findbug as well.
>>
>> Thank You
>> Manujith
>>
>> [1]
>> https://github.com/ManZzup/identity-framework/tree/master/components/entitlement/org.wso2.carbon.identity.entitlement.endpoint
>>
>> On Wed, Jun 8, 2016 at 11:35 AM, Pushpalanka Jayawardhana <
>> la...@wso2.com> wrote:
>>
>>>
>>>
>>> On Tue, Jun 7, 2016 at 11:01 AM, Manujith Pallewatte <
>>> manujith...@gmail.com> wrote:
>>>
 Hi all,

 Code is almost all refracted (apart from the part where
 authenticators are hard coded) and it' is available at [1]
 I have attached a readme so everyone can help with testing it. But
 there's still an issue remaining to debug with the *entitled-attribs
 *service call, that came up in preliminary testing by Omindu.

 Thank You Omindu, I will use the formatting configs and format the
 code asap. For now i added a gitignore as in the sample 

[Dev] How can we keep wait a docker container to start

[Tharindu Dharmarathna]

Hi All,

Is there any way to wait the start of containers which depends on other
container get started successfully.

I had tried with [1] . But it didn't get worked as well.

[1] - https://docs.docker.com/compose/startup-order/

-- 

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

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

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Kasun Bandara]

Hi all,

I could successfully run IS test suit with the upgraded Kernel 4.4.7- RC1.
Hence +1 for the release.

Thanks,
Kasun

On Mon, Jul 4, 2016 at 5:35 PM, Chamalee De Silva  wrote:

> P.S. Test done base done API Manager 2.0.0 beta-2
>
> On Mon, Jul 4, 2016 at 5:33 PM, Chamalee De Silva 
> wrote:
>
>> Hi,
>> I tested the kernel 4.4.7 RC1 with
>>
>> MySQL 5.6 and  5.7,
>> Oracle 11g,
>> PostgreSQL 9.3
>>
>> and they worked without an issue.
>>
>> [x] Stable - go ahead and release.
>>
>>
>>
>> Thanks,
>> Chamalee
>>
>> On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage 
>> wrote:
>>
>>> Hi,
>>>
>>> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
>>> issue related to this RC.
>>>
>>> *Note :* Feature repo not shown issue [1], introduced with kernel 4.4.6
>>> is observed. Hope this will be fixed in a future release.
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-15973
>>>
>>> Regards,
>>> Anupama
>>>
>>> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne 
>>> wrote:
>>>
 Hi,

 I tested the kernal with following databases and no issues observed.

 Test Area:
 Add/ Delete resource (inline text) and collection
 Add/Remove user and role

 Databases:
 mysql 5.5.
 mysql 5.7
 postgres 9.3
 oracle 12c

 Regards,
 Shashika

 Shashika Ubhayaratne
 Associate Technical Lead - QA
 WSO2 Inc: http://www.wso2.com/
 Mobile: *+94773383831*

 On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna 
 wrote:

> Hi all,
>
> I've tested the kernel with following databases and found no issues.
> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>
> [x] Stable - go ahead and release.
>
> Regards,
> Aruna
> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake 
> wrote:
>
>> Hi Devs,
>>
>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=13113
>>
>> Please download and test your products with kernel 4.4.7 RC1 and
>> vote. Vote will be open for 72 hours or as longer as needed.
>>
>> Source and binary distribution files:
>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>>
>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>>
>> Maven staging repository
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>>
>> The tag to be voted upon :
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you
>> Carbon Team​
>>
>>
>> *Jayanga Dissanayake*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.com/
>> lean . enterprise . middleware
>> email: jaya...@wso2.com
>> mobile: +94772207259
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.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


>>>
>>>
>>> --
>>> Anupama Pathirage
>>> Associate Technical Lead
>>> WSO2, Inc.  http://wso2.com/
>>> Email: anup...@wso2.com
>>> Mobile:+94 71 8273 979
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. .:http://wso2.com
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>> * *
>>
>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. .:http://wso2.com
>
> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>
> * *
>
> --
> You received this message because you are subscribed to the Google Groups
> "WSO2 Engineering Group" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to engineering-group+unsubscr...@wso2.com.
> For more options, 

Re: [Dev] "[ml][cep][gsoc-2016]Samoa vs Spark.Which is good for streaming?"

[Mahesh Dananjaya]

Hi Srinath,
Yes , Mahout has algorithms that can be used for streaming applications
such as SGD. They have listed their algorithms in [1]. And IMO in Samoa
they have implement some streaming applications based on those algorithms .
Seems to be they are still on it. you can see couple of such applications
in [2].i have been going through it recently.thank you.
regards,
Mahesh.

[1] http://mahout.apache.org/users/basics/algorithms.html
[2]
https://samoa.incubator.apache.org/documentation/SAMOA-and-Machine-Learning.html
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] "[ml][cep][gsoc-2016]Samoa vs Spark.Which is good for streaming?"

[Srinath Perera]

Does Mahout has any streaming algorithms? ( list you sent do not have
anything as I can tell)?

Also I think mahout needs hadoop, which has the same problem as needing
Spark.

--Srinath

On Mon, Jul 4, 2016 at 1:51 PM, Mahesh Dananjaya 
wrote:

> Hi Maheshakya,
> As i sent you before there are several options other than spark that we
> can used for our purpose [1]. I wen t through Samoa up to some extent. [2]
> Samoa is the streaming extension for ML framework Mahout [4] . Mahout is
> basically using hadoop framework and has lots of counterparts to apache
> spark. There are pros and cos of both platforms [5] . apache Mllib is based
> on the Apache spark [3] platform. Apache spark has its own streaming
> extension. as I see Samoa and Mahout has lots of options and algorithms for
> machine learning  and data analytics. And also Mahout is more advanced than
> the spark as i realized.So what we will gone a do. Samoa and mahout has
> lots options for streaming analytics.
> regards,
> Mahesh.
>
> [1] https://github.com/dananjayamahesh/awesome-machine-learning
> [2] https://samoa.incubator.apache.org/
> [3] http://spark.apache.org/
> [4] http://mahout.apache.org/users/basics/algorithms.html
> [5]
> http://stackoverflow.com/questions/23511459/what-is-the-difference-between-apache-mahout-and-apache-sparks-mllib
>



-- 

Srinath Perera, Ph.D.
   http://people.apache.org/~hemapani/
   http://srinathsview.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Chamalee De Silva]

P.S. Test done base done API Manager 2.0.0 beta-2

On Mon, Jul 4, 2016 at 5:33 PM, Chamalee De Silva  wrote:

> Hi,
> I tested the kernel 4.4.7 RC1 with
>
> MySQL 5.6 and  5.7,
> Oracle 11g,
> PostgreSQL 9.3
>
> and they worked without an issue.
>
> [x] Stable - go ahead and release.
>
>
>
> Thanks,
> Chamalee
>
> On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage 
> wrote:
>
>> Hi,
>>
>> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
>> issue related to this RC.
>>
>> *Note :* Feature repo not shown issue [1], introduced with kernel 4.4.6
>> is observed. Hope this will be fixed in a future release.
>>
>> [1] https://wso2.org/jira/browse/CARBON-15973
>>
>> Regards,
>> Anupama
>>
>> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne 
>> wrote:
>>
>>> Hi,
>>>
>>> I tested the kernal with following databases and no issues observed.
>>>
>>> Test Area:
>>> Add/ Delete resource (inline text) and collection
>>> Add/Remove user and role
>>>
>>> Databases:
>>> mysql 5.5.
>>> mysql 5.7
>>> postgres 9.3
>>> oracle 12c
>>>
>>> Regards,
>>> Shashika
>>>
>>> Shashika Ubhayaratne
>>> Associate Technical Lead - QA
>>> WSO2 Inc: http://www.wso2.com/
>>> Mobile: *+94773383831*
>>>
>>> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna 
>>> wrote:
>>>
 Hi all,

 I've tested the kernel with following databases and found no issues.
 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1

 [x] Stable - go ahead and release.

 Regards,
 Aruna
 On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake 
 wrote:

> Hi Devs,
>
> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=13113
>
> Please download and test your products with kernel 4.4.7 RC1 and vote.
> Vote will be open for 72 hours or as longer as needed.
>
> Source and binary distribution files:
> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>
> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>
> Maven staging repository
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>
> The tag to be voted upon :
> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you
> Carbon Team​
>
>
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --

 *Aruna Sujith Karunarathna *
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 71 9040362 | Work: +94 112145345
 Email: ar...@wso2.com | Web: www.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
>>>
>>>
>>
>>
>> --
>> Anupama Pathirage
>> Associate Technical Lead
>> WSO2, Inc.  http://wso2.com/
>> Email: anup...@wso2.com
>> Mobile:+94 71 8273 979
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. .:http://wso2.com
>
> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>
> * *
>



-- 
Thanks & Regards,

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

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*


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

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Chamalee De Silva]

Hi,
I tested the kernel 4.4.7 RC1 with

MySQL 5.6 and  5.7,
Oracle 11g,
PostgreSQL 9.3

and they worked without an issue.

[x] Stable - go ahead and release.



Thanks,
Chamalee

On Mon, Jul 4, 2016 at 5:09 PM, Anupama Pathirage  wrote:

> Hi,
>
> I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any
> issue related to this RC.
>
> *Note :* Feature repo not shown issue [1], introduced with kernel 4.4.6
> is observed. Hope this will be fixed in a future release.
>
> [1] https://wso2.org/jira/browse/CARBON-15973
>
> Regards,
> Anupama
>
> On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne 
> wrote:
>
>> Hi,
>>
>> I tested the kernal with following databases and no issues observed.
>>
>> Test Area:
>> Add/ Delete resource (inline text) and collection
>> Add/Remove user and role
>>
>> Databases:
>> mysql 5.5.
>> mysql 5.7
>> postgres 9.3
>> oracle 12c
>>
>> Regards,
>> Shashika
>>
>> Shashika Ubhayaratne
>> Associate Technical Lead - QA
>> WSO2 Inc: http://www.wso2.com/
>> Mobile: *+94773383831*
>>
>> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna 
>> wrote:
>>
>>> Hi all,
>>>
>>> I've tested the kernel with following databases and found no issues.
>>> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
>>> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>>>
>>> [x] Stable - go ahead and release.
>>>
>>> Regards,
>>> Aruna
>>> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake 
>>> wrote:
>>>
 Hi Devs,

 This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.

 This release fixes the following issues:
 https://wso2.org/jira/issues/?filter=13113

 Please download and test your products with kernel 4.4.7 RC1 and vote.
 Vote will be open for 72 hours or as longer as needed.

 Source and binary distribution files:
 https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip

 http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip

 Maven staging repository
 http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025

 The tag to be voted upon :
 https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1

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

 Thank you
 Carbon Team​


 *Jayanga Dissanayake*
 Associate Technical Lead
 WSO2 Inc. - http://wso2.com/
 lean . enterprise . middleware
 email: jaya...@wso2.com
 mobile: +94772207259

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


>>>
>>>
>>> --
>>>
>>> *Aruna Sujith Karunarathna *
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 71 9040362 | Work: +94 112145345
>>> Email: ar...@wso2.com | Web: www.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
>>
>>
>
>
> --
> Anupama Pathirage
> Associate Technical Lead
> WSO2, Inc.  http://wso2.com/
> Email: anup...@wso2.com
> Mobile:+94 71 8273 979
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,

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

Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*


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

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Anupama Pathirage]

Hi,

I tested DSS 3.5.1 Snapshot with kernel 4.4.7 RC1 and didn't find any issue
related to this RC.

*Note :* Feature repo not shown issue [1], introduced with kernel 4.4.6 is
observed. Hope this will be fixed in a future release.

[1] https://wso2.org/jira/browse/CARBON-15973

Regards,
Anupama

On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne 
wrote:

> Hi,
>
> I tested the kernal with following databases and no issues observed.
>
> Test Area:
> Add/ Delete resource (inline text) and collection
> Add/Remove user and role
>
> Databases:
> mysql 5.5.
> mysql 5.7
> postgres 9.3
> oracle 12c
>
> Regards,
> Shashika
>
> Shashika Ubhayaratne
> Associate Technical Lead - QA
> WSO2 Inc: http://www.wso2.com/
> Mobile: *+94773383831*
>
> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna  wrote:
>
>> Hi all,
>>
>> I've tested the kernel with following databases and found no issues.
>> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
>> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>>
>> [x] Stable - go ahead and release.
>>
>> Regards,
>> Aruna
>> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=13113
>>>
>>> Please download and test your products with kernel 4.4.7 RC1 and vote.
>>> Vote will be open for 72 hours or as longer as needed.
>>>
>>> Source and binary distribution files:
>>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>>>
>>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>>>
>>> Maven staging repository
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>>>
>>> The tag to be voted upon :
>>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thank you
>>> Carbon Team​
>>>
>>>
>>> *Jayanga Dissanayake*
>>> Associate Technical Lead
>>> WSO2 Inc. - http://wso2.com/
>>> lean . enterprise . middleware
>>> email: jaya...@wso2.com
>>> mobile: +94772207259
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.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
>
>


-- 
Anupama Pathirage
Associate Technical Lead
WSO2, Inc.  http://wso2.com/
Email: anup...@wso2.com
Mobile:+94 71 8273 979
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Fazlan Nazeem]

Hi all,

I have tested the User/Registry with 4.4.7 kernel for the following
databases.

   - Mssql
   - DB2
   - Informix (LDAP user store)

[x] Stable - go ahead and release.

On Mon, Jul 4, 2016 at 4:58 PM, Shashika Ubhayaratne 
wrote:

> Hi,
>
> I tested the kernal with following databases and no issues observed.
>
> Test Area:
> Add/ Delete resource (inline text) and collection
> Add/Remove user and role
>
> Databases:
> mysql 5.5.
> mysql 5.7
> postgres 9.3
> oracle 12c
>
> Regards,
> Shashika
>
> Shashika Ubhayaratne
> Associate Technical Lead - QA
> WSO2 Inc: http://www.wso2.com/
> Mobile: *+94773383831*
>
> On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna  wrote:
>
>> Hi all,
>>
>> I've tested the kernel with following databases and found no issues.
>> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
>> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>>
>> [x] Stable - go ahead and release.
>>
>> Regards,
>> Aruna
>> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=13113
>>>
>>> Please download and test your products with kernel 4.4.7 RC1 and vote.
>>> Vote will be open for 72 hours or as longer as needed.
>>>
>>> Source and binary distribution files:
>>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>>>
>>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>>>
>>> Maven staging repository
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>>>
>>> The tag to be voted upon :
>>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>> Thank you
>>> Carbon Team​
>>>
>>>
>>> *Jayanga Dissanayake*
>>> Associate Technical Lead
>>> WSO2 Inc. - http://wso2.com/
>>> lean . enterprise . middleware
>>> email: jaya...@wso2.com
>>> mobile: +94772207259
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Aruna Sujith Karunarathna *
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 9040362 | Work: +94 112145345
>> Email: ar...@wso2.com | Web: www.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
>
>


-- 
Thanks & Regards,

Fazlan Nazeem

*Software Engineer*

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

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Shashika Ubhayaratne]

Hi,

I tested the kernal with following databases and no issues observed.

Test Area:
Add/ Delete resource (inline text) and collection
Add/Remove user and role

Databases:
mysql 5.5.
mysql 5.7
postgres 9.3
oracle 12c

Regards,
Shashika

Shashika Ubhayaratne
Associate Technical Lead - QA
WSO2 Inc: http://www.wso2.com/
Mobile: *+94773383831*

On Mon, Jul 4, 2016 at 3:50 PM, Aruna Karunarathna  wrote:

> Hi all,
>
> I've tested the kernel with following databases and found no issues.
> 1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
> 2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1
>
> [x] Stable - go ahead and release.
>
> Regards,
> Aruna
> On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake 
> wrote:
>
>> Hi Devs,
>>
>> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=13113
>>
>> Please download and test your products with kernel 4.4.7 RC1 and vote.
>> Vote will be open for 72 hours or as longer as needed.
>>
>> Source and binary distribution files:
>> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>>
>> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>>
>> Maven staging repository
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>>
>> The tag to be voted upon :
>> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>> Thank you
>> Carbon Team​
>>
>>
>> *Jayanga Dissanayake*
>> Associate Technical Lead
>> WSO2 Inc. - http://wso2.com/
>> lean . enterprise . middleware
>> email: jaya...@wso2.com
>> mobile: +94772207259
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> *Aruna Sujith Karunarathna *
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.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

[Dev] [Dockerfile] WSO2IS docker image build fails due to missing file

[Udara Liyanage]

Hi,

WSO2 IS as KM docker image build fails due to a missing file. This file is
not found even in original pack.

bash build.sh -v 5.1.0 -s mesos -r puppet

172.17.0.3 - - [04/Jul/2016 06:21:27] "GET
/modules/wso2is_km/files/wso2is_km-5.1.0/modules/ws/ HTTP/1.1" 200 -
2016-07-04 10:21:27 URL:
http://172.17.0.1:8002/modules/wso2is_km/files/wso2is_km-5.1.0/modules/ws/
[320/320] ->
"modules/wso2is_km/files/wso2is_km-5.1.0/modules/ws/index.html" [1]
172.17.0.3 - - [04/Jul/2016 06:21:27] code 404, message File not found
172.17.0.3 - - [04/Jul/2016 06:21:27] "GET
/modules/wso2is_km/files/wso2is_km-5.1.0/css/is-docs.css HTTP/1.1" 404 -
http://172.17.0.1:8002/modules/wso2is_km/files/wso2is_km-5.1.0/css/is-docs.css
:
*2016-07-04 10:21:27 ERROR 404: File not found.*
172.17.0.3 - - [04/Jul/2016 06:21:27] "GET /mod
ERROR: Docker image
cdtsdvo108p.rxcorp.com:8443/wso2/devl/wso2is_km-mesos:5.1.0 creation failed

-- 

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

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.7 RC1

[Aruna Karunarathna]

Hi all,

I've tested the kernel with following databases and found no issues.
1. mysql_cluster - Server version: 5.6.29-ndb-7.4.11-cluster-gpl
2. mariadb 5.5.49-MariaDB-1ubuntu0.14.04.1

[x] Stable - go ahead and release.

Regards,
Aruna
On Fri, Jul 1, 2016 at 6:20 PM, Jayanga Dissanayake 
wrote:

> Hi Devs,
>
> This is the 1st release candidate of WSO2 Carbon Kernel 4.4.7.
>
> This release fixes the following issues:
> https://wso2.org/jira/issues/?filter=13113
>
> Please download and test your products with kernel 4.4.7 RC1 and vote.
> Vote will be open for 72 hours or as longer as needed.
>
> Source and binary distribution files:
> https://github.com/wso2/carbon-kernel/archive/v4.4.7-rc1.zip
>
> http://svn.wso2.org/repos/wso2/people/jayanga/wso2carbon-4.4.7-rc1/wso2carbon-4.4.7-rc1.zip
>
> Maven staging repository
> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-1025
>
> The tag to be voted upon :
> https://github.com/wso2/carbon-kernel/releases/tag/v4.4.7-rc1
>
> [ ] Broken - do not release (explain why)
> [ ] Stable - go ahead and release
>
> Thank you
> Carbon Team​
>
>
> *Jayanga Dissanayake*
> Associate Technical Lead
> WSO2 Inc. - http://wso2.com/
> lean . enterprise . middleware
> email: jaya...@wso2.com
> mobile: +94772207259
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

*Aruna Sujith Karunarathna *
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 9040362 | Work: +94 112145345
Email: ar...@wso2.com | Web: www.wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cannot log into management console when disk usage is at 100%

[Grainier Perera]

Current audit.log/wso2carbon.log only seems to have logs after the
incident. Earlier logs (wso2carbon.log.2016-07-03) seems to ends with;

> org.apache.qpid.pTID: [-1234] [] [2016-07-03 00:53:07,213] ERROR
> {org.wso2.carbon.registry.core.dataaccess.TransactionManager} -  Failed to
> start new registry transaction.
> {org.wso2.carbon.registry.core.dataaccess.TransactionManager}
> org.h2.jdbc.JdbcSQLException: IO Exception: "java.io.IOException: No space
> left on device";
> "/home/ladmin/cloud_setup/wso2das-3.0.1/repository/database/WSO2CARBON_DB.h2.db"
> [90031-140]

May be it couldn't log the incident, since there's No space left on device.

On Mon, Jul 4, 2016 at 2:39 PM, Dulanja Liyanage  wrote:

> What was getting printed on the logs?
>
> Thanks,
> Dulanja
>
> On Mon, Jul 4, 2016 at 2:11 PM, Grainier Perera  wrote:
>
>> Hi All,
>>
>> I was trying to access Carbon Management Console (of DAS 3.0.1) with
>> correct credentials and it kept returning "Login failed! Please recheck the
>> username and password and try again.". Then I checked disk usage of that
>> node and it was at 100% (/dev/sda1 29G 29G 0 100% /). After cleaning some
>> logs and artifacts, I tried to log back in with the same credentials, and
>> this time it worked. Is this the expected behavior?
>>
>> Regards,
>> --
>> Grainier Perera
>> Software Engineer
>> Mobile : +94716122384
>> WSO2 Inc. | http://wso2.com
>> lean.enterprise.middleware
>>
>
>
>
> --
> Thanks & Regards,
> Dulanja Liyanage
> Lead, Platform Security Team
> WSO2 Inc.
>



-- 
Grainier Perera
Software Engineer
Mobile : +94716122384
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Manjula Rathnayake]

Hi Nisala and Kasun,

Great. This will help us to include AS6 as a jaggery runtime in AppCloud.

thank you.

On Mon, Jul 4, 2016 at 3:04 PM, KasunG Gajasinghe  wrote:

>
>
> On Mon, Jul 4, 2016 at 1:48 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi Manjula,
>>
>> Yes.Jaggery support will be inbuilt into the server with the release of
>> AS-6.0.0 next milestone. This email and documentation is provided to inform
>> the procedure of running jaggery apps in a pure tomcat server, not in the
>> AS-6.0.0. I will update the finalized documentation and configuration
>> details for AS-6.0.0 in a separate mail thread, once we finished the
>> fine-tuning process.
>>
>> Thanks,
>> Nisala
>>
>> On Mon, Jul 4, 2016 at 1:39 PM, Manjula Rathnayake 
>> wrote:
>>
>>> Hi all,
>>>
>>> IIUC, when we release the next AS-6.0.0 milestone, jaggery support is
>>> inbuilt into the server. And users do not need to follow above instructions
>>> to copy jars etc. Please correct If it is not.
>>>
>>
> Yes, that's the case. So, we need separate documentation on how to deploy
> Jaggery apps in AS6 as well.
>
>
>>
>>> thank you.
>>>
>>> On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran 
>>> wrote:
>>>
 Hi,

 Anyhow ultimately when all the carbon products move to AS 6.0 based
 platform, we can merge all those into one.

 Thanks,
 Sinthuja.

 On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara 
 wrote:

> Hi Kasun,
>
> Yes.We can do a performance round. Currently we manage the Tomcat
> Jaggery/ AS6 support code base under a new branch [1] in our jaggery
> repository. Current jaggery is based on tomcat version 7 and Tomcat 
> Jaggery
> implementation is based on tomcat version 8. So there are some api changes
> in the jaggery level. So it is difficult to manage these codebases in same
> place.
>
> Thanks,
> Nisala
>
> On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe 
> wrote:
>
>>
>> Good work Nisala.
>>
>> Can we also do a performance round to see whether there are any perf
>> gains when running Jaggery apps in vanilla Tomcat/AS6?
>>
>> How are you going to manage the codebase for Carbon vs Tomcat Jaggery
>> support? Better if we can maintain it in the same place.
>>
>> On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is an update regarding the feature 'Provide Support to run
>>> Jaggery apps in Tomcat Server'.
>>>
>>> At present Jaggery scripts can only be executed in a jaggery server.
>>> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is 
>>> the
>>> Runtime Environment that hosts Jaggery applications. The goal of this
>>> feature is to provide support to run jaggery apps in a pure tomcat 
>>> server
>>> without any modifications to the jaggery apps.This will enable 
>>> developers
>>> to write Jaggery scripts and directly deploy them in apache tomcat 
>>> server.
>>> So this will improve the flexibility of the jaggery apps.
>>>
>>> This is an extension for the Apache tomcat 8 to run the jaggery app
>>> without modifying it. Although this is implemented as a requirement of 
>>> WSO2
>>> Application Server 6, Users who want to run jaggery apps without jaggery
>>> server, can use this feature to run their jaggery apps in Apache tomcat
>>> server.
>>>
>>> I have attached the documentation and sample jaggery with this
>>> email. Please find these attachments and relevant jaggery branch 
>>> here[1].
>>> Please feel free to ask any questions.
>>>
>>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>>
>>> Thanks,
>>> Nisala
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>>
>>
>>
>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Sinthuja Rajendran*
 Technical Lead
 WSO2, Inc.:http://wso2.com

 Blog: http://sinthu-rajan.blogspot.com/
 Mobile: +94774273955

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

[KasunG Gajasinghe]

On Mon, Jul 4, 2016 at 1:48 PM, Nisala Nanayakkara  wrote:

> Hi Manjula,
>
> Yes.Jaggery support will be inbuilt into the server with the release of
> AS-6.0.0 next milestone. This email and documentation is provided to inform
> the procedure of running jaggery apps in a pure tomcat server, not in the
> AS-6.0.0. I will update the finalized documentation and configuration
> details for AS-6.0.0 in a separate mail thread, once we finished the
> fine-tuning process.
>
> Thanks,
> Nisala
>
> On Mon, Jul 4, 2016 at 1:39 PM, Manjula Rathnayake 
> wrote:
>
>> Hi all,
>>
>> IIUC, when we release the next AS-6.0.0 milestone, jaggery support is
>> inbuilt into the server. And users do not need to follow above instructions
>> to copy jars etc. Please correct If it is not.
>>
>
Yes, that's the case. So, we need separate documentation on how to deploy
Jaggery apps in AS6 as well.


>
>> thank you.
>>
>> On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran 
>> wrote:
>>
>>> Hi,
>>>
>>> Anyhow ultimately when all the carbon products move to AS 6.0 based
>>> platform, we can merge all those into one.
>>>
>>> Thanks,
>>> Sinthuja.
>>>
>>> On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi Kasun,

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

 Thanks,
 Nisala

 On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe 
 wrote:

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



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

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


>>>
>>>
>>> --
>>> *Sinthuja Rajendran*
>>> Technical Lead
>>> WSO2, Inc.:http://wso2.com
>>>
>>> Blog: http://sinthu-rajan.blogspot.com/
>>> Mobile: +94774273955
>>>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> architect...@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> Manjula Rathnayaka
>> Associate Technical Lead
>> WSO2, Inc.
>> Mobile:+94 77 743 1987
>>
>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> 

Re: [Dev] Cannot log into management console when disk usage is at 100%

[Dulanja Liyanage]

What was getting printed on the logs?

Thanks,
Dulanja

On Mon, Jul 4, 2016 at 2:11 PM, Grainier Perera  wrote:

> Hi All,
>
> I was trying to access Carbon Management Console (of DAS 3.0.1) with
> correct credentials and it kept returning "Login failed! Please recheck the
> username and password and try again.". Then I checked disk usage of that
> node and it was at 100% (/dev/sda1 29G 29G 0 100% /). After cleaning some
> logs and artifacts, I tried to log back in with the same credentials, and
> this time it worked. Is this the expected behavior?
>
> Regards,
> --
> Grainier Perera
> Software Engineer
> Mobile : +94716122384
> WSO2 Inc. | http://wso2.com
> lean.enterprise.middleware
>



-- 
Thanks & Regards,
Dulanja Liyanage
Lead, Platform Security Team
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM 2.0] [clarification] [api manager xml] all server url's local ip has hard coded as 'localhost'

[Bhathiya Jayasekara]

Yes, we had to do this after kernel upgrade.

Thanks,
Bhathiya

On Mon, Jul 4, 2016 at 2:15 PM, Kavitha Subramaniyam 
wrote:

> Hi apim team,
>  I have observed $subject in 17th pack & beta2 pack[1] and we want to make
> sure whether this change has been done purposely since earlier packs had
> parameter reference for the server url.
> Please confirm..
>
> [1] https://localhost:
> ${mgt.transport.https.port}${carbon.context}services/
>
>
> Thanks,
> --
> Kavitha.S
> *Software Engineer -QA*
> Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
> kavi...@wso2.com 
>



-- 
*Bhathiya Jayasekara*
*Senior Software Engineer,*
*WSO2 inc., http://wso2.com *

*Phone: +94715478185 <%2B94715478185>*
*LinkedIn: http://www.linkedin.com/in/bhathiyaj
*
*Twitter: https://twitter.com/bhathiyax *
*Blog: http://movingaheadblog.blogspot.com
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [APIM 2.0] [clarification] [api manager xml] all server url's local ip has hard coded as 'localhost'

[Kavitha Subramaniyam]

Hi apim team,
 I have observed $subject in 17th pack & beta2 pack[1] and we want to make
sure whether this change has been done purposely since earlier packs had
parameter reference for the server url.
Please confirm..

[1] https://localhost:
${mgt.transport.https.port}${carbon.context}services/


Thanks,
-- 
Kavitha.S
*Software Engineer -QA*
Mobile : +94 (0) 771538811 <%2B94%20%280%29%20773%20451194>
kavi...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Cannot log into management console when disk usage is at 100%

[Grainier Perera]

Hi All,

I was trying to access Carbon Management Console (of DAS 3.0.1) with
correct credentials and it kept returning "Login failed! Please recheck the
username and password and try again.". Then I checked disk usage of that
node and it was at 100% (/dev/sda1 29G 29G 0 100% /). After cleaning some
logs and artifacts, I tried to log back in with the same credentials, and
this time it worked. Is this the expected behavior?

Regards,
-- 
Grainier Perera
Software Engineer
Mobile : +94716122384
WSO2 Inc. | http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] "[ml][cep][gsoc-2016]Samoa vs Spark.Which is good for streaming?"

[Mahesh Dananjaya]

Hi Maheshakya,
As i sent you before there are several options other than spark that we can
used for our purpose [1]. I wen t through Samoa up to some extent. [2]
Samoa is the streaming extension for ML framework Mahout [4] . Mahout is
basically using hadoop framework and has lots of counterparts to apache
spark. There are pros and cos of both platforms [5] . apache Mllib is based
on the Apache spark [3] platform. Apache spark has its own streaming
extension. as I see Samoa and Mahout has lots of options and algorithms for
machine learning  and data analytics. And also Mahout is more advanced than
the spark as i realized.So what we will gone a do. Samoa and mahout has
lots options for streaming analytics.
regards,
Mahesh.

[1] https://github.com/dananjayamahesh/awesome-machine-learning
[2] https://samoa.incubator.apache.org/
[3] http://spark.apache.org/
[4] http://mahout.apache.org/users/basics/algorithms.html
[5]
http://stackoverflow.com/questions/23511459/what-is-the-difference-between-apache-mahout-and-apache-sparks-mllib
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Nisala Nanayakkara]

Hi Manjula,

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

Thanks,
Nisala

On Mon, Jul 4, 2016 at 1:39 PM, Manjula Rathnayake 
wrote:

> Hi all,
>
> IIUC, when we release the next AS-6.0.0 milestone, jaggery support is
> inbuilt into the server. And users do not need to follow above instructions
> to copy jars etc. Please correct If it is not.
>
> thank you.
>
> On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran 
> wrote:
>
>> Hi,
>>
>> Anyhow ultimately when all the carbon products move to AS 6.0 based
>> platform, we can merge all those into one.
>>
>> Thanks,
>> Sinthuja.
>>
>> On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi Kasun,
>>>
>>> Yes.We can do a performance round. Currently we manage the Tomcat
>>> Jaggery/ AS6 support code base under a new branch [1] in our jaggery
>>> repository. Current jaggery is based on tomcat version 7 and Tomcat Jaggery
>>> implementation is based on tomcat version 8. So there are some api changes
>>> in the jaggery level. So it is difficult to manage these codebases in same
>>> place.
>>>
>>> Thanks,
>>> Nisala
>>>
>>> On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe 
>>> wrote:
>>>

 Good work Nisala.

 Can we also do a performance round to see whether there are any perf
 gains when running Jaggery apps in vanilla Tomcat/AS6?

 How are you going to manage the codebase for Carbon vs Tomcat Jaggery
 support? Better if we can maintain it in the same place.

 On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara 
 wrote:

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


 --

 *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
 email: kasung AT spamfree wso2.com
 linked-in: http://lk.linkedin.com/in/gajasinghe
 blog: http://kasunbg.org



>>>
>>>
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Sinthuja Rajendran*
>> Technical Lead
>> WSO2, Inc.:http://wso2.com
>>
>> Blog: http://sinthu-rajan.blogspot.com/
>> Mobile: +94774273955
>>
>>
>>
>> ___
>> Architecture mailing list
>> architect...@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Manjula Rathnayaka
> Associate Technical Lead
> WSO2, Inc.
> Mobile:+94 77 743 1987
>



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

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

[Manjula Rathnayake]

Hi all,

IIUC, when we release the next AS-6.0.0 milestone, jaggery support is
inbuilt into the server. And users do not need to follow above instructions
to copy jars etc. Please correct If it is not.

thank you.

On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran 
wrote:

> Hi,
>
> Anyhow ultimately when all the carbon products move to AS 6.0 based
> platform, we can merge all those into one.
>
> Thanks,
> Sinthuja.
>
> On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara 
> wrote:
>
>> Hi Kasun,
>>
>> Yes.We can do a performance round. Currently we manage the Tomcat
>> Jaggery/ AS6 support code base under a new branch [1] in our jaggery
>> repository. Current jaggery is based on tomcat version 7 and Tomcat Jaggery
>> implementation is based on tomcat version 8. So there are some api changes
>> in the jaggery level. So it is difficult to manage these codebases in same
>> place.
>>
>> Thanks,
>> Nisala
>>
>> On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe 
>> wrote:
>>
>>>
>>> Good work Nisala.
>>>
>>> Can we also do a performance round to see whether there are any perf
>>> gains when running Jaggery apps in vanilla Tomcat/AS6?
>>>
>>> How are you going to manage the codebase for Carbon vs Tomcat Jaggery
>>> support? Better if we can maintain it in the same place.
>>>
>>> On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara 
>>> wrote:
>>>
 Hi all,

 This is an update regarding the feature 'Provide Support to run Jaggery
 apps in Tomcat Server'.

 At present Jaggery scripts can only be executed in a jaggery server.
 Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is the
 Runtime Environment that hosts Jaggery applications. The goal of this
 feature is to provide support to run jaggery apps in a pure tomcat server
 without any modifications to the jaggery apps.This will enable developers
 to write Jaggery scripts and directly deploy them in apache tomcat server.
 So this will improve the flexibility of the jaggery apps.

 This is an extension for the Apache tomcat 8 to run the jaggery app
 without modifying it. Although this is implemented as a requirement of WSO2
 Application Server 6, Users who want to run jaggery apps without jaggery
 server, can use this feature to run their jaggery apps in Apache tomcat
 server.

 I have attached the documentation and sample jaggery with this email.
 Please find these attachments and relevant jaggery branch here[1]. Please
 feel free to ask any questions.

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

 Thanks,
 Nisala

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

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


>>>
>>>
>>> --
>>>
>>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>>> email: kasung AT spamfree wso2.com
>>> linked-in: http://lk.linkedin.com/in/gajasinghe
>>> blog: http://kasunbg.org
>>>
>>>
>>>
>>
>>
>>
>> --
>> *Nisala Niroshana Nanayakkara,*
>> Software Engineer
>> Mobile:(+94)717600022
>> WSO2 Inc., http://wso2.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Sinthuja Rajendran*
> Technical Lead
> WSO2, Inc.:http://wso2.com
>
> Blog: http://sinthu-rajan.blogspot.com/
> Mobile: +94774273955
>
>
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Manjula Rathnayaka
Associate Technical Lead
WSO2, Inc.
Mobile:+94 77 743 1987
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Scope based authorization for CDMF

[Chathura Dilan]

+1 Instead of having users:add, users:edit, users:view and users:delete we
can have all of them under users:manage scope.

But when designing the scopes it not possible to consider all the business
functionalities so we can provide basic functionalities such as
users:manage, roles:view, roles:manage.

When it comes to UI, when managing users, viewing roles is also needed. In
that case we need to combine two or more scopes and create a special UI
permission like 'manage_users'

having separate UI permissions make them easy to authorize the UI pages as
well as focuses on the real business functionality rather than depending on
BE.


On Mon, Jul 4, 2016 at 12:20 PM, Prabath Abeysekera 
wrote:

> IMO, scopes for any application should be designed and implemented taking
> the end-to-end business functionalities into account, rather than focussing
> on different discrete pieces of small functional units such as UI, BE, etc.
> For instance, if some user is authorized to "manage users", the underlying
> scopes that make it possible to that particular user to perform the
> intended task, should be shared across the UI as well as the BE. In other
> words, the same scope that lets the user access the BE resources associated
> with managing users, can be re-used to render the associated UI elements as
> well. That way, not only it makes us avoid overly redundant scopes, which -
> if not managed properly - can be a headache, but also helps us make things
> much more simplified.
>
> Cheers,
> Prabath
>
> On Mon, Jul 4, 2016 at 12:00 PM, Chathura Dilan 
> wrote:
>
>> +Dev
>>
>> For the UI
>>
>> IMO, UI should have their own permissions. and they should be associated
>> with scopes
>>
>> Such as
>>
>> *UI Permission scopes*
>> manage_user users:add, users:edit, users:delete, users:view,
>> roles:view
>> view_user   users:view
>>
>> These UI permissions can to be assigned from the permission tree to a
>> role. Once the permission is assigned to a role, the scopes associated with
>> the permission also assigned to that role automatically.
>>
>> For that we can reduce the complexity of assigning the UI permission.
>> WDYT?
>>
>>
>>
>>
>> On Mon, Jul 4, 2016 at 10:16 AM, Milan Perera  wrote:
>>
>>> Sure, will schedule it in the morning.
>>>
>>> On Mon, Jul 4, 2016 at 6:27 AM, Prabath Abeysekera 
>>> wrote:
>>>
 Awesome! Shall we review this in the morn and be done with it?

 Cheers,
 Prabath


 On Monday, July 4, 2016, Milan Perera  wrote:

> Hi all,
>
> I've done the $subject and its still in my fork [1]. Let's have a
> review on that and then I will merge.
> I've tested this implementation with JDBC scope validator and it works
> fine.
>
> Currently I just only changed the devicemgt-api and have to do
> necessary changes to other apis as well.
>
> [1]
> https://github.com/milanperera/carbon-device-mgt/commit/49623a4693dcbd35f6b5305c3e29d31254fcb4ce
>
>
> Regards,
>
> --
> *Milan Perera *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
> Email: mi...@wso2.com | Web: www.wso2.com
> 
>


 --
 Prabath Abeysekara
 Technical Lead
 WSO2 Inc.
 Email: praba...@wso2.com
 Mobile: +94774171471


>>>
>>>
>>> --
>>> *Milan Perera *| Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>>> Email: mi...@wso2.com  | Web: www.wso2.com
>>> 
>>>
>>
>>
>>
>> --
>> Regards,
>>
>> Chatura Dilan Perera
>> *Associate Tech Lead** - WSO2 Inc.*
>> www.dilan.me
>>
>
>
>
> --
> Prabath Abeysekara
> Technical Lead
> WSO2 Inc.
> Email: praba...@wso2.com
> Mobile: +94774171471
>



-- 
Regards,

Chatura Dilan Perera
*Associate Tech Lead** - WSO2 Inc.*
www.dilan.me
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[Sinthuja Ragendran]

Hi,

Anyhow ultimately when all the carbon products move to AS 6.0 based
platform, we can merge all those into one.

Thanks,
Sinthuja.

On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara  wrote:

> Hi Kasun,
>
> Yes.We can do a performance round. Currently we manage the Tomcat Jaggery/
> AS6 support code base under a new branch [1] in our jaggery repository.
> Current jaggery is based on tomcat version 7 and Tomcat Jaggery
> implementation is based on tomcat version 8. So there are some api changes
> in the jaggery level. So it is difficult to manage these codebases in same
> place.
>
> Thanks,
> Nisala
>
> On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe  wrote:
>
>>
>> Good work Nisala.
>>
>> Can we also do a performance round to see whether there are any perf
>> gains when running Jaggery apps in vanilla Tomcat/AS6?
>>
>> How are you going to manage the codebase for Carbon vs Tomcat Jaggery
>> support? Better if we can maintain it in the same place.
>>
>> On Sat, Jul 2, 2016 at 12:51 PM, Nisala Nanayakkara 
>> wrote:
>>
>>> Hi all,
>>>
>>> This is an update regarding the feature 'Provide Support to run Jaggery
>>> apps in Tomcat Server'.
>>>
>>> At present Jaggery scripts can only be executed in a jaggery server.
>>> Because Jaggery Server which is powered by WSO2 carbon OSGi Runtime, is the
>>> Runtime Environment that hosts Jaggery applications. The goal of this
>>> feature is to provide support to run jaggery apps in a pure tomcat server
>>> without any modifications to the jaggery apps.This will enable developers
>>> to write Jaggery scripts and directly deploy them in apache tomcat server.
>>> So this will improve the flexibility of the jaggery apps.
>>>
>>> This is an extension for the Apache tomcat 8 to run the jaggery app
>>> without modifying it. Although this is implemented as a requirement of WSO2
>>> Application Server 6, Users who want to run jaggery apps without jaggery
>>> server, can use this feature to run their jaggery apps in Apache tomcat
>>> server.
>>>
>>> I have attached the documentation and sample jaggery with this email.
>>> Please find these attachments and relevant jaggery branch here[1]. Please
>>> feel free to ask any questions.
>>>
>>> [1] - https://github.com/wso2/jaggery/tree/tomcat-8.0.x-jaggery
>>>
>>> Thanks,
>>> Nisala
>>>
>>> --
>>> *Nisala Niroshana Nanayakkara,*
>>> Software Engineer
>>> Mobile:(+94)717600022
>>> WSO2 Inc., http://wso2.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc.
>> email: kasung AT spamfree wso2.com
>> linked-in: http://lk.linkedin.com/in/gajasinghe
>> blog: http://kasunbg.org
>>
>>
>>
>
>
>
> --
> *Nisala Niroshana Nanayakkara,*
> Software Engineer
> Mobile:(+94)717600022
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Sinthuja Rajendran*
Technical Lead
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] log user events to audit.log file via Jaggery block layer

[Danushka Fernando]

Shall we have two logs prior to action and after success or failure of the
action.
And I am suggesting to have logs like
User XXX triggered action YYY
Action YYY triggered by User XXX successfully completed
Error occurred while processing Action YYY triggered by User XXX

WDYT?

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

On Mon, Jul 4, 2016 at 10:57 AM, Amalka Subasinghe  wrote:

> Added above mentioned code block to the router.jag file
> Then the logs will be printed as...
>
> [2016-07-04 10:48:00,050]  INFO -  User : ad...@wso2.com, Action :
> createDatabaseAndAttachUser
> [2016-07-04 10:48:06,300]  INFO -  User : ad...@wso2.com, Action :
> dropDatabase
> [2016-07-04 10:48:08,406]  INFO -  User : ad...@wso2.com, Action :
> dropDatabase
> [2016-07-04 10:48:15,675]  INFO -  User : ad...@wso2.com, Action :
> createDatabaseAndAttachUser
> [2016-07-04 10:48:24,817]  INFO -  User : ad...@wso2.com, Action :
> createDatabaseUser
>
>
>
> On Sun, Jul 3, 2016 at 4:17 PM, Mahesh Chinthaka  wrote:
>
>> Hi Amalka,
>>
>> All the requests/actions go through it (router.jag).
>>
>>
>>
>> On Sun, Jul 3, 2016 at 7:16 AM, Amalka Subasinghe 
>> wrote:
>>
>>> Hi,
>>>
>>> We can log adding following to the jaggery.
>>>
>>> var audit = org.wso2.carbon.CarbonConstants.AUDIT_LOG;
>>> audit.info("User : " + jagg.getUser() + ", Action : " +  action);
>>>
>>> Here. I want to log who is the user logged in and what action he called.
>>> Would it be ok to add this code to the router jag in app cloud? As I
>>> know all requests/actions go through it. am I right?
>>>
>>> Thanks
>>> Amalka
>>>
>>> On Fri, Jul 1, 2016 at 12:13 PM, Amalka Subasinghe 
>>> wrote:
>>>
 Hi,

 I have a Jaggery app deployed in WSO2AS, I want to log user activities
 via block layer to a separate file (to audit.log).
 Please help.

 Thanks
 Amalka


>>>
>>>
>>> --
>>> Amalka Subasinghe
>>>
>>> WSO2 Inc.
>>> Mobile: +94 77 9401267
>>>
>>
>>
>>
>> --
>> *Mahesh Chinthaka Vidanagama* | Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 63 63 083 | Work: +94 112 145 345
>> Email: mahe...@wso2.com | Web: www.wso2.com
>>
>
>
>
> --
> Amalka Subasinghe
>
> WSO2 Inc.
> Mobile: +94 77 9401267
>
> ___
> 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] Provide Support to run Jaggery apps in Tomcat Server

[Nisala Nanayakkara]

Hi Kasun,

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

Thanks,
Nisala

On Sun, Jul 3, 2016 at 9:01 AM, KasunG Gajasinghe  wrote:

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



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

Re: [Dev] DAS event receiving gets blocked under high load in minimum HA

[Supun Sethunga]

Execution plan:

[1]
https://github.com/wso2/analytics-esb/blob/master/features/org.wso2.analytics.esb.feature/src/main/capp/realtime/ESBAnalyticsExecutionPlan/ESBAnalytics.siddhiql

Thanks,
Supun

On Mon, Jul 4, 2016 at 12:30 PM, Supun Sethunga  wrote:

> Attached the thread dump.
>
> [1] is the execution plan
>
>
> On Fri, Jul 1, 2016 at 7:37 PM, Sriskandarajah Suhothayan 
> wrote:
>
>> Can you reproduce this and get a thread dump & share that with us when it
>> got stuck.
>>
>> Regards
>> Suho
>>
>> On Fri, Jul 1, 2016 at 7:25 PM, Supun Sethunga  wrote:
>>
>>> Hi,
>>>
>>> While running a load test with the latest analytics-esb, noticed that
>>> the event receiving gets blocked after some time (within 15 mins), under
>>> high load. This was a minimum HA cluster, and we persist only per-second
>>> stats. Until the receiving got blocked, events received at a throughput of
>>> around 9000.  Also, I couldn't reproduce this in a single node setup.
>>>
>>> Since there weren't any changes to execution plans, I tried reverting
>>> the siddhi (core, query-api, query-compiler) to an older build (Jun 23,
>>> 2016), and re-ran the test, and did not encounter the issue...
>>>
>>> Thanks,
>>> Supun
>>>
>>> --
>>> *Supun Sethunga*
>>> Senior Software Engineer
>>> WSO2, Inc.
>>> http://wso2.com/
>>> lean | enterprise | middleware
>>> Mobile : +94 716546324
>>> Blog: http://supunsetunga.blogspot.com
>>>
>>
>>
>>
>> --
>>
>> *S. Suhothayan*
>> Technical Lead & Team Lead of WSO2 Complex Event Processor
>> *WSO2 Inc. *http://wso2.com
>> * *
>> lean . enterprise . middleware
>>
>>
>> *cell: (+94) 779 756 757 <%28%2B94%29%20779%20756%20757> | blog:
>> http://suhothayan.blogspot.com/ twitter:
>> http://twitter.com/suhothayan  | linked-in:
>> http://lk.linkedin.com/in/suhothayan *
>>
>
>
>
> --
> *Supun Sethunga*
> Senior Software Engineer
> WSO2, Inc.
> http://wso2.com/
> lean | enterprise | middleware
> Mobile : +94 716546324
> Blog: http://supunsetunga.blogspot.com
>



-- 
*Supun Sethunga*
Senior Software Engineer
WSO2, Inc.
http://wso2.com/
lean | enterprise | middleware
Mobile : +94 716546324
Blog: http://supunsetunga.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSOC 2016 - Project 21 : MongoDB Userstore Development

[Asantha Thilina]

Hi Tharindu,

thanks for the reply ,sure i will try out that and update the progress as
soon as possible

Thanks,
Asantha

On Mon, Jul 4, 2016 at 1:38 AM, Tharindu Edirisinghe 
wrote:

> Hi Asantha,
>
> While you are adding the roll back transaction capability, also look into
> testing a high load and try to generate database level exceptions. Once
> thing you can try out is writing a client for performing userstore manager
> operations such as add user, add role, login, logout etc. and play it with
> a high concurrency using Jmeter. Then we should be able to get a better
> understanding of transaction management with respective to MongoDB.
>
> Regards,
> TharinduE
>
> On Mon, Jul 4, 2016 at 10:57 AM, Asantha Thilina  > wrote:
>
>> Hi all,
>>
>> i will be trying for implement roll back transactions capability in
>> MongoDB to add to MongoDB User Store[2] i found that MongoDB use a concept
>> call two phase commit[1] i trying to implement that inside my code but it
>> seems to be little complex and i think it may arise performance issue when
>> adding high load of dataset at once is there any other better method i can
>> achieve this task? any advices would be grateful
>>
>> [1] https://docs.mongodb.com/manual/tutorial/perform-two-phase-commits/
>> [2] https://github.com/asanthamax/mongodbuserstore
>>
>> Thanks,
>> Asantha
>>
>> On Wed, Jun 29, 2016 at 2:55 PM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> I have finished and added delete functions also to users ,roles and user
>>> claim deletions to my repo[1]
>>>
>>> [1] https://github.com/asanthamax/mongodbuserstore
>>>
>>> Thanks,
>>> Asantha
>>>
>>> On Mon, Jun 27, 2016 at 4:18 AM, Asantha Thilina <
>>> asanthathil...@gmail.com> wrote:
>>>
 Hi aiya,

 i have small problem in my research, i will be developing convolution
 neural network using deeplearning4j to detect frauds i have discovered some
 fraud patterns which can use to train my network but the problem i having
 is,are there any possibility to add condition driven capability to dataset
 to train model

 Thanks,
 Asantha

 On Wed, Jun 22, 2016 at 9:35 PM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Good work Asantha... Meanwhile let's look at getting your research
> work published as well. I will provide feedback for the work so far in
> couple of days time. I have also completed the Mid Review based on your
> current work where you are already ahead of schedule.
>
> Regards,
> TharinduE
>
> On Wed, Jun 22, 2016 at 9:41 PM, Asantha Thilina <
> asanthathil...@gmail.com> wrote:
>
>> Hi Tharindu,
>>
>> following is the summary of operations i have implemented up to now
>> and yet to implement
>>
>> 1. Add new MongoDB User Store - done both case sensitive and
>> intensensitive
>> 2. Add new users to MongoDB user store - done both case sensitive and
>> intensensitive
>> 3. Add new roles to MongoDB user store - done both case sensitive and
>> intensensitive
>> 4. Search users and roles - done both case sensitive and
>> intensensitive
>> 5. Assign roles to mongodb user store users - done both case
>> sensitive and intensensitive
>> 6. Assign users to mongodb user store roles - done both case
>> sensitive and intensensitive
>> 7. Edit claim values of user profiles  - done both case sensitive and
>> intensensitive
>> for those implemented user operations i have added selenium scripts
>> also to my repo[1] and also i have prepared user guide[2] and 
>> administrator
>> guide[3] also and also i have updated my blog[4] with all my tasks what i
>> have done and following are the tasks yet to complete
>>
>> 1. implement delete operations
>> 2. implement new profiles adding
>> 3. check for injections possibilities and improve the security of all
>> the functions
>> 4. prepare full test scripts for all the functions
>> 5. prepare developer guide and database architecture diagrams
>>
>> expect your feedback
>>
>> [1]  https://github.com/asanthamax/mongodbuserstore
>> [2]
>> https://docs.google.com/document/d/1mdnmYruzQz5QSxAYwM1XVeJntJMFdxUsV5gord7LuPA/edit?usp=sharing
>> [3]
>> https://docs.google.com/document/d/1fCLfZYsPOBkHMzRCGM3aexoBSplX3bKIRmONmFsgkBc/edit?usp=sharing
>> [4]  http://asanthamax.blogspot.com
>>
>> Thanks,
>> Asantha
>>
>> On Wed, Jun 22, 2016 at 12:29 AM, Asantha Thilina <
>> asanthathil...@gmail.com> wrote:
>>
>>> Hi Tharindu,
>>>
>>> I have finished the case insensitive user operations as well and i
>>> added selenium test scripts for those implemented functions to my 
>>> repo[1]
>>> except delete function all the other functions with test script added 
>>> to my
>>> repo[1]
>>>

[Dev] [DEV][ES]Secure Vault for JSON files in Enterprise Store(ES)

[Megala Uthayakumar]

Hi,

We are working on ES extension for DS(Dashboard Server) gadgets. In that
case, we need to have the user name and password in a json file and that is
used to authenticate the user in DS side when sending a DS gadgets from ES
side to DS. Is secure vault for json files is available in ES? If so how
can I use it? If not, is this included in road map of ES?

Thanks.

Regards,
Megala


-- 
Megala Uthayakumar

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

Re: [Dev] Scope based authorization for CDMF

[Prabath Abeysekera]

IMO, scopes for any application should be designed and implemented taking
the end-to-end business functionalities into account, rather than focussing
on different discrete pieces of small functional units such as UI, BE, etc.
For instance, if some user is authorized to "manage users", the underlying
scopes that make it possible to that particular user to perform the
intended task, should be shared across the UI as well as the BE. In other
words, the same scope that lets the user access the BE resources associated
with managing users, can be re-used to render the associated UI elements as
well. That way, not only it makes us avoid overly redundant scopes, which -
if not managed properly - can be a headache, but also helps us make things
much more simplified.

Cheers,
Prabath

On Mon, Jul 4, 2016 at 12:00 PM, Chathura Dilan  wrote:

> +Dev
>
> For the UI
>
> IMO, UI should have their own permissions. and they should be associated
> with scopes
>
> Such as
>
> *UI Permission scopes*
> manage_user users:add, users:edit, users:delete, users:view, roles:view
> view_user   users:view
>
> These UI permissions can to be assigned from the permission tree to a
> role. Once the permission is assigned to a role, the scopes associated with
> the permission also assigned to that role automatically.
>
> For that we can reduce the complexity of assigning the UI permission. WDYT?
>
>
>
>
> On Mon, Jul 4, 2016 at 10:16 AM, Milan Perera  wrote:
>
>> Sure, will schedule it in the morning.
>>
>> On Mon, Jul 4, 2016 at 6:27 AM, Prabath Abeysekera 
>> wrote:
>>
>>> Awesome! Shall we review this in the morn and be done with it?
>>>
>>> Cheers,
>>> Prabath
>>>
>>>
>>> On Monday, July 4, 2016, Milan Perera  wrote:
>>>
 Hi all,

 I've done the $subject and its still in my fork [1]. Let's have a
 review on that and then I will merge.
 I've tested this implementation with JDBC scope validator and it works
 fine.

 Currently I just only changed the devicemgt-api and have to do
 necessary changes to other apis as well.

 [1]
 https://github.com/milanperera/carbon-device-mgt/commit/49623a4693dcbd35f6b5305c3e29d31254fcb4ce


 Regards,

 --
 *Milan Perera *| Software Engineer
 WSO2, Inc | lean. enterprise. middleware.
 #20, Palm Grove, Colombo 03, Sri Lanka
 Mobile: +94 77 309 7088 | Work: +94 11 214 5345
 Email: mi...@wso2.com | Web: www.wso2.com
 

>>>
>>>
>>> --
>>> Prabath Abeysekara
>>> Technical Lead
>>> WSO2 Inc.
>>> Email: praba...@wso2.com
>>> Mobile: +94774171471
>>>
>>>
>>
>>
>> --
>> *Milan Perera *| Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>> Email: mi...@wso2.com  | Web: www.wso2.com
>> 
>>
>
>
>
> --
> Regards,
>
> Chatura Dilan Perera
> *Associate Tech Lead** - WSO2 Inc.*
> www.dilan.me
>



-- 
Prabath Abeysekara
Technical Lead
WSO2 Inc.
Email: praba...@wso2.com
Mobile: +94774171471
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Scope based authorization for CDMF

[Chathura Dilan]

+Dev

For the UI

IMO, UI should have their own permissions. and they should be associated
with scopes

Such as

*UI Permission scopes*
manage_user users:add, users:edit, users:delete, users:view, roles:view
view_user   users:view

These UI permissions can to be assigned from the permission tree to a role.
Once the permission is assigned to a role, the scopes associated with the
permission also assigned to that role automatically.

For that we can reduce the complexity of assigning the UI permission. WDYT?




On Mon, Jul 4, 2016 at 10:16 AM, Milan Perera  wrote:

> Sure, will schedule it in the morning.
>
> On Mon, Jul 4, 2016 at 6:27 AM, Prabath Abeysekera 
> wrote:
>
>> Awesome! Shall we review this in the morn and be done with it?
>>
>> Cheers,
>> Prabath
>>
>>
>> On Monday, July 4, 2016, Milan Perera  wrote:
>>
>>> Hi all,
>>>
>>> I've done the $subject and its still in my fork [1]. Let's have a review
>>> on that and then I will merge.
>>> I've tested this implementation with JDBC scope validator and it works
>>> fine.
>>>
>>> Currently I just only changed the devicemgt-api and have to do necessary
>>> changes to other apis as well.
>>>
>>> [1]
>>> https://github.com/milanperera/carbon-device-mgt/commit/49623a4693dcbd35f6b5305c3e29d31254fcb4ce
>>>
>>>
>>> Regards,
>>>
>>> --
>>> *Milan Perera *| Software Engineer
>>> WSO2, Inc | lean. enterprise. middleware.
>>> #20, Palm Grove, Colombo 03, Sri Lanka
>>> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
>>> Email: mi...@wso2.com | Web: www.wso2.com
>>> 
>>>
>>
>>
>> --
>> Prabath Abeysekara
>> Technical Lead
>> WSO2 Inc.
>> Email: praba...@wso2.com
>> Mobile: +94774171471
>>
>>
>
>
> --
> *Milan Perera *| Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 77 309 7088 | Work: +94 11 214 5345
> Email: mi...@wso2.com  | Web: www.wso2.com
> 
>



-- 
Regards,

Chatura Dilan Perera
*Associate Tech Lead** - WSO2 Inc.*
www.dilan.me
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please merge

[Isura Karunaratne]

Hi Kalpa,

Please find the carbon-multitenancy jira [1]. Test case for this
improvement can be written in Identity Sever side.

Thanks
Isura

[1] https://wso2.org/jira/browse/CMTENANCY-5

On Mon, Jul 4, 2016 at 6:26 AM, Kalpa Welivitigoda  wrote:

> Hi Isura,
>
> Would you please provide with a related carbon-multitenancy jira [1] and a
> test case for the fix?
>
> [1] https://wso2.org/jira/browse/CMTENANCY
>
> On Sat, Jul 2, 2016 at 1:35 AM, Isura Karunaratne  wrote:
>
>> Hi Johann,
>>
>>
>>
>> On Sat, Jul 2, 2016 at 1:03 AM, Johann Nallathamby 
>> wrote:
>>
>>> Added two comments. Please check.''
>>>
>>
>> Noted and Fixed.
>>
>>
>> Thanks
>> Isura
>>
>>>
>>> On Sat, Jul 2, 2016 at 12:05 AM, Isura Karunaratne 
>>> wrote:
>>>
 HI Kalpa,


 Please review and merge following PR[1]

 [1] https://github.com/wso2/carbon-multitenancy/pull/91

 Thanks
 Isura

 --
 Isura Dilhara Karunaratne
 Senior Software Engineer

 Mob +94 772 254 810


>>>
>>>
>>> --
>>> Thanks & Regards,
>>>
>>> *Johann Dilantha Nallathamby*
>>> Technical Lead & Product Lead of WSO2 Identity Server
>>> Governance Technologies Team
>>> WSO2, Inc.
>>> lean.enterprise.middleware
>>>
>>> Mobile - *+9476950*
>>> Blog - *http://nallaa.wordpress.com *
>>>
>>
>>
>>
>> --
>> Isura Dilhara Karunaratne
>> Senior Software Engineer
>>
>> Mob +94 772 254 810
>>
>>
>
>
> --
> Best Regards,
>
> Kalpa Welivitigoda
> Senior Software Engineer, WSO2 Inc. http://wso2.com
> Email: kal...@wso2.com
> Mobile: +94776509215
>



-- 
Isura Dilhara Karunaratne
Senior Software Engineer

Mob +94 772 254 810
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev