Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Dinuksha Ishwari]

Hi Maduranga,

I have made the suggested changes in the proposal. Would appreciate if you
could review and provide feedback.

Thanks,
Dinuksha.

On Mon, Apr 3, 2017 at 1:14 AM, Maduranga Siriwardena 
wrote:

> Hi Dinushika,
>
> I have added some comments to the the draft proposal.
>
> Thanks,
>
> On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi,
>>
>> Sorry for the late reply as I had my Semester exams this week. I have
>> shared the draft proposal on the GSoC dashboard. Would appreciate if you
>> could review and provide feedback.
>>
>> Thanks,
>> Dinuksha.
>>
>> On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Maduranga,
>>>
>>> Thank you for the information. I shall look in to this and proceed with
>>> the basic implementation and preparing the proposal. Will keep you informed.
>>>
>>> On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Dinuksha,

 DCR has 3 specs.

- OAuth 2.0 Dynamic Client Registration
- OAuth 2.0 Dynamic Client Registration Management
- OpenID Connect Dynamic Client Registration

 OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
 Connect Dynamic Client Registration is handled by [2]. This is the class
 that handles requests for /identity/connect/register. OAuth 2.0
 Dynamic Client Registration Management is the one you are going to
 implement.

 As a start you can just register a servlet and implement the
 functionality. We will guide you how to register a processor for identity
 endpoint, if we decide to go in that path.

 I hope that I answered your questions. Get back to us of you need
 anything clarified.


 [1] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oauth
 .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
 sor/DCRProcessor.java
 [2] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
 dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
 r/OIDCDCRProcessor.java

 Thanks,


 On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
 dinuksha.ishw...@gmail.com> wrote:

> Hi Maduranga,
>
> I have referred the given code [1] and observed that DCRProcessor will
> only process requests that call the endpoint /identity/register as 
> OAuth2.0
> specification and will not process the the calls to
> /identity/connect/register which is the endpoint specified in 
> OpenIDConnect
> specification for DCR. Correct me if I am wrong.
>
> I would appreciate if you could provide me some more information
> regarding exposing an endpoint for the custom component of DCRM.
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
> sor/DCRProcessor.java
>
> Thank you,
> Dinuksha.
>
> On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
> madura...@wso2.com> wrote:
>
>> Hi Dinuksha,
>>
>> Glad to hear that you have made progress with the project.
>>
>> As a start, exposing a separate servlet would be okay. But going
>> forward with the project, you may have to use the approach used in the 
>> DCR
>> endpoint which is [1] (or may have to use a cxf endpoint).
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
>> sor/DCRProcessor.java
>>
>> Thanks,
>>
>> On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Devs/Mentors,
>>>
>>> This is to inform you the progress made so far with the project. In
>>> order to get familiar with the wso2 codebase and the product building
>>> process, I built the kernel and product-is for IS 5.3.0 successfully. 
>>> Then
>>> I patched the current DCR component, built it and added as a patch to IS
>>> and got the modifications applied to the server.
>>>
>>> Now I am working on a basic implementation of the DCRM where I have
>>> written a separate component and exposed a servlet from that. I am now
>>> modifying it to accept required parameters and to get the basic flow
>>> working. I will share the code via github soon for reviewing. Meanwhile 
>>> I'm
>>> working on preparing the project proposal as well.
>>>
>>> Regards,
>>> Dinuksha.
>>>
>>> On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
>>> 

Re: [Dev] [GSoC] Proposal 24 : Real-Time Machine Learning Toolkit for Siddhi

[Nadheesh Jihan]

About the comment, It is like adding a version of method to take a
period(week) and no of events(1000) and then train the model periodically
using 1000 entries once a week without continuously training​ the model
whenever new event comes?

On Apr 3, 2017 9:33 AM, "Nadheesh Jihan"  wrote:

> Ok. I'll start improving the proposal right now.
>
> Thanks for the comments.
>
> On Mon, Apr 3, 2017 at 8:11 AM, Upul Bandara  wrote:
>
>> Hi Nadheesh,
>>
>> I reviewed your proposal. For me, it looks OK.
>> Please add a little bit on how these algorithm works (high-level
>> introduction would be enough.)
>>
>> Thanks,
>> Upul
>>
>>
>> On Thu, Mar 30, 2017 at 2:23 PM, Sriskandarajah Suhothayan > > wrote:
>>
>>> @Upul can you go through this.
>>>
>>>
>>> On Wed, Mar 29, 2017 at 8:38 PM, Nadheesh Jihan 
>>> wrote:
>>>
 Hi,

 I have shared the draft proposal for the GSoC proposal - 24 via the
 GSoC web portal. Please review it and let me know if there are any changes
 required in the proposal.

 I have changed the proposal according to the our last discussion.
 Please check if the diagrams represent those details correctly.

 Thank you.
 --
 Best regards,
 *Nadheesh Jihan*
 Undergraduate | Department of Computer Science and Engineering
 Faculty of Engineering
 University of Moratuwa

>>>
>>>
>>>
>>> --
>>>
>>> *S. Suhothayan*
>>> Associate Director / Architect
>>> *WSO2 Inc. *http://wso2.com
>>> * *
>>> lean . enterprise . middleware
>>>
>>>
>>> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
>>> http://suhothayan.blogspot.com/ twitter:
>>> http://twitter.com/suhothayan  | linked-in:
>>> http://lk.linkedin.com/in/suhothayan *
>>>
>>
>>
>>
>> --
>> Upul Bandara,
>> Associate Technical Lead, WSO2, Inc.,
>> Mob: +94 715 468 345 <+94%2071%20546%208345>.
>>
>
>
>
> --
> Best regards,
> *Nadheesh Jihan*
> Undergraduate | Department of Computer Science and Engineering
> Faculty of Engineering
> University of Moratuwa
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC] Proposal 24 : Real-Time Machine Learning Toolkit for Siddhi

[Nadheesh Jihan]

Ok. I'll start improving the proposal right now.

Thanks for the comments.

On Mon, Apr 3, 2017 at 8:11 AM, Upul Bandara  wrote:

> Hi Nadheesh,
>
> I reviewed your proposal. For me, it looks OK.
> Please add a little bit on how these algorithm works (high-level
> introduction would be enough.)
>
> Thanks,
> Upul
>
>
> On Thu, Mar 30, 2017 at 2:23 PM, Sriskandarajah Suhothayan 
> wrote:
>
>> @Upul can you go through this.
>>
>>
>> On Wed, Mar 29, 2017 at 8:38 PM, Nadheesh Jihan 
>> wrote:
>>
>>> Hi,
>>>
>>> I have shared the draft proposal for the GSoC proposal - 24 via the GSoC
>>> web portal. Please review it and let me know if there are any changes
>>> required in the proposal.
>>>
>>> I have changed the proposal according to the our last discussion. Please
>>> check if the diagrams represent those details correctly.
>>>
>>> Thank you.
>>> --
>>> Best regards,
>>> *Nadheesh Jihan*
>>> Undergraduate | Department of Computer Science and Engineering
>>> Faculty of Engineering
>>> University of Moratuwa
>>>
>>
>>
>>
>> --
>>
>> *S. Suhothayan*
>> Associate Director / Architect
>> *WSO2 Inc. *http://wso2.com
>> * *
>> lean . enterprise . middleware
>>
>>
>> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
>> http://suhothayan.blogspot.com/ twitter:
>> http://twitter.com/suhothayan  | linked-in:
>> http://lk.linkedin.com/in/suhothayan *
>>
>
>
>
> --
> Upul Bandara,
> Associate Technical Lead, WSO2, Inc.,
> Mob: +94 715 468 345 <+94%2071%20546%208345>.
>



-- 
Best regards,
*Nadheesh Jihan*
Undergraduate | Department of Computer Science and Engineering
Faculty of Engineering
University of Moratuwa
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] For reference - data changes between MB 3.1.0 and MB 3.2.0 (internal feature)

[Sasikala Kottegoda]

Hi Hasitha,

Following are the changes in MB 3.2.0 compared to 3.1.0 in a summary as I
can see.

   1. Changes in subscriptions data in MB_DURABLE_SUBSCRIPTION
   2. Simplified queue data in MB_QUEUE
   3. Simplified  binding data in MB_BINDINGS
   4. All queue names being lower case

We have already written a tool to cater the first 3 requirements. What is
remaining is to only change the queue names to lower case which was
intorduced recently.

Regarding the concerns on the changes in subscription data, we actually
have to do almost nothing since there won't be any active subscriptions
when the system is migrated. We only need to remove all susbription entries
from the table so that new subscriptions to MB 3.2.0 will be of the new
format.

Ragarding your suggestion on the approach for migration, we cannot wait
until all the subscriptions are done consuming since there could be
inactive subscribers, slow subscribers, a large number of pending messages,
etc. In that case, what we can do is to provide a migration client which
will consume from MB 3.1.0 and publish to MB 3.2.0 as in what we have
suggested in [1].

If the system could have a down time, both approaches would be okay. Where
as, if we need to migrate with zero down time, we'll need to go with the
first approach which is to write a mgration tool.

[1] https://docs.wso2.com/display/MB300/Upgrading+from+a+Previous+Release

Thank you,
Sasikala

On Sun, Apr 2, 2017 at 8:41 PM, Ramith Jayasinghe  wrote:

> whats the possibility of writing a tool which can migrate the data?
>
>
> On Sun, Apr 2, 2017 at 7:53 PM, Hasitha Hiranya  wrote:
>
>> Hi,
>>
>> Please see attached.
>>
>> 1. Queue names should be fixed in about 5 tables (make all simple)
>> 2. Queue data string is updated in the model
>> 3. Subscriber data string is updated in the model
>> 4. Subscriber has a UUID as subscriber ID now.
>> 5. Subscriber connection is base64 encoded. Code will decode and work. In
>> 3.1.0 there was nothing like that.
>> 6. Inactive durable topic subscribers are derived from the queues now. No
>> entries in subscriber table.
>>
>>
>> Since there is a lot of changes in schema and code, IMO migrating from
>> 3.1.0 to 3.2.0 is error prone. Mainly this is because the model of working
>> is different now.
>>
>> Can we migrate a production MB customer to EI using below approach?
>>
>> 1. Create an EI cluster. MB cluster is in production.
>> 2. Switch publishers to EI cluster. Let subscribers be done with MB
>> cluster
>> 3. Switch subscribers also to EI cluster.
>>
>> For durable topic/queue subscribers above should work.
>>
>> WDYT?
>>
>>
>> --
>> *Hasitha Abeykoon*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* 
>>
>>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851 <+94%2077%20754%202851>
>



-- 
Sasikala Kottegoda
*Software Engineer*
WSO2 Inc., http://wso2.com/
lean. enterprise. middleware
Mobile: +94 774835928

[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV] GSoC 2017 - Real-Time Machine Learning Toolkit for Siddhi

[Upul Bandara]

Hi Kasun,

I reviewed your proposal and it looks OK for me.
I have added few comments. Can you please look at them?

Thanks,
Upul


On Sun, Apr 2, 2017 at 5:31 AM, Kasun Weerakoon  wrote:

> Hi Upul,
>
> I shared my draft proposal in GSoC dashboard and I kindly request your
> feedback in improving the proposal.
>
> Thanks and Regards,
>
> *Kasun Bandara*
> Faculty of Information Technology, University of Moratuwa
> 0715787004 | kasun...@gmail.com
> 
>   
>
> On Tue, Mar 28, 2017 at 3:25 PM, Kasun Weerakoon 
> wrote:
>
>> Hi,
>>
>> I'm working on the project proposal and there were several questions
>> emerged as follows,
>>
>>1. In offline machine learning we normally preprocess data by doing
>>operations such as *scaling*, before training the model. So in the
>>streaming algorithm is there any way to do that?
>>
>>2. Does this algorithms we are going to implement should support *non
>>numeric* input such as text data?
>>
>>3. If it's so,  do we need to implement a *word2vec* model to convert
>>inputs into numeric vectors?
>>
>>4. If our streaming algorithms supports sentiment analysis on the
>>Social Networks,  how are we going to address this problem with streaming
>>data?
>>I researched about this matter and found some approach such as *Modified
>>Balanced Winnow *for streaming algorithms instead of batch mode
>>learning approach.
>>http://file.scirp.org/pdf/JDAIP_2014053015541008.pdf
>>
>> I appreciate your opinion about this problems and it would be very
>> helpful in creating the proposal for me.
>>
>> Thanks and Regards,
>>
>> *Kasun Bandara*
>> Faculty of Information Technology, University of Moratuwa
>> 0715787004 | kasun...@gmail.com
>> 
>>   
>>
>> On Thu, Mar 23, 2017 at 11:19 AM, Kasun Weerakoon 
>> wrote:
>>
>>> Hi,
>>>
>>> I started working on the project proposal as you mentioned and came up
>>> with a sample perceptron classifier algorithm.
>>>
>>> Please find the github repo in following link -
>>> https://github.com/KasunWeerakoon/GSoC_WSO2
>>>
>>> It would be great if you can provide me some feedback about it.
>>>
>>> Thanks and regards,
>>>
>>> On Wed, 15 Mar 2017, 07:25 Upul Bandara,  wrote:
>>>
 Hi Kasun,

 Sounds good. Also, please start working on the project proposal as
 well.
 The proposal should be included following high-level sections and
 please feel free to add sub-sections as needed.

 1. Description
 2. Deliverables
 3. Timeline
 4. Implementation


 Thanks,
 Upul

 On Tue, Mar 14, 2017 at 9:54 AM, Kasun Weerakoon 
 wrote:

 Hi,

 Sorry for being late to communicate my progress with you, because of my
 academic works. From now on I will be able to work on this project with my
 full potential.

 I went through the CEP quick start guide and created  event flow,
 received events via HTTP transport, processed events with an execution plan
 and published events to dashboard successfully.

 I also went through the Apache SAMOA getting start guide and did some
 tutorials.

 I'm currently reading Chapter 12 of the Mining of Massive Datasets book
 as you mentioned and hope your guidance to carry out the work.

 Thanks and Regards,

 *Kasun Bandara*
 Faculty of Information Technology, University of Moratuwa
 0715787004 | kasun...@gmail.com
 
   

 On Tue, Feb 28, 2017 at 12:06 PM, Kasun Weerakoon 
 wrote:

 Hi,

 According to the rules mentioned,  I think I'm eligible to the program.

 Thanks and Regards,

 *Kasun Bandara*
 Faculty of Information Technology, University of Moratuwa
 0715787004 | kasun...@gmail.com
 
   

 On Tue, Feb 28, 2017 at 10:59 AM, Upul Bandara  wrote:

 Hi Kasun,

 Great!
 Also, please verify your eligibility as per the GSoC rules:
 https://summerofcode.withgoogle.com/rules/

 Thanks,
 Upul

 On Tue, Feb 21, 2017 at 9:52 AM, Kasun Weerakoon 
 wrote:

 Hi Upul,

 Thanks you for your reply. I'll go through above mentioned guides and
 get back to you later.

 Regards,
 Kasun Weerakoon.

 On Tue, 21 Feb 2017, 08:39 Upul Bandara,  wrote:

 Hi Kasun,

 We are glad to see your interest!

Re: [Dev] [GSoC] Proposal 24 : Real-Time Machine Learning Toolkit for Siddhi

[Upul Bandara]

Hi Nadheesh,

I reviewed your proposal. For me, it looks OK.
Please add a little bit on how these algorithm works (high-level
introduction would be enough.)

Thanks,
Upul


On Thu, Mar 30, 2017 at 2:23 PM, Sriskandarajah Suhothayan 
wrote:

> @Upul can you go through this.
>
>
> On Wed, Mar 29, 2017 at 8:38 PM, Nadheesh Jihan 
> wrote:
>
>> Hi,
>>
>> I have shared the draft proposal for the GSoC proposal - 24 via the GSoC
>> web portal. Please review it and let me know if there are any changes
>> required in the proposal.
>>
>> I have changed the proposal according to the our last discussion. Please
>> check if the diagrams represent those details correctly.
>>
>> Thank you.
>> --
>> Best regards,
>> *Nadheesh Jihan*
>> Undergraduate | Department of Computer Science and Engineering
>> Faculty of Engineering
>> University of Moratuwa
>>
>
>
>
> --
>
> *S. Suhothayan*
> Associate Director / Architect
> *WSO2 Inc. *http://wso2.com
> * *
> lean . enterprise . middleware
>
>
> *cell: (+94) 779 756 757 <+94%2077%20975%206757> | blog:
> http://suhothayan.blogspot.com/ twitter:
> http://twitter.com/suhothayan  | linked-in:
> http://lk.linkedin.com/in/suhothayan *
>



-- 
Upul Bandara,
Associate Technical Lead, WSO2, Inc.,
Mob: +94 715 468 345.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - Proposal 20: [IS] OAuth 2.0 Dynamic Client Registration Management Protocol Support

[Maduranga Siriwardena]

Hi Dinushika,

I have added some comments to the the draft proposal.

Thanks,

On Sat, Apr 1, 2017 at 9:24 PM, Dinuksha Ishwari  wrote:

> Hi,
>
> Sorry for the late reply as I had my Semester exams this week. I have
> shared the draft proposal on the GSoC dashboard. Would appreciate if you
> could review and provide feedback.
>
> Thanks,
> Dinuksha.
>
> On Thu, Mar 23, 2017 at 8:11 AM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Maduranga,
>>
>> Thank you for the information. I shall look in to this and proceed with
>> the basic implementation and preparing the proposal. Will keep you informed.
>>
>> On Wed, Mar 22, 2017 at 9:40 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Dinuksha,
>>>
>>> DCR has 3 specs.
>>>
>>>- OAuth 2.0 Dynamic Client Registration
>>>- OAuth 2.0 Dynamic Client Registration Management
>>>- OpenID Connect Dynamic Client Registration
>>>
>>> OAuth 2.0 Dynamic Client Registration is handled by [1]. And OpenID
>>> Connect Dynamic Client Registration is handled by [2]. This is the class
>>> that handles requests for /identity/connect/register. OAuth 2.0 Dynamic
>>> Client Registration Management is the one you are going to implement.
>>>
>>> As a start you can just register a servlet and implement the
>>> functionality. We will guide you how to register a processor for identity
>>> endpoint, if we decide to go in that path.
>>>
>>> I hope that I answered your questions. Get back to us of you need
>>> anything clarified.
>>>
>>>
>>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
>>> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/
>>> processor/DCRProcessor.java
>>> [2] https://github.com/wso2-extensions/identity-inbound-auth
>>> -oauth/blob/master/components/org.wso2.carbon.identity.oidc.
>>> dcr/src/main/java/org/wso2/carbon/identity/oidc/dcr/processo
>>> r/OIDCDCRProcessor.java
>>>
>>> Thanks,
>>>
>>>
>>> On Wed, Mar 22, 2017 at 10:53 AM, Dinuksha Ishwari <
>>> dinuksha.ishw...@gmail.com> wrote:
>>>
 Hi Maduranga,

 I have referred the given code [1] and observed that DCRProcessor will
 only process requests that call the endpoint /identity/register as OAuth2.0
 specification and will not process the the calls to
 /identity/connect/register which is the endpoint specified in OpenIDConnect
 specification for DCR. Correct me if I am wrong.

 I would appreciate if you could provide me some more information
 regarding exposing an endpoint for the custom component of DCRM.

 [1] https://github.com/wso2-extensions/identity-inbound-auth
 -oauth/blob/master/components/org.wso2.carbon.identity.oauth
 .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
 sor/DCRProcessor.java

 Thank you,
 Dinuksha.

 On Tue, Mar 21, 2017 at 11:54 PM, Maduranga Siriwardena <
 madura...@wso2.com> wrote:

> Hi Dinuksha,
>
> Glad to hear that you have made progress with the project.
>
> As a start, exposing a separate servlet would be okay. But going
> forward with the project, you may have to use the approach used in the DCR
> endpoint which is [1] (or may have to use a cxf endpoint).
>
> [1] https://github.com/wso2-extensions/identity-inbound-auth
> -oauth/blob/master/components/org.wso2.carbon.identity.oauth
> .dcr/src/main/java/org/wso2/carbon/identity/oauth/dcr/proces
> sor/DCRProcessor.java
>
> Thanks,
>
> On Tue, Mar 21, 2017 at 12:26 PM, Dinuksha Ishwari <
> dinuksha.ishw...@gmail.com> wrote:
>
>> Hi Devs/Mentors,
>>
>> This is to inform you the progress made so far with the project. In
>> order to get familiar with the wso2 codebase and the product building
>> process, I built the kernel and product-is for IS 5.3.0 successfully. 
>> Then
>> I patched the current DCR component, built it and added as a patch to IS
>> and got the modifications applied to the server.
>>
>> Now I am working on a basic implementation of the DCRM where I have
>> written a separate component and exposed a servlet from that. I am now
>> modifying it to accept required parameters and to get the basic flow
>> working. I will share the code via github soon for reviewing. Meanwhile 
>> I'm
>> working on preparing the project proposal as well.
>>
>> Regards,
>> Dinuksha.
>>
>> On Fri, Mar 17, 2017 at 8:04 AM, Dinuksha Ishwari <
>> dinuksha.ishw...@gmail.com> wrote:
>>
>>> Hi Omindu,
>>>
>>> Thanks for the information.
>>>
>>>
>>>
>>> On Fri, Mar 17, 2017 at 1:44 AM, Omindu Rathnaweera >> > wrote:
>>>
 Hi Dinuksha,

 For OAuth, those two are the only libraries we use.


 On Wed, Mar 15, 2017 at 10:16 AM, Dinuksha Ishwari 

Re: [Dev] For reference - data changes between MB 3.1.0 and MB 3.2.0 (internal feature)

[Ramith Jayasinghe]

whats the possibility of writing a tool which can migrate the data?


On Sun, Apr 2, 2017 at 7:53 PM, Hasitha Hiranya  wrote:

> Hi,
>
> Please see attached.
>
> 1. Queue names should be fixed in about 5 tables (make all simple)
> 2. Queue data string is updated in the model
> 3. Subscriber data string is updated in the model
> 4. Subscriber has a UUID as subscriber ID now.
> 5. Subscriber connection is base64 encoded. Code will decode and work. In
> 3.1.0 there was nothing like that.
> 6. Inactive durable topic subscribers are derived from the queues now. No
> entries in subscriber table.
>
>
> Since there is a lot of changes in schema and code, IMO migrating from
> 3.1.0 to 3.2.0 is error prone. Mainly this is because the model of working
> is different now.
>
> Can we migrate a production MB customer to EI using below approach?
>
> 1. Create an EI cluster. MB cluster is in production.
> 2. Switch publishers to EI cluster. Let subscribers be done with MB cluster
> 3. Switch subscribers also to EI cluster.
>
> For durable topic/queue subscribers above should work.
>
> WDYT?
>
>
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>


-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] GSoC 2017 - Proposal 8: CLI tool for WSO2 API Manager

[Pubudu Gunatilaka]

Hi Ayesh,

Added some comments to the proposal.

Thank you!

On Sun, Apr 2, 2017 at 2:02 PM, Ayeshmantha Perera 
wrote:

> Hi All
> I shared the draft proposal in the GSOC dashboard.Would be great and
> appreciated if can review and provide a feed back on it
>
> Thank you
> Regards
> Ayeshmantha
>
> On Tue, Mar 7, 2017 at 1:28 PM, Ayeshmantha Perera <
> akayeshman...@gmail.com> wrote:
>
>> Hi Pubudu
>>
>> Yeah already started going through the code and started some
>> implementation regarding the Token generation task.Already up and run
>> the  WSO2 API Manager 3.0.0-m1 which is based on Carbon 5(C5) and also went
>> through some coding based on Go for CLI tool and also based on
>> Go-Programming and can find the the CLI tool  worked on in [1] And the
>> coding on go programming in [2] repos.
>>
>> [1] https://github.com/Akayeshmantha/GO_CLI_Practice
>>
>> [2] https://github.com/Akayeshmantha/Go_Practice
>>
>> Than you
>> Best Regards
>> Ayeshmantha
>>
>>
>>
>>
>> On Mon, Mar 6, 2017 at 8:05 PM, Ayeshmantha Perera <
>> akayeshman...@gmail.com> wrote:
>>
>>> Hi Pubudu
>>>
>>> Went through the basic key concepts of the WSO2 API Manager and went
>>> through the token generation Documentation And the specification doc of
>>> OAuth 2  protocol to get more idea on how it will be used in the task on
>>> token generation.And went through the code of Dynamic client registration
>>> class(dcr)[1] and .And yeah for the time been proposed a solution on Token
>>> generation task [2].
>>>
>>> [1] https://github.com/wso2/carbon-apimgt/blob/master/compon
>>> ents/apimgt/org.wso2.carbon.apimgt.rest.api.dcr/src/main/jav
>>> a/org/wso2/carbon/apimgt/rest/api/dcr/web/impl/RegistrationS
>>> erviceImpl.java#L12
>>> 
>>>
>>> [2] http://gsocproposal8.blogspot.com/2017/02/task-4-key-gen
>>> eration-solution-proposed.html
>>>
>>> Thank you
>>> Best regards
>>> Ayeshmantha
>>>
>>> On Wed, Mar 1, 2017 at 1:51 AM, Pubudu Gunatilaka 
>>> wrote:
>>>
 Hi Ayeshmantha,

 Thank you for your interest and good progress on the work.

 As you have some experience in using API Manager, you can also go
 through the API Manager concepts [1] and get familiar with them.
 Additionally, you can try out API export/import feature [2] and the API
 Manager 2.1.0 REST APIs [3] to tryout the product.

 Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
 Manager implementation and you can find the relevant repos in [4] and [5].
 When you are developing the CLI, you should use the C5 REST APIs. API
 Manager team has already added most important REST APIs and we are working
 on adding new REST APIs based on the functionalities. Meantime, you can
 also get familiar with GO language and learn the concepts.

 As described in the project description you need to develop a CLI tool
 for API Manager. You can also check the available CLI tools and get an idea
 how you can develop the CLI in a more user-friendly way.

 [1] - https://docs.wso2.com/display/AM210/Key+Concepts
 [2] - https://docs.wso2.com/display/AM210/Migrating+the+APIs+to+a+
 Different+Environment
 [3] - https://docs.wso2.com/display/AM210/WSO2+APIs
 [4] - https://github.com/wso2/carbon-apimgt/tree/C5
 [5] - https://github.com/wso2/product-apim/tree/C5

 Thank you!

 On Wed, Mar 1, 2017 at 2:28 PM, Tharindu Edirisinghe <
 tharin...@wso2.com> wrote:

> Hi Ayeshmantha,
>
> We are glad to see  your interest in doing GSoC with WSO2. I have
> added the mentors of the project here, so they will guide you for
> proceeding further.
>
> Best Regards,
> Tharindu Edirisinghe
>
> On Wed, Mar 1, 2017 at 1:25 PM, Ayeshmantha Perera <
> akayeshman...@gmail.com> wrote:
>
>> Hi All,
>>
>> I'm Ayeshmantha Perera, from Sri Lanka Institute of Information
>> Technology, currently studying in the final (4th) year specializing in
>> Software Engineering.
>>
>> I am interested in taking part in GSoC 2017 with WSO2 and and hope to
>> apply for the CLI tool on API Manager.
>>
>> I have been following up the work done by the API Manager team of
>> WSO2 and went through the webinars that was handled by WSO2 API Manager
>> team.
>>
>> I have experienced  working on WSO2 API Manager in my previous
>> working experience as an Intern.And I'm experienced on WSO2 ESB and Also
>> the WSO2 Data analytics server also.
>>
>> Other than the experience on the products I have experience on
>> working with Go lang ,Java EE ,Maven,Git,OAuth2 protocol,JAX-RS,Spring
>> ,Hibernater.And I have 1 year experience on Node.js development, with

[Dev] For reference - data changes between MB 3.1.0 and MB 3.2.0 (internal feature)

[Hasitha Hiranya]

Hi,

Please see attached.

1. Queue names should be fixed in about 5 tables (make all simple)
2. Queue data string is updated in the model
3. Subscriber data string is updated in the model
4. Subscriber has a UUID as subscriber ID now.
5. Subscriber connection is base64 encoded. Code will decode and work. In
3.1.0 there was nothing like that.
6. Inactive durable topic subscribers are derived from the queues now. No
entries in subscriber table.


Since there is a lot of changes in schema and code, IMO migrating from
3.1.0 to 3.2.0 is error prone. Mainly this is because the model of working
is different now.

Can we migrate a production MB customer to EI using below approach?

1. Create an EI cluster. MB cluster is in production.
2. Switch publishers to EI cluster. Let subscribers be done with MB cluster
3. Switch subscribers also to EI cluster.

For durable topic/queue subscribers above should work.

WDYT?


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


data changes between mb 3.1.0 and 3.2.0
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GSoC 2017][IS] SCIM 2.0 Compliance Test Suite

[Vindula Jayawardana]

Hi Omindu,

Thank you for the prompt feedback on the draft proposal. I incorporated the
suggestions you made on the proposal.

As also mentioned in the proposal, I made the configuration options more
flexible by giving the manual configuration feasibility to the tester as an
optional feature apart from what is mandatory in the project. I hope that
would give us the required flexibility in the SCIM 2.0 compliance test
suite in terms of configuration options.

Thank you,

*Vindula Jayawardana*
Computer Science and Engineering Dept.
University of Moratuwa
mobile : +713462554
Email : vindul...@gmail.com






*“Respect is how to treat everyone, not just those you want to impress. "*


*-Richard Branson-*



On 2 April 2017 at 17:08, Omindu Rathnaweera  wrote:

> Will have a look Vindula.
>
> Thanks for putting an effort on running the 1.1 test. The intention behind
> it was to get a general idea on what to include in the 2.0 test suite and
> the areas to be improved. What you have obtained should be enough to
> understand the nature of the tests and basics information to be captured. I
> agree on the fact that the configuration options should be more flexible.
> Let's capture this in the project proposal if you haven't already.
>
> Regards,
> Omindu.
>
>
>
>
>
> On Sun, Apr 2, 2017 at 1:26 PM, Vindula Jayawardana <
> vindula...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>> I shared my draft proposal in GSoC dashboard and I kindly request your
>> feedback in improving the proposal.
>>
>> Thank you,
>>
>> *Vindula Jayawardana*
>> Computer Science and Engineering Dept.
>> University of Moratuwa
>> mobile : +713462554
>> Email : vindul...@gmail.com
>>
>> 
>> 
>> 
>> 
>>
>> *“Respect is how to treat everyone, not just those you want to impress. "*
>>
>>
>> *-Richard Branson-*
>>
>>
>>
>> On 30 March 2017 at 23:13, Vindula Jayawardana 
>> wrote:
>>
>>> Hi,
>>>
>>> As mentioned above, I looked at the SCIM 1.1 compliance test suite [1].
>>> Due to the reason that the SCIM 1.1 test suite requires an internet facing
>>> SCIM 1.1 server to run the tests against, I setup-ed an Identity Server
>>> instance in AWS [2]. However when the test are run, it fails due to
>>> /ServiceProviderConfigs and /Schemas endpoints. As WSO2 SCIM 1.1 support
>>> [3] is not covering the mentioned two endpoints, tests are failing when
>>> run.
>>>
>>> However in order to get an idea on how the result representation had
>>> been done in SCIM 1.1 compliance test suit, I mocked the
>>> /ServiceProviderConfigs endpoint [4] and was able to get the
>>> following output.
>>>
>>>
>>> ​
>>>
>>> Due to the complexity of mocking the /Schemas endpoint and also as the
>>> test on one endpoint ( /ServiceProviderConfigs) could give the nature
>>> of the result representation as seen above, I did not try to mock /Schemas
>>> endpoint and run the test suit again. However I tried by mocking the
>>> endpoint with 501 NOT IMPLEMENTED [5] as the output, but that was not
>>> accepted by the test suit as a valid return object.
>>>
>>> However, in my opinion, the SCIM test suit should be flexible in nature
>>> to skip any test which was given the input from the SCIM server as 501 NOT
>>> IMPLEMENTED [5]. I encourage such kind of implementation to be adopted in
>>> the proposed SCIM 2.0 compliance test suit as in that way the test suit
>>> acknowledges the SP's inability to provide those endpoints while making
>>> sure such kind of inability does not compromise the ability to run the test
>>> suit on other endpoints.
>>>
>>> [1] - http://www.simplecloud.info/#complianceTest
>>> [2] - https://aws.amazon.com/
>>> [3] - https://github.com/wso2/charon/tree/release-2.0.7
>>> [4] - https://github.com/Vindulamj/mocked-identity-inbound-provi
>>> sioning-scim/tree/master/identity-inbound-provisioning-scim-master
>>> [5] - http://www.simplecloud.info/specs/draft-scim-api-01.html#anchor6
>>>
>>> *Vindula Jayawardana*
>>> Computer Science and Engineering Dept.
>>> University of Moratuwa
>>> mobile : +713462554
>>> Email : vindul...@gmail.com
>>>
>>> 
>>> 
>>> 
>>> 
>>>
>>> *“Respect is how to treat everyone, not just those you want to impress.
>>> "*
>>>
>>>
>>> *-Richard Branson-*
>>>
>>>
>>>
>>> On 10 March 2017 at 16:42, Vindula Jayawardana >> > wrote:
>>>
 Hi,

 Thank you very much for the prompt replies. I will look into the points
 

Re: [Dev] [GSoC 2017][IS] SCIM 2.0 Compliance Test Suite

[Omindu Rathnaweera]

Will have a look Vindula.

Thanks for putting an effort on running the 1.1 test. The intention behind
it was to get a general idea on what to include in the 2.0 test suite and
the areas to be improved. What you have obtained should be enough to
understand the nature of the tests and basics information to be captured. I
agree on the fact that the configuration options should be more flexible.
Let's capture this in the project proposal if you haven't already.

Regards,
Omindu.





On Sun, Apr 2, 2017 at 1:26 PM, Vindula Jayawardana <
vindula...@cse.mrt.ac.lk> wrote:

> Hi,
>
> I shared my draft proposal in GSoC dashboard and I kindly request your
> feedback in improving the proposal.
>
> Thank you,
>
> *Vindula Jayawardana*
> Computer Science and Engineering Dept.
> University of Moratuwa
> mobile : +713462554
> Email : vindul...@gmail.com
>
> 
> 
> 
> 
>
> *“Respect is how to treat everyone, not just those you want to impress. "*
>
>
> *-Richard Branson-*
>
>
>
> On 30 March 2017 at 23:13, Vindula Jayawardana 
> wrote:
>
>> Hi,
>>
>> As mentioned above, I looked at the SCIM 1.1 compliance test suite [1].
>> Due to the reason that the SCIM 1.1 test suite requires an internet facing
>> SCIM 1.1 server to run the tests against, I setup-ed an Identity Server
>> instance in AWS [2]. However when the test are run, it fails due to
>> /ServiceProviderConfigs and /Schemas endpoints. As WSO2 SCIM 1.1 support
>> [3] is not covering the mentioned two endpoints, tests are failing when
>> run.
>>
>> However in order to get an idea on how the result representation had been
>> done in SCIM 1.1 compliance test suit, I mocked the /ServiceProviderConfigs
>> endpoint [4] and was able to get the following output.
>>
>>
>> ​
>>
>> Due to the complexity of mocking the /Schemas endpoint and also as the
>> test on one endpoint ( /ServiceProviderConfigs) could give the nature of
>> the result representation as seen above, I did not try to mock /Schemas
>> endpoint and run the test suit again. However I tried by mocking the
>> endpoint with 501 NOT IMPLEMENTED [5] as the output, but that was not
>> accepted by the test suit as a valid return object.
>>
>> However, in my opinion, the SCIM test suit should be flexible in nature
>> to skip any test which was given the input from the SCIM server as 501 NOT
>> IMPLEMENTED [5]. I encourage such kind of implementation to be adopted in
>> the proposed SCIM 2.0 compliance test suit as in that way the test suit
>> acknowledges the SP's inability to provide those endpoints while making
>> sure such kind of inability does not compromise the ability to run the test
>> suit on other endpoints.
>>
>> [1] - http://www.simplecloud.info/#complianceTest
>> [2] - https://aws.amazon.com/
>> [3] - https://github.com/wso2/charon/tree/release-2.0.7
>> [4] - https://github.com/Vindulamj/mocked-identity-inbound-
>> provisioning-scim/tree/master/identity-inbound-provisioning-scim-master
>> [5] - http://www.simplecloud.info/specs/draft-scim-api-01.html#anchor6
>>
>> *Vindula Jayawardana*
>> Computer Science and Engineering Dept.
>> University of Moratuwa
>> mobile : +713462554
>> Email : vindul...@gmail.com
>>
>> 
>> 
>> 
>> 
>>
>> *“Respect is how to treat everyone, not just those you want to impress. "*
>>
>>
>> *-Richard Branson-*
>>
>>
>>
>> On 10 March 2017 at 16:42, Vindula Jayawardana 
>> wrote:
>>
>>> Hi,
>>>
>>> Thank you very much for the prompt replies. I will look into the points
>>> you have mentioned and will keep you updated here.
>>>
>>> Thank you.
>>>
>>> *Vindula Jayawardana*
>>> Computer Science and Engineering Dept.
>>> University of Moratuwa
>>> mobile : +713462554
>>> Email : vindul...@gmail.com
>>>
>>> 
>>> 
>>> 
>>> 
>>>
>>> *“Respect is how to treat everyone, not just those you want to impress.
>>> "*
>>>
>>>
>>> *-Richard Branson-*
>>>
>>>
>>>
>>> On 9 March 2017 at 21:22, Omindu Rathnaweera  wrote:
>>>
 Hi Vindula,

 If we can run the existing 1.1 test on IS and see the generated output,
 that will be a good point to start. However we'll need to host an IS
 instance publicly to run the tests on it.

 Regards,
 Omindu.



 On Thu, Mar 9, 2017 at 8:52 PM, Gayan Gunawardana 
 wrote:

> Hi Vindula,
>
> Thanks for your interest in this project.
> Since you have good 

Re: [Dev] [PRODUCT_EI] Class Loading issue with latest andes client

[Hasitha Amal De Silva]

+ We also tested and verified that Object messages can be produced and
consumed fine with the current andes client (without fronting with the
ESB).

Thanks

On Sun, Apr 2, 2017 at 4:35 PM, Hasitha Amal De Silva 
wrote:

> Hi Vijitha,
>
> We found a similar issue reported at [1], in which synapse-core is unable
> to load a class from CacheMediator. It seems the fix here was to remove the
> "resolution:=optional" line at the OSGI Import-Package section in the pom
> of CacheMediator (refer [2]).
>
> I tried the same fix at the synapse-core and saw that the error does not
> occur anymore. However, I'm still not sure how this scenario works with the
> old andes-client. Maybe the carbon-kernel upgrade handles optional
> resolutions in a different way ?
>
> @PrabathAr - any clue on this ?
>
> [1] : https://wso2.org/jira/browse/ESBJAVA-4878
> [2] : https://github.com/wso2/carbon-mediation/pull/745/files#diff-
> 4873f9136db2279e0714fbf75dfbbd1aL51
>
> Thanks
>
> On Sat, Apr 1, 2017 at 5:15 PM, Indika Sampath  wrote:
>
>> I was able to reproduce the above issue in ESB 5.0.0 with
>> andes-client-3.2.6.jar (beta release) as well. Exception says
>> org.apache.synapse.message.store.impl.commons.StorableMessage cannot be
>> found by andes_client. Basically what we getting is ByteBuffer as a message
>> and do not maintain any specific format. I wonder the issue regard to
>> kernel change (4.4.15) in the latest version. We need to further look into
>> the issue to identify the exact root cause. Public JIRA[1] create to track
>> down the issue.
>>
>> [1] https://wso2.org/jira/browse/MB-1923
>>
>> On Sat, Apr 1, 2017 at 10:37 AM, Nandika Jayawardana 
>> wrote:
>>
>>> Adding DEV
>>>
>>> Nandika
>>>
>>> On Fri, Mar 31, 2017 at 9:51 PM, Vijitha Ekanayake 
>>> wrote:
>>>
 Hi All,

 We Observe class loading issue with latest andes client (3.2.4) in MSMP
 scenarios. The issue occurs while consuming message from the message store
 where it continuously prints message[1]. I change the code a bit and got
 exact stack trace [2].It seems to be OSGI issue and this issue isn't there
 if we use previous andes client version(3.1.4).

 Did anyone come across this kind of OSGI issue before?


 [1].

 [2017-03-31 20:57:01,076] [EI-Core] ERROR - JmsConsumer
 [PaymentRequestJMSMessageStore-C-1] cannot receive message from store.
 Error:Could not deserialize message: java.lang.ClassNotFoundException:
 org.apache.synapse.message.store.impl.commons.StorableMessage cannot
 be found by andes_client_3.2.4_1.0.0

 [2].
 javax.jms.MessageFormatException: Could not deserialize message:
 java.lang.ClassNotFoundException: org.apache.synapse.message.sto
 re.impl.commons.StorableMessage cannot be found by
 andes_client_3.2.4_1.0.0
 at org.wso2.andes.client.message.JMSObjectMessage.getObject(JMS
 ObjectMessage.java:154)
 at org.apache.synapse.message.store.impl.jms.JmsConsumer.receiv
 e(JmsConsumer.java:99)
 at org.apache.synapse.message.processor.impl.sampler.SamplingSe
 rvice.fetch(SamplingService.java:188)
 at org.apache.synapse.message.processor.impl.sampler.SamplingSe
 rvice.execute(SamplingService.java:120)
 at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAd
 apter.java:98)
 at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute
 (TaskQuartzJobAdapter.java:67)
 at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executor
 s.java:511)
 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
 Executor.java:1142)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
 lExecutor.java:617)
 at java.lang.Thread.run(Thread.java:745)
 Caused by: java.lang.ClassNotFoundException:
 org.apache.synapse.message.store.impl.commons.StorableMessage cannot
 be found by andes_client_3.2.4_1.0.0
 at org.eclipse.osgi.internal.loader.BundleLoader.findClassInter
 nal(BundleLoader.java:501)
 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(Bund
 leLoader.java:421)
 at org.eclipse.osgi.internal.loader.BundleLoader.findClass(Bund
 leLoader.java:412)
 at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa
 dClass(DefaultClassLoader.java:107)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:348)
 at org.wso2.andes.client.util.ClassLoadingAwareObjectInputStrea
 m.load(ClassLoadingAwareObjectInputStream.java:64)
 at org.wso2.andes.client.util.ClassLoadingAwareObjectInputStrea
 m.resolveClass(ClassLoadingAwareObjectInputStream.java:38)
 at 

Re: [Dev] [PRODUCT_EI] Class Loading issue with latest andes client

[Hasitha Amal De Silva]

Hi Vijitha,

We found a similar issue reported at [1], in which synapse-core is unable
to load a class from CacheMediator. It seems the fix here was to remove the
"resolution:=optional" line at the OSGI Import-Package section in the pom
of CacheMediator (refer [2]).

I tried the same fix at the synapse-core and saw that the error does not
occur anymore. However, I'm still not sure how this scenario works with the
old andes-client. Maybe the carbon-kernel upgrade handles optional
resolutions in a different way ?

@PrabathAr - any clue on this ?

[1] : https://wso2.org/jira/browse/ESBJAVA-4878
[2] :
https://github.com/wso2/carbon-mediation/pull/745/files#diff-4873f9136db2279e0714fbf75dfbbd1aL51

Thanks

On Sat, Apr 1, 2017 at 5:15 PM, Indika Sampath  wrote:

> I was able to reproduce the above issue in ESB 5.0.0 with
> andes-client-3.2.6.jar (beta release) as well. Exception says
> org.apache.synapse.message.store.impl.commons.StorableMessage cannot be
> found by andes_client. Basically what we getting is ByteBuffer as a message
> and do not maintain any specific format. I wonder the issue regard to
> kernel change (4.4.15) in the latest version. We need to further look into
> the issue to identify the exact root cause. Public JIRA[1] create to track
> down the issue.
>
> [1] https://wso2.org/jira/browse/MB-1923
>
> On Sat, Apr 1, 2017 at 10:37 AM, Nandika Jayawardana 
> wrote:
>
>> Adding DEV
>>
>> Nandika
>>
>> On Fri, Mar 31, 2017 at 9:51 PM, Vijitha Ekanayake 
>> wrote:
>>
>>> Hi All,
>>>
>>> We Observe class loading issue with latest andes client (3.2.4) in MSMP
>>> scenarios. The issue occurs while consuming message from the message store
>>> where it continuously prints message[1]. I change the code a bit and got
>>> exact stack trace [2].It seems to be OSGI issue and this issue isn't there
>>> if we use previous andes client version(3.1.4).
>>>
>>> Did anyone come across this kind of OSGI issue before?
>>>
>>>
>>> [1].
>>>
>>> [2017-03-31 20:57:01,076] [EI-Core] ERROR - JmsConsumer
>>> [PaymentRequestJMSMessageStore-C-1] cannot receive message from store.
>>> Error:Could not deserialize message: java.lang.ClassNotFoundException:
>>> org.apache.synapse.message.store.impl.commons.StorableMessage cannot be
>>> found by andes_client_3.2.4_1.0.0
>>>
>>> [2].
>>> javax.jms.MessageFormatException: Could not deserialize message:
>>> java.lang.ClassNotFoundException: org.apache.synapse.message.sto
>>> re.impl.commons.StorableMessage cannot be found by
>>> andes_client_3.2.4_1.0.0
>>> at org.wso2.andes.client.message.JMSObjectMessage.getObject(JMS
>>> ObjectMessage.java:154)
>>> at org.apache.synapse.message.store.impl.jms.JmsConsumer.receiv
>>> e(JmsConsumer.java:99)
>>> at org.apache.synapse.message.processor.impl.sampler.SamplingSe
>>> rvice.fetch(SamplingService.java:188)
>>> at org.apache.synapse.message.processor.impl.sampler.SamplingSe
>>> rvice.execute(SamplingService.java:120)
>>> at org.wso2.carbon.mediation.ntask.NTaskAdapter.execute(NTaskAd
>>> apter.java:98)
>>> at org.wso2.carbon.ntask.core.impl.TaskQuartzJobAdapter.execute
>>> (TaskQuartzJobAdapter.java:67)
>>> at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>>> at java.util.concurrent.Executors$RunnableAdapter.call(Executor
>>> s.java:511)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
>>> Executor.java:1142)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
>>> lExecutor.java:617)
>>> at java.lang.Thread.run(Thread.java:745)
>>> Caused by: java.lang.ClassNotFoundException:
>>> org.apache.synapse.message.store.impl.commons.StorableMessage cannot be
>>> found by andes_client_3.2.4_1.0.0
>>> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInter
>>> nal(BundleLoader.java:501)
>>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(Bund
>>> leLoader.java:421)
>>> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(Bund
>>> leLoader.java:412)
>>> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loa
>>> dClass(DefaultClassLoader.java:107)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:348)
>>> at org.wso2.andes.client.util.ClassLoadingAwareObjectInputStrea
>>> m.load(ClassLoadingAwareObjectInputStream.java:64)
>>> at org.wso2.andes.client.util.ClassLoadingAwareObjectInputStrea
>>> m.resolveClass(ClassLoadingAwareObjectInputStream.java:38)
>>> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream
>>> .java:1613)
>>> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518)
>>> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStre
>>> am.java:1774)
>>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351)
>>> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371)
>>> at 

Re: [Dev] GSoC 2017 - Proposal 8: CLI tool for WSO2 API Manager

[Ayeshmantha Perera]

Hi All
I shared the draft proposal in the GSOC dashboard.Would be great and
appreciated if can review and provide a feed back on it

Thank you
Regards
Ayeshmantha

On Tue, Mar 7, 2017 at 1:28 PM, Ayeshmantha Perera 
wrote:

> Hi Pubudu
>
> Yeah already started going through the code and started some
> implementation regarding the Token generation task.Already up and run
> the  WSO2 API Manager 3.0.0-m1 which is based on Carbon 5(C5) and also went
> through some coding based on Go for CLI tool and also based on
> Go-Programming and can find the the CLI tool  worked on in [1] And the
> coding on go programming in [2] repos.
>
> [1] https://github.com/Akayeshmantha/GO_CLI_Practice
>
> [2] https://github.com/Akayeshmantha/Go_Practice
>
> Than you
> Best Regards
> Ayeshmantha
>
>
>
>
> On Mon, Mar 6, 2017 at 8:05 PM, Ayeshmantha Perera <
> akayeshman...@gmail.com> wrote:
>
>> Hi Pubudu
>>
>> Went through the basic key concepts of the WSO2 API Manager and went
>> through the token generation Documentation And the specification doc of
>> OAuth 2  protocol to get more idea on how it will be used in the task on
>> token generation.And went through the code of Dynamic client registration
>> class(dcr)[1] and .And yeah for the time been proposed a solution on Token
>> generation task [2].
>>
>> [1] https://github.com/wso2/carbon-apimgt/blob/master/compon
>> ents/apimgt/org.wso2.carbon.apimgt.rest.api.dcr/src/main/jav
>> a/org/wso2/carbon/apimgt/rest/api/dcr/web/impl/RegistrationS
>> erviceImpl.java#L12
>> 
>>
>> [2] http://gsocproposal8.blogspot.com/2017/02/task-4-key-gen
>> eration-solution-proposed.html
>>
>> Thank you
>> Best regards
>> Ayeshmantha
>>
>> On Wed, Mar 1, 2017 at 1:51 AM, Pubudu Gunatilaka 
>> wrote:
>>
>>> Hi Ayeshmantha,
>>>
>>> Thank you for your interest and good progress on the work.
>>>
>>> As you have some experience in using API Manager, you can also go
>>> through the API Manager concepts [1] and get familiar with them.
>>> Additionally, you can try out API export/import feature [2] and the API
>>> Manager 2.1.0 REST APIs [3] to tryout the product.
>>>
>>> Currently, WSO2 API Manager team is working on Carbon 5(C5) based API
>>> Manager implementation and you can find the relevant repos in [4] and [5].
>>> When you are developing the CLI, you should use the C5 REST APIs. API
>>> Manager team has already added most important REST APIs and we are working
>>> on adding new REST APIs based on the functionalities. Meantime, you can
>>> also get familiar with GO language and learn the concepts.
>>>
>>> As described in the project description you need to develop a CLI tool
>>> for API Manager. You can also check the available CLI tools and get an idea
>>> how you can develop the CLI in a more user-friendly way.
>>>
>>> [1] - https://docs.wso2.com/display/AM210/Key+Concepts
>>> [2] - https://docs.wso2.com/display/AM210/Migrating+the+APIs+to+a+
>>> Different+Environment
>>> [3] - https://docs.wso2.com/display/AM210/WSO2+APIs
>>> [4] - https://github.com/wso2/carbon-apimgt/tree/C5
>>> [5] - https://github.com/wso2/product-apim/tree/C5
>>>
>>> Thank you!
>>>
>>> On Wed, Mar 1, 2017 at 2:28 PM, Tharindu Edirisinghe >> > wrote:
>>>
 Hi Ayeshmantha,

 We are glad to see  your interest in doing GSoC with WSO2. I have added
 the mentors of the project here, so they will guide you for proceeding
 further.

 Best Regards,
 Tharindu Edirisinghe

 On Wed, Mar 1, 2017 at 1:25 PM, Ayeshmantha Perera <
 akayeshman...@gmail.com> wrote:

> Hi All,
>
> I'm Ayeshmantha Perera, from Sri Lanka Institute of Information
> Technology, currently studying in the final (4th) year specializing in
> Software Engineering.
>
> I am interested in taking part in GSoC 2017 with WSO2 and and hope to
> apply for the CLI tool on API Manager.
>
> I have been following up the work done by the API Manager team of WSO2
> and went through the webinars that was handled by WSO2 API Manager team.
>
> I have experienced  working on WSO2 API Manager in my previous working
> experience as an Intern.And I'm experienced on WSO2 ESB and Also the WSO2
> Data analytics server also.
>
> Other than the experience on the products I have experience on working
> with Go lang ,Java EE ,Maven,Git,OAuth2 protocol,JAX-RS,Spring
> ,Hibernater.And I have 1 year experience on Node.js development, with
> Meanstack 1 and Meanstack 2 and Also With React , Redux , Reactive
> Programming and Android, Cross platform(React native ,Native Base.IO ,
> Native Script , Ionic 2 ) And also I have more than 2 year experience on
> working with .Net(Web pages , MVC , WEB API).
> 

Re: [Dev] [GSoC 2017][IS] SCIM 2.0 Compliance Test Suite

[Vindula Jayawardana]

Hi,

I shared my draft proposal in GSoC dashboard and I kindly request your
feedback in improving the proposal.

Thank you,

*Vindula Jayawardana*
Computer Science and Engineering Dept.
University of Moratuwa
mobile : +713462554
Email : vindul...@gmail.com






*“Respect is how to treat everyone, not just those you want to impress. "*


*-Richard Branson-*



On 30 March 2017 at 23:13, Vindula Jayawardana 
wrote:

> Hi,
>
> As mentioned above, I looked at the SCIM 1.1 compliance test suite [1].
> Due to the reason that the SCIM 1.1 test suite requires an internet facing
> SCIM 1.1 server to run the tests against, I setup-ed an Identity Server
> instance in AWS [2]. However when the test are run, it fails due to
> /ServiceProviderConfigs and /Schemas endpoints. As WSO2 SCIM 1.1 support
> [3] is not covering the mentioned two endpoints, tests are failing when
> run.
>
> However in order to get an idea on how the result representation had been
> done in SCIM 1.1 compliance test suit, I mocked the /ServiceProviderConfigs
> endpoint [4] and was able to get the following output.
>
>
> ​
>
> Due to the complexity of mocking the /Schemas endpoint and also as the
> test on one endpoint ( /ServiceProviderConfigs) could give the nature of
> the result representation as seen above, I did not try to mock /Schemas
> endpoint and run the test suit again. However I tried by mocking the
> endpoint with 501 NOT IMPLEMENTED [5] as the output, but that was not
> accepted by the test suit as a valid return object.
>
> However, in my opinion, the SCIM test suit should be flexible in nature to
> skip any test which was given the input from the SCIM server as 501 NOT
> IMPLEMENTED [5]. I encourage such kind of implementation to be adopted in
> the proposed SCIM 2.0 compliance test suit as in that way the test suit
> acknowledges the SP's inability to provide those endpoints while making
> sure such kind of inability does not compromise the ability to run the test
> suit on other endpoints.
>
> [1] - http://www.simplecloud.info/#complianceTest
> [2] - https://aws.amazon.com/
> [3] - https://github.com/wso2/charon/tree/release-2.0.7
> [4] - https://github.com/Vindulamj/mocked-identity-
> inbound-provisioning-scim/tree/master/identity-inbound-
> provisioning-scim-master
> [5] - http://www.simplecloud.info/specs/draft-scim-api-01.html#anchor6
>
> *Vindula Jayawardana*
> Computer Science and Engineering Dept.
> University of Moratuwa
> mobile : +713462554
> Email : vindul...@gmail.com
>
> 
> 
> 
> 
>
> *“Respect is how to treat everyone, not just those you want to impress. "*
>
>
> *-Richard Branson-*
>
>
>
> On 10 March 2017 at 16:42, Vindula Jayawardana 
> wrote:
>
>> Hi,
>>
>> Thank you very much for the prompt replies. I will look into the points
>> you have mentioned and will keep you updated here.
>>
>> Thank you.
>>
>> *Vindula Jayawardana*
>> Computer Science and Engineering Dept.
>> University of Moratuwa
>> mobile : +713462554
>> Email : vindul...@gmail.com
>>
>> 
>> 
>> 
>> 
>>
>> *“Respect is how to treat everyone, not just those you want to impress. "*
>>
>>
>> *-Richard Branson-*
>>
>>
>>
>> On 9 March 2017 at 21:22, Omindu Rathnaweera  wrote:
>>
>>> Hi Vindula,
>>>
>>> If we can run the existing 1.1 test on IS and see the generated output,
>>> that will be a good point to start. However we'll need to host an IS
>>> instance publicly to run the tests on it.
>>>
>>> Regards,
>>> Omindu.
>>>
>>>
>>>
>>> On Thu, Mar 9, 2017 at 8:52 PM, Gayan Gunawardana 
>>> wrote:
>>>
 Hi Vindula,

 Thanks for your interest in this project.
 Since you have good knowledge about SCIM 2.0 specifications, could you
 please look at SCIM 1.1 compliance test and source code [1]. SCIM 2.0
 compliance test doesn't need to be same as SCIM 1.1 just get an idea from
 SCIM 1.1 compliance test. Further you can extract test scenarios from [2]
 as well.

 [1]https://github.com/erdtman/simplecloud.info
 
 [2]https://github.com/wso2-extensions/identity-inbound-provi
 sioning-scim2/tree/master/tests

 Thanks,
 Gayan

 On Thu, Mar 9, 2017 at 7:51 PM, Vindula Jayawardana <
 vindula...@cse.mrt.ac.lk> wrote: