Re: [Dev] [DEV] Implement unit/integration test cases for API Manager JAX-RS Rest API

[Nuwan Dias]

Is it right to auto-generate the test client code? IMO one objective of
this should be to make sure the REST APIs don't change across patch
releases, etc. If we auto-generate the test stubs we would loose that
advantage.

Thanks,
NuwanD.

On Mon, Oct 19, 2015 at 12:26 PM, Joseph Fonseka  wrote:

> Hi Sanjeewa
>
> Saneth & I had an offline chat regarding this last week there are few
> things we need to consider.
>
> 1. Generating integration test for the Jax-RS functionality ex . If crud
> operations work, if it returns correct error messages.
>  -  We can use swagger-codegen to do this.
>  -  API Definition has all the details of the API interface what
> missing are the data fixtures.
>  - There are few options with the fixtures which we can auto
> generate since the schema of the model is there or we can use a predefined
> set of json files.
>
> 2. How to get the existing integration test to utilize the new API.
>  - We already have a lot of integration tests which uses existing
> store & publisher APIs to add/remove resources. As Saneth mention they have
> written it in a layered architecture this replacing the existing API layer
> with Jax-rs existing test should work.
>  - We might have to look at this in the next phase when we plan to
> deprecate the existing APIs.
>
> 3. How to make it easy to write test in the future with Jax-Rs API.
>  - Ex Creating a Jax-rs client/library to utilize by other
> integration test.
>
> Thanks & Regards
> Jo
>
> On Mon, Oct 19, 2015 at 12:17 PM, Joseph Fonseka  wrote:
>
>> Sorry mail got sent accidentally half written. will complete and send
>> shortly.
>>
>> On Mon, Oct 19, 2015 at 12:15 PM, Joseph Fonseka  wrote:
>>
>>> Hi Sanjeewa
>>>
>>> Saneth & I had an offline chat regarding this last week there are few
>>> things we need to consider.
>>>
>>> 1. Generating integration test for the Jax-RS functionality ex . If crud
>>> operations work, if it returns correct error messages.
>>>  -  We can use swagger-codegen to do this.
>>>  API Definition has all the details of the API interface what missing
>>> are
>>>
>>> 2. How to get the existing integration test to utilize the new API.
>>>  - We already have a lot of integration tests which uses
>>> existing store & publisher APIs to add/remove resources. As Saneth mention
>>> they have written it in a layered architecture this replacing the existing
>>> API layer with Jax-rs existing test should work.
>>>
>>>
>>> 3. How to make it easy to write test in the future with Jax-Rs API.
>>>
>>>
>>>
>>>
>>> On Mon, Oct 19, 2015 at 11:39 AM, Sanjeewa Malalgoda 
>>> wrote:
>>>
 Hi Team,
 We are planning to implement complete REST API for all operations
 available in API Manager.
 This will be CXF based jax-rs application.
 This application based on swagger template and service skeleton
 automatically generate according to swagger to cxf implementation done by
 Jo.
 We would like to know what would be the best approach to implement test
 for this service.
 Do we have any mechanism to generate client and test service in unit
 test level ? I can see there are projects to generate java client based on
 swagger content.
 Or do we need to write integration test to run this application in
 server and perform tests?
 Since this implementation changes rapidly it would be ideal if we can
 have skeleton based testing approach without binding to real
 implementation(like auto generated client).

 Have we done something similar?
 What would be the best approach?

 Thanks,
 sanjeewa.

 --

 *Sanjeewa Malalgoda*
 WSO2 Inc.
 Mobile : +94713068779

 blog
 :http://sanjeewamalalgoda.blogspot.com/
 



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


>>>
>>>
>>> --
>>>
>>> --
>>> *Joseph Fonseka*
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 772 512 430
>>> skype: jpfonseka
>>>
>>> * *
>>>
>>>
>>
>>
>> --
>>
>> --
>> *Joseph Fonseka*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 772 512 430
>> skype: jpfonseka
>>
>> * *
>>
>>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * *
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Nuwan Dias

Technical Lead - WSO2, Inc. http://wso2.com
email : nuw...@wso2.com
Phone : +94 777 775 729
___
Dev mailing list
De

Re: [Dev] [DEV] Implement unit/integration test cases for API Manager JAX-RS Rest API

[Joseph Fonseka]

Hi Sanjeewa

Saneth & I had an offline chat regarding this last week there are few
things we need to consider.

1. Generating integration test for the Jax-RS functionality ex . If crud
operations work, if it returns correct error messages.
 -  We can use swagger-codegen to do this.
 -  API Definition has all the details of the API interface what
missing are the data fixtures.
 - There are few options with the fixtures which we can auto
generate since the schema of the model is there or we can use a predefined
set of json files.

2. How to get the existing integration test to utilize the new API.
 - We already have a lot of integration tests which uses existing
store & publisher APIs to add/remove resources. As Saneth mention they have
written it in a layered architecture this replacing the existing API layer
with Jax-rs existing test should work.
 - We might have to look at this in the next phase when we plan to
deprecate the existing APIs.

3. How to make it easy to write test in the future with Jax-Rs API.
 - Ex Creating a Jax-rs client/library to utilize by other
integration test.

Thanks & Regards
Jo

On Mon, Oct 19, 2015 at 12:17 PM, Joseph Fonseka  wrote:

> Sorry mail got sent accidentally half written. will complete and send
> shortly.
>
> On Mon, Oct 19, 2015 at 12:15 PM, Joseph Fonseka  wrote:
>
>> Hi Sanjeewa
>>
>> Saneth & I had an offline chat regarding this last week there are few
>> things we need to consider.
>>
>> 1. Generating integration test for the Jax-RS functionality ex . If crud
>> operations work, if it returns correct error messages.
>>  -  We can use swagger-codegen to do this.
>>  API Definition has all the details of the API interface what missing are
>>
>> 2. How to get the existing integration test to utilize the new API.
>>  - We already have a lot of integration tests which uses existing
>> store & publisher APIs to add/remove resources. As Saneth mention they have
>> written it in a layered architecture this replacing the existing API layer
>> with Jax-rs existing test should work.
>>
>>
>> 3. How to make it easy to write test in the future with Jax-Rs API.
>>
>>
>>
>>
>> On Mon, Oct 19, 2015 at 11:39 AM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> Hi Team,
>>> We are planning to implement complete REST API for all operations
>>> available in API Manager.
>>> This will be CXF based jax-rs application.
>>> This application based on swagger template and service skeleton
>>> automatically generate according to swagger to cxf implementation done by
>>> Jo.
>>> We would like to know what would be the best approach to implement test
>>> for this service.
>>> Do we have any mechanism to generate client and test service in unit
>>> test level ? I can see there are projects to generate java client based on
>>> swagger content.
>>> Or do we need to write integration test to run this application in
>>> server and perform tests?
>>> Since this implementation changes rapidly it would be ideal if we can
>>> have skeleton based testing approach without binding to real
>>> implementation(like auto generated client).
>>>
>>> Have we done something similar?
>>> What would be the best approach?
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>> blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>> 
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> --
>> *Joseph Fonseka*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 772 512 430
>> skype: jpfonseka
>>
>> * *
>>
>>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * *
>
>


-- 

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

mobile: +94 772 512 430
skype: jpfonseka

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

Re: [Dev] [DEV] Implement unit/integration test cases for API Manager JAX-RS Rest API

[Dharshana Warusavitharana]

Hi Jo,

As per the practise we followed there won't be a big effort in migrating
these tests since we use base test methods to use these API calls. So we
can handle this without changing tests.

Thank you,
Dharshana.


On Mon, Oct 19, 2015 at 12:17 PM, Joseph Fonseka  wrote:

> Sorry mail got sent accidentally half written. will complete and send
> shortly.
>
> On Mon, Oct 19, 2015 at 12:15 PM, Joseph Fonseka  wrote:
>
>> Hi Sanjeewa
>>
>> Saneth & I had an offline chat regarding this last week there are few
>> things we need to consider.
>>
>> 1. Generating integration test for the Jax-RS functionality ex . If crud
>> operations work, if it returns correct error messages.
>>  -  We can use swagger-codegen to do this.
>>  API Definition has all the details of the API interface what missing are
>>
>> 2. How to get the existing integration test to utilize the new API.
>>  - We already have a lot of integration tests which uses existing
>> store & publisher APIs to add/remove resources. As Saneth mention they have
>> written it in a layered architecture this replacing the existing API layer
>> with Jax-rs existing test should work.
>>
>>
>> 3. How to make it easy to write test in the future with Jax-Rs API.
>>
>>
>>
>>
>> On Mon, Oct 19, 2015 at 11:39 AM, Sanjeewa Malalgoda 
>> wrote:
>>
>>> Hi Team,
>>> We are planning to implement complete REST API for all operations
>>> available in API Manager.
>>> This will be CXF based jax-rs application.
>>> This application based on swagger template and service skeleton
>>> automatically generate according to swagger to cxf implementation done by
>>> Jo.
>>> We would like to know what would be the best approach to implement test
>>> for this service.
>>> Do we have any mechanism to generate client and test service in unit
>>> test level ? I can see there are projects to generate java client based on
>>> swagger content.
>>> Or do we need to write integration test to run this application in
>>> server and perform tests?
>>> Since this implementation changes rapidly it would be ideal if we can
>>> have skeleton based testing approach without binding to real
>>> implementation(like auto generated client).
>>>
>>> Have we done something similar?
>>> What would be the best approach?
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>> --
>>>
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>> blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>> 
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>>
>> --
>> *Joseph Fonseka*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 772 512 430
>> skype: jpfonseka
>>
>> * *
>>
>>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * *
>
>


-- 

Dharshana Warusavitharana
Senior Software Engineer , Test Automation
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
Tel  : +94 11 214 5345
Fax :+94 11 2145300
cell : +94770342233
blog : http://dharshanaw.blogspot.com

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

Re: [Dev] [DEV] Implement unit/integration test cases for API Manager JAX-RS Rest API

[Joseph Fonseka]

Sorry mail got sent accidentally half written. will complete and send
shortly.

On Mon, Oct 19, 2015 at 12:15 PM, Joseph Fonseka  wrote:

> Hi Sanjeewa
>
> Saneth & I had an offline chat regarding this last week there are few
> things we need to consider.
>
> 1. Generating integration test for the Jax-RS functionality ex . If crud
> operations work, if it returns correct error messages.
>  -  We can use swagger-codegen to do this.
>  API Definition has all the details of the API interface what missing are
>
> 2. How to get the existing integration test to utilize the new API.
>  - We already have a lot of integration tests which uses existing
> store & publisher APIs to add/remove resources. As Saneth mention they have
> written it in a layered architecture this replacing the existing API layer
> with Jax-rs existing test should work.
>
>
> 3. How to make it easy to write test in the future with Jax-Rs API.
>
>
>
>
> On Mon, Oct 19, 2015 at 11:39 AM, Sanjeewa Malalgoda 
> wrote:
>
>> Hi Team,
>> We are planning to implement complete REST API for all operations
>> available in API Manager.
>> This will be CXF based jax-rs application.
>> This application based on swagger template and service skeleton
>> automatically generate according to swagger to cxf implementation done by
>> Jo.
>> We would like to know what would be the best approach to implement test
>> for this service.
>> Do we have any mechanism to generate client and test service in unit test
>> level ? I can see there are projects to generate java client based on
>> swagger content.
>> Or do we need to write integration test to run this application in server
>> and perform tests?
>> Since this implementation changes rapidly it would be ideal if we can
>> have skeleton based testing approach without binding to real
>> implementation(like auto generated client).
>>
>> Have we done something similar?
>> What would be the best approach?
>>
>> Thanks,
>> sanjeewa.
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>> blog
>> :http://sanjeewamalalgoda.blogspot.com/
>> 
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * *
>
>


-- 

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

mobile: +94 772 512 430
skype: jpfonseka

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

Re: [Dev] finding the buying pattern of consumer store data.

[Fazlan Nazeem]

Hi Nifras.

If you have successfully built the model using the Machine Learner with a
suitable algorithm, you can use the model for prediction. Different ways of
using the model are listed in the documentation page[1] . The pattern is
stored within the model, and you can use this pattern for prediction.

[1] https://docs.wso2.com/display/ML100/Using+Models




On Mon, Oct 19, 2015 at 10:11 AM, NIFRAS ISMAIL 
wrote:

> Hi Machine Learners,
> I have to find the buying pattern of stored data. I am using WSO2 ML and
> get the model. From the model how do i get the buying pattern any ideas? or
> research paper like materials.
>
> Thanks
>
> Regards.
> *M. Nifras Ismail*
> [image: LinkedIn] 
>
>
>
> ___
> 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] [DEV] Implement unit/integration test cases for API Manager JAX-RS Rest API

[Dharshana Warusavitharana]

Hi Sanjeewa,

Currently we are not using a mechanism to proceed testing with auto
generated clients. As I understand by the requirement this might subject to
change API definition posted by the application with changes in the product
level.

But as per the requirement I think it would be ideal if we can follow an
approach to add both unit tests and integration tests for the scenario.

Currently we are using simple CXF application to monitor API and Sample
applications used by integration tests to verify its  state of deployment.
In this case we just deploy the webapp and invoke it inside test methods.
Which is bit similar to what you are doing here. In this we deploy
out cxf application in APIM itself. So in your case also we do not need
additional application container to move on.

As I see we can follow same approach we are doing with service stubs. In
build time we can generate client using WADL -> Java or swagger ->  java
approach and use it inside tests. This will illuminate effort in redoing
all tests while API definition is changed.

Thank you,
Dharshana.


On Mon, Oct 19, 2015 at 12:15 PM, Joseph Fonseka  wrote:

> Hi Sanjeewa
>
> Saneth & I had an offline chat regarding this last week there are few
> things we need to consider.
>
> 1. Generating integration test for the Jax-RS functionality ex . If crud
> operations work, if it returns correct error messages.
>  -  We can use swagger-codegen to do this.
>  API Definition has all the details of the API interface what missing are
>
> 2. How to get the existing integration test to utilize the new API.
>  - We already have a lot of integration tests which uses existing
> store & publisher APIs to add/remove resources. As Saneth mention they have
> written it in a layered architecture this replacing the existing API layer
> with Jax-rs existing test should work.
>
>
> 3. How to make it easy to write test in the future with Jax-Rs API.
>
>
>
>
> On Mon, Oct 19, 2015 at 11:39 AM, Sanjeewa Malalgoda 
> wrote:
>
>> Hi Team,
>> We are planning to implement complete REST API for all operations
>> available in API Manager.
>> This will be CXF based jax-rs application.
>> This application based on swagger template and service skeleton
>> automatically generate according to swagger to cxf implementation done by
>> Jo.
>> We would like to know what would be the best approach to implement test
>> for this service.
>> Do we have any mechanism to generate client and test service in unit test
>> level ? I can see there are projects to generate java client based on
>> swagger content.
>> Or do we need to write integration test to run this application in server
>> and perform tests?
>> Since this implementation changes rapidly it would be ideal if we can
>> have skeleton based testing approach without binding to real
>> implementation(like auto generated client).
>>
>> Have we done something similar?
>> What would be the best approach?
>>
>> Thanks,
>> sanjeewa.
>>
>> --
>>
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>> blog
>> :http://sanjeewamalalgoda.blogspot.com/
>> 
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> --
> *Joseph Fonseka*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 772 512 430
> skype: jpfonseka
>
> * *
>
>


-- 

Dharshana Warusavitharana
Senior Software Engineer , Test Automation
WSO2 Inc. http://wso2.com
email : dharsha...@wso2.com 
Tel  : +94 11 214 5345
Fax :+94 11 2145300
cell : +94770342233
blog : http://dharshanaw.blogspot.com

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

Re: [Dev] [DEV] Implement unit/integration test cases for API Manager JAX-RS Rest API

[Joseph Fonseka]

Hi Sanjeewa

Saneth & I had an offline chat regarding this last week there are few
things we need to consider.

1. Generating integration test for the Jax-RS functionality ex . If crud
operations work, if it returns correct error messages.
 -  We can use swagger-codegen to do this.
 API Definition has all the details of the API interface what missing are

2. How to get the existing integration test to utilize the new API.
 - We already have a lot of integration tests which uses existing
store & publisher APIs to add/remove resources. As Saneth mention they have
written it in a layered architecture this replacing the existing API layer
with Jax-rs existing test should work.


3. How to make it easy to write test in the future with Jax-Rs API.




On Mon, Oct 19, 2015 at 11:39 AM, Sanjeewa Malalgoda 
wrote:

> Hi Team,
> We are planning to implement complete REST API for all operations
> available in API Manager.
> This will be CXF based jax-rs application.
> This application based on swagger template and service skeleton
> automatically generate according to swagger to cxf implementation done by
> Jo.
> We would like to know what would be the best approach to implement test
> for this service.
> Do we have any mechanism to generate client and test service in unit test
> level ? I can see there are projects to generate java client based on
> swagger content.
> Or do we need to write integration test to run this application in server
> and perform tests?
> Since this implementation changes rapidly it would be ideal if we can have
> skeleton based testing approach without binding to real implementation(like
> auto generated client).
>
> Have we done something similar?
> What would be the best approach?
>
> Thanks,
> sanjeewa.
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 

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

mobile: +94 772 512 430
skype: jpfonseka

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

Re: [Dev] [DEV] Implement unit/integration test cases for API Manager JAX-RS Rest API

[Sanjeewa Malalgoda]

On Mon, Oct 19, 2015 at 11:39 AM, Sanjeewa Malalgoda 
wrote:

> Hi Team,
> We are planning to implement complete REST API for all operations
> available in API Manager.
> This will be CXF based jax-rs application.
> This application based on swagger template and service skeleton
> automatically generate according to swagger to cxf implementation done by
> Jo.
> We would like to know what would be the best approach to implement test
> for this service.
> Do we have any mechanism to generate client and test service in unit test
> level ? I can see there are projects to generate java client based on
> swagger content.
> Or do we need to write integration test to run this application in server
> and perform tests?
> Since this implementation changes rapidly it would be ideal if we can have
> skeleton based testing approach without binding to real implementation(like
> auto generated client).
>
> Have we done something similar?
> What would be the best approach?
>
> Thanks,
> sanjeewa.
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
> blog
> :http://sanjeewamalalgoda.blogspot.com/
> 
>
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.blogspot.com/

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

[Dev] [DEV] Implement unit/integration test cases for API Manager JAX-RS Rest API

[Sanjeewa Malalgoda]

Hi Team,
We are planning to implement complete REST API for all operations available
in API Manager.
This will be CXF based jax-rs application.
This application based on swagger template and service skeleton
automatically generate according to swagger to cxf implementation done by
Jo.
We would like to know what would be the best approach to implement test for
this service.
Do we have any mechanism to generate client and test service in unit test
level ? I can see there are projects to generate java client based on
swagger content.
Or do we need to write integration test to run this application in server
and perform tests?
Since this implementation changes rapidly it would be ideal if we can have
skeleton based testing approach without binding to real implementation(like
auto generated client).

Have we done something similar?
What would be the best approach?

Thanks,
sanjeewa.

-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

blog
:http://sanjeewamalalgoda.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.2 RC3

[Rajith Vitharana]

Hi,

Tested with DSS basic scenarios
1 - deploying car scenario
2 - invoking simple service
3 - invoking simple rest service (with post body content - which doesn't
work in kernel 4.4.1)

+1 to release

Thanks,

On Mon, Oct 19, 2015 at 10:45 AM, Manuri Amaya Perera 
wrote:

> Hi Maduranga,
>
> If you need to use the bundle exported by kernel you'll have to use the
> version exported by kernel which is 0.0.0.
>
> Was it working it 4.4.1? But, as this is a framework package we have not
> changed anything.
>
>
> Thank you.
>
>
>
> On Sat, Oct 17, 2015 at 1:21 PM, Maduranga Siriwardena  > wrote:
>
>> Hi Manuri,
>>
>> When building IS 5.1.0 master branch with kernel 4.4.2 RC3, we got error
>> at [1]. It searches for javax.xml.parsers in the version
>> range [1.3.0,2.0.0). Currently we haven't specified the version for
>> javax.xml.parsers in our Import-Packages in carbon-identity. But after
>> defining the Import-Package version range to [0.0.0,1.0.0), it builds okay.
>> We get this error only when using kernel 4.4.2. Do we need to explicitly
>> specify the javax.xml.parsers version?
>>
>> [1] https://gist.github.com/madurangasiriwardena/5d118b4323ecd41e53bb
>>
>> Thanks,
>> Maduranga
>>
>> On Fri, Oct 16, 2015 at 11:20 PM, Manuri Amaya Perera 
>> wrote:
>>
>>> Hi Devs,
>>>
>>> WSO2 Carbon Kernel 4.4.2 RC3 Release Vote.
>>>
>>> This release fixes the following issues:
>>> https://wso2.org/jira/issues/?filter=12396
>>>
>>> Please download and test your products with kernel 4.4.2 RC3 and vote.
>>> Vote will be open for 72 hours or longer as needed.
>>>
>>> *​Source and binary distribution files:*
>>> http://svn.wso2.org/repos/wso2/people/kalpaw/wso2carbon-4.4.2/
>>>
>>> *Maven staging repository:*
>>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-020/
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/carbon-kernel/tree/v4.4.2-rc3
>>>
>>> [ ] Broken - do not release (explain why)
>>> [ ] Stable - go ahead and release
>>>
>>>
>>> Thank you
>>> Carbon Team
>>>
>>> --
>>>
>>> *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
>>>
>>>
>>
>>
>> --
>> Maduranga Siriwardena
>> Software Engineer
>> WSO2 Inc.
>>
>> email: madura...@wso2.com
>> mobile: +94718990591
>>
>
>
>
> --
>
> *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
>
>


-- 
Rajith Vitharana

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

Re: [Dev] [APIM] [OSGI] Removal of dynamic imports causes CNF on extention points

[Kishanthan Thangarajah]

On Fri, Oct 16, 2015 at 4:31 PM, Shani Ranasinghe  wrote:

>
> Hi,
>
> In APIM current code (1.10), we have removed the  >* from all packages at the moment.
>
> We faced an issue now, where an extension point would not work with this
> change. i.e. if we put a external jar into the
> /repository/components/lib folder, that class will not be picked
> up by the component OSGI bundle because of the aforementioned reason.
>
> Discussing with KasunG, I learned that we cannot remove the 
> DynamicImport-Package
> statement, if the components use Class.forName() or 
> .class.getClassLoader().loadClass();
> because the OSGI bundle would not be able to identify the external class.
>
> As a possible solution, what we thought of is, to move the Class.forName()
> to a central location, possibily to the org.wso2.carbon.apimgt.impl
> package, and have the
> * to that package. Then
> all other packages that used to have the Class.forName() can be referred to
> the method introduced in the org.wso2.carbon.apimgt.impl package.
>
> @KasunG, Kishanthan, is this the correct approach?
>

This will not work. DynamicImport-Package :   (or
org.wso2.carbon.apimgt.impl) means, you do not know that this package will
be available at runtime in advance so that bundle resolution process will
not take this package into account when resolving the bundle import
statements. It will only try to resolve this package when it is requested
to be loaded.

For packages (mostly if its extensions) we will not know the package name
in advance too, and for situations like this we will have to use the "*"
with dynamic import. We do not have any other ways to solve this when
loading classes using Class.forName and we do not know the package names in
advance.


> Are there any other approaches that we could look into?
> --
> Thanks and Regards
> *,Shani Ranasinghe*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273555
> Blog: http://waysandmeans.blogspot.com/
> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>



-- 
*Kishanthan Thangarajah*
Associate Technical Lead,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com *
Twitter - *http://twitter.com/kishanthan *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.2 RC3

[Manuri Amaya Perera]

Hi Maduranga,

If you need to use the bundle exported by kernel you'll have to use the
version exported by kernel which is 0.0.0.

Was it working it 4.4.1? But, as this is a framework package we have not
changed anything.


Thank you.



On Sat, Oct 17, 2015 at 1:21 PM, Maduranga Siriwardena 
wrote:

> Hi Manuri,
>
> When building IS 5.1.0 master branch with kernel 4.4.2 RC3, we got error
> at [1]. It searches for javax.xml.parsers in the version
> range [1.3.0,2.0.0). Currently we haven't specified the version for
> javax.xml.parsers in our Import-Packages in carbon-identity. But after
> defining the Import-Package version range to [0.0.0,1.0.0), it builds okay.
> We get this error only when using kernel 4.4.2. Do we need to explicitly
> specify the javax.xml.parsers version?
>
> [1] https://gist.github.com/madurangasiriwardena/5d118b4323ecd41e53bb
>
> Thanks,
> Maduranga
>
> On Fri, Oct 16, 2015 at 11:20 PM, Manuri Amaya Perera 
> wrote:
>
>> Hi Devs,
>>
>> WSO2 Carbon Kernel 4.4.2 RC3 Release Vote.
>>
>> This release fixes the following issues:
>> https://wso2.org/jira/issues/?filter=12396
>>
>> Please download and test your products with kernel 4.4.2 RC3 and vote.
>> Vote will be open for 72 hours or longer as needed.
>>
>> *​Source and binary distribution files:*
>> http://svn.wso2.org/repos/wso2/people/kalpaw/wso2carbon-4.4.2/
>>
>> *Maven staging repository:*
>> http://maven.wso2.org/nexus/content/repositories/orgwso2carbon-020/
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/carbon-kernel/tree/v4.4.2-rc3
>>
>> [ ] Broken - do not release (explain why)
>> [ ] Stable - go ahead and release
>>
>>
>> Thank you
>> Carbon Team
>>
>> --
>>
>> *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
>>
>>
>
>
> --
> Maduranga Siriwardena
> Software Engineer
> WSO2 Inc.
>
> email: madura...@wso2.com
> mobile: +94718990591
>



-- 

*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

[Dev] finding the buying pattern of consumer store data.

[NIFRAS ISMAIL]

Hi Machine Learners,
I have to find the buying pattern of stored data. I am using WSO2 ML and
get the model. From the model how do i get the buying pattern any ideas? or
research paper like materials.

Thanks

Regards.
*M. Nifras Ismail*
[image: LinkedIn] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [jaggery] Where should I Report Issues in IDEA Jaggery Plugin?

[Godwin Amila Shrimal]

Adding [Manu]

On Mon, Oct 19, 2015 at 9:05 AM, Chamila Wijayarathna 
wrote:

> Hi all,
>
> I have installed jaggery plugin in IDEA 14.1.3. I observed following
> suggestion which is not spelled correctly.
>
> [image: Inline image 1]
>
> Correct function which is supported is "isDebugEnabled", but here it shows
> "isDebugEnabeld".
>
> At where should I report this issue?
>
> Thank You!
>
> --
> *Chamila Dilshan Wijayarathna,*
> Software Engineer
> Mobile:(+94)788193620
> WSO2 Inc., http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.2 RC2

[Aruna Karunarathna]

On Mon, Oct 19, 2015 at 9:32 AM, Hasanthi Purnima Dissanayake <
hasan...@wso2.com> wrote:

> Hi Kishanthan,
> Please find the requested information for [1] as a jira attchement. Please
> consider that I observed this issue only when both proxy context path and
> web context root is enabled as I mentioned in the JIRA.
>

Hi Johann, Hasanthi,

AFAIU the configuration you are using is wrong when using WebContext and
the ProxyContextpath both.

You need to add the *proxy cookie rewrite* URL paths in order to work
correctly. Try adding those parameters.

Regards,
Aruna


>
> [1] https://wso2.org/jira/browse/CARBON-15475
>
> Thanks
>
> Hasanthi Dissanayake
>
> Software Engineer | WSO2
>
> E: hasan...@wso2.com 
> M :0718407133| http://wso2.com 
>
> On Fri, Oct 16, 2015 at 2:38 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>>
>>
>> On Fri, Oct 16, 2015 at 11:27 AM, Johann Nallathamby 
>> wrote:
>>
>>> Hi Kishanthan/Kernel Team,
>>>
>>> We have added the test case as well to the same PR.
>>>
>>
>> Thanks Johann.
>>
>> @MB Team, could you guys verify that all your scenarios are now
>> passing?.  We will start the next RC build once this is confirmed ASAP.
>>
>>>
>>> Also can we get CARBON-15505 merged? The PR for master is a very old PR
>>> which we have missed to review and merge. This mainly contains some
>>> reordering of fields in the UI to make it more consistent and reorder
>>> properties in user-mgt.xml to be consistent with UI. Hope we don't need any
>>> tests for this.
>>>
>>
>> I think its better not to add any more changes at this stage. We will
>> merge this for next patch release.
>>
>>>
>>> Any update on the 3 issues raised above ?
>>>
>>
>> For [1], we need more information to reproduce (LB & IS config, example
>> requests, HTTP access logs on both LB and IS side with this issue). Will
>> send a separate mail on that, but I believe its not a blocker for the IS
>> release right?
>> [2] and [3], we haven't seen this error previously and according the
>> trace, it looks like the "distributedCache" instance is becoming null in
>> CacheImpl class. If the exact steps can be found or given on how to
>> reproduce this, then we can work on finding the root cause for this.
>>
>>
>>> Thanks,
>>> Johann.
>>>
>>> On Thu, Oct 15, 2015 at 3:30 PM, Johann Nallathamby 
>>> wrote:
>>>
 Hi Kishanthan/Kernel Team,

 We are in the process writing the test case for the issue. Should be
 able to send it before end of day.

 [1] has been reported in another thread. This issue in particular looks
 critical to me, because AFAIK there are many users using proxyContextPath.
 Not sure about WebContextRoot though. Apart from that WSO2 QA has reported
 [2,3] in IS 5.1.0 SNAPSHOT pack. May be its harmless, but looks like it is
 coming from kernel and would like to get your thoughts on this if this is
 critical and needs to be fixed.

 [1] https://wso2.org/jira/browse/CARBON-15475
 [2] https://wso2.org/jira/browse/IDENTITY-3815
 [3] https://wso2.org/jira/browse/IDENTITY-3817

 And also it will be great if we can change the default value of
 XSSPreventionConfig.Enabled to 'false' because this was added in order to
 prevent XSS centrally, however the approach is not 100% bug free. Whoever
 has this enabled needs to test all their functionality well. Therefore what
 I suggest is to make it 'false' by default and whatever product that needs
 it can enable it at product level. WDYT ? Can we do this ?

 Regards,
 Johann.


 On Wed, Oct 14, 2015 at 6:30 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> Can we also have test case for this fix please?
>
> On Wed, Oct 14, 2015 at 6:13 PM, Isura Karunaratne 
> wrote:
>
>> Hi,
>>
>> This issue is fixed in [1].
>>
>>
>> Thanks
>> isura
>>
>>
>> [1] https://wso2.org/jira/browse/CARBON-15517
>>
>>
>> On Wed, Oct 14, 2015 at 11:25 AM, Johann Nallathamby > > wrote:
>>
>>> Hi Isura,
>>>
>>> Can you look into this issue urgently. I remember you fixing an
>>> issue related to this.
>>>
>>> Thanks.
>>>
>>> On Wed, Oct 14, 2015 at 7:16 AM, Indika Sampath 
>>> wrote:
>>>
 Hi All,

 I debug code of our and found issue. It seems implementation of
 some API changed in user-core. Let me explain the flow.

 Our queue/topic creation has two call.

 1. We create internal role when adding queue and assign
 "changePermission", "publish", "consume"  permissions to it. Which 
 means
 that, user who created particular queue can update permission, publish 
 or
 consume.

 - Below code line used to get internal role name:

 UserCoreUtil.addInternalDomainName(QUEUE_ROLE_PREFIX +
 queueName.replace("."

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.2 RC2

[Johann Nallathamby]

Hi Pandula,

AFAIK I have seen users using both of these configurations separately, but
not often together. So in that sense I don't think it should be considered
a blocker. This is just my opinion.

Thanks.

On Fri, Oct 16, 2015 at 8:34 PM, Pandula Kariyawasam 
wrote:

> Hi Johann,
>
> Still we are working on to identify the correct nginx config for this
> scenario.
>
> From the QA perspective, we need to get this issue fixed, because if there
> is a customer who will use this scenario, we will end up with a support
> patch.
>
> So, either need to get this fixed on 4.4.2 or have to wait for a fix on
> 4.4.3.
>
> WDYT?
>
> Thanks,
> Pandula
>
> On Fri, Oct 16, 2015 at 6:26 PM, Johann Nallathamby 
> wrote:
>
>> Hi Pandula,
>>
>> Thanks. But actually the JIRA in concern is
>> https://wso2.org/jira/browse/CARBON-15475 . Can you please provide your
>> feedback on this.
>>
>> Thanks.
>>
>> On Fri, Oct 16, 2015 at 4:03 PM, Pandula Kariyawasam 
>> wrote:
>>
>>> Hi Johann/Kishanthan,
>>>
>>> Both issue [2][3] were observed rarely on IS510 pack received on 8th Oct
>>> 2015, which was based on kernel 4.4.1.
>>> We didn't experience these issue up to now, on the pack received on 13th
>>> Oct 2015, which is based on kernel 4.4.2.
>>> So I think we can reduce the priority of these issues, and keep eye on
>>> them in latest packs with kernel 4.4.2.
>>>
>>> [2] https://wso2.org/jira/browse/IDENTITY-3815
>>> [3] https://wso2.org/jira/browse/IDENTITY-3817
>>>
>>> Thanks,
>>> Pandula
>>>
>>>
>>> On Fri, Oct 16, 2015 at 3:09 PM, Johann Nallathamby 
>>> wrote:
>>>
 Hi Kishanthan,

 On Fri, Oct 16, 2015 at 2:38 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

>
>
> On Fri, Oct 16, 2015 at 11:27 AM, Johann Nallathamby 
> wrote:
>
>> Hi Kishanthan/Kernel Team,
>>
>> We have added the test case as well to the same PR.
>>
>
> Thanks Johann.
>
> @MB Team, could you guys verify that all your scenarios are now
> passing?.  We will start the next RC build once this is confirmed ASAP.
>
>>
>> Also can we get CARBON-15505 merged? The PR for master is a very old
>> PR which we have missed to review and merge. This mainly contains some
>> reordering of fields in the UI to make it more consistent and reorder
>> properties in user-mgt.xml to be consistent with UI. Hope we don't need 
>> any
>> tests for this.
>>
>
> I think its better not to add any more changes at this stage. We will
> merge this for next patch release.
>
>>
>> Any update on the 3 issues raised above ?
>>
>
> For [1], we need more information to reproduce (LB & IS config,
> example requests, HTTP access logs on both LB and IS side with this 
> issue).
> Will send a separate mail on that, but I believe its not a blocker for the
> IS release right?
>

 I will request Hasanthi to upload the artifacts you requested.

 I may be not the right person to say if this is blocker or not.
 @QA Team, please give your opinion if we can consider this as not a
 blocker and go ahead with the release.

 Regards.


> [2] and [3], we haven't seen this error previously and according the
> trace, it looks like the "distributedCache" instance is becoming null in
> CacheImpl class. If the exact steps can be found or given on how to
> reproduce this, then we can work on finding the root cause for this.
>
>
>> Thanks,
>> Johann.
>>
>> On Thu, Oct 15, 2015 at 3:30 PM, Johann Nallathamby 
>> wrote:
>>
>>> Hi Kishanthan/Kernel Team,
>>>
>>> We are in the process writing the test case for the issue. Should be
>>> able to send it before end of day.
>>>
>>> [1] has been reported in another thread. This issue in particular
>>> looks critical to me, because AFAIK there are many users using
>>> proxyContextPath. Not sure about WebContextRoot though. Apart from that
>>> WSO2 QA has reported [2,3] in IS 5.1.0 SNAPSHOT pack. May be its 
>>> harmless,
>>> but looks like it is coming from kernel and would like to get your 
>>> thoughts
>>> on this if this is critical and needs to be fixed.
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-15475
>>> [2] https://wso2.org/jira/browse/IDENTITY-3815
>>> [3] https://wso2.org/jira/browse/IDENTITY-3817
>>>
>>> And also it will be great if we can change the default value of
>>> XSSPreventionConfig.Enabled to 'false' because this was added in order 
>>> to
>>> prevent XSS centrally, however the approach is not 100% bug free. 
>>> Whoever
>>> has this enabled needs to test all their functionality well. Therefore 
>>> what
>>> I suggest is to make it 'false' by default and whatever product that 
>>> needs
>>> it can enable it at product level. WDYT ? Can we do this ?
>>>
>>> Regards,
>>> Johan

Re: [Dev] [VOTE] Release WSO2 Carbon Kernel 4.4.2 RC2

[Hasanthi Purnima Dissanayake]

Hi Kishanthan,
Please find the requested information for [1] as a jira attchement. Please
consider that I observed this issue only when both proxy context path and
web context root is enabled as I mentioned in the JIRA.

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

Thanks

Hasanthi Dissanayake

Software Engineer | WSO2

E: hasan...@wso2.com 
M :0718407133| http://wso2.com 

On Fri, Oct 16, 2015 at 2:38 PM, Kishanthan Thangarajah  wrote:

>
>
> On Fri, Oct 16, 2015 at 11:27 AM, Johann Nallathamby 
> wrote:
>
>> Hi Kishanthan/Kernel Team,
>>
>> We have added the test case as well to the same PR.
>>
>
> Thanks Johann.
>
> @MB Team, could you guys verify that all your scenarios are now passing?.
> We will start the next RC build once this is confirmed ASAP.
>
>>
>> Also can we get CARBON-15505 merged? The PR for master is a very old PR
>> which we have missed to review and merge. This mainly contains some
>> reordering of fields in the UI to make it more consistent and reorder
>> properties in user-mgt.xml to be consistent with UI. Hope we don't need any
>> tests for this.
>>
>
> I think its better not to add any more changes at this stage. We will
> merge this for next patch release.
>
>>
>> Any update on the 3 issues raised above ?
>>
>
> For [1], we need more information to reproduce (LB & IS config, example
> requests, HTTP access logs on both LB and IS side with this issue). Will
> send a separate mail on that, but I believe its not a blocker for the IS
> release right?
> [2] and [3], we haven't seen this error previously and according the
> trace, it looks like the "distributedCache" instance is becoming null in
> CacheImpl class. If the exact steps can be found or given on how to
> reproduce this, then we can work on finding the root cause for this.
>
>
>> Thanks,
>> Johann.
>>
>> On Thu, Oct 15, 2015 at 3:30 PM, Johann Nallathamby 
>> wrote:
>>
>>> Hi Kishanthan/Kernel Team,
>>>
>>> We are in the process writing the test case for the issue. Should be
>>> able to send it before end of day.
>>>
>>> [1] has been reported in another thread. This issue in particular looks
>>> critical to me, because AFAIK there are many users using proxyContextPath.
>>> Not sure about WebContextRoot though. Apart from that WSO2 QA has reported
>>> [2,3] in IS 5.1.0 SNAPSHOT pack. May be its harmless, but looks like it is
>>> coming from kernel and would like to get your thoughts on this if this is
>>> critical and needs to be fixed.
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-15475
>>> [2] https://wso2.org/jira/browse/IDENTITY-3815
>>> [3] https://wso2.org/jira/browse/IDENTITY-3817
>>>
>>> And also it will be great if we can change the default value of
>>> XSSPreventionConfig.Enabled to 'false' because this was added in order to
>>> prevent XSS centrally, however the approach is not 100% bug free. Whoever
>>> has this enabled needs to test all their functionality well. Therefore what
>>> I suggest is to make it 'false' by default and whatever product that needs
>>> it can enable it at product level. WDYT ? Can we do this ?
>>>
>>> Regards,
>>> Johann.
>>>
>>>
>>> On Wed, Oct 14, 2015 at 6:30 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 Can we also have test case for this fix please?

 On Wed, Oct 14, 2015 at 6:13 PM, Isura Karunaratne 
 wrote:

> Hi,
>
> This issue is fixed in [1].
>
>
> Thanks
> isura
>
>
> [1] https://wso2.org/jira/browse/CARBON-15517
>
>
> On Wed, Oct 14, 2015 at 11:25 AM, Johann Nallathamby 
> wrote:
>
>> Hi Isura,
>>
>> Can you look into this issue urgently. I remember you fixing an issue
>> related to this.
>>
>> Thanks.
>>
>> On Wed, Oct 14, 2015 at 7:16 AM, Indika Sampath 
>> wrote:
>>
>>> Hi All,
>>>
>>> I debug code of our and found issue. It seems implementation of some
>>> API changed in user-core. Let me explain the flow.
>>>
>>> Our queue/topic creation has two call.
>>>
>>> 1. We create internal role when adding queue and assign
>>> "changePermission", "publish", "consume"  permissions to it. Which means
>>> that, user who created particular queue can update permission, publish 
>>> or
>>> consume.
>>>
>>> - Below code line used to get internal role name:
>>>
>>> UserCoreUtil.addInternalDomainName(QUEUE_ROLE_PREFIX +
>>> queueName.replace(".","-").replace("/", "-"))
>>>
>>> result = {java.lang.String@10289}"*Internal/Q_userQueue*"
>>> value = {char[21]@10290}
>>> hash = 0
>>> hash32 = 0
>>>
>>> - assign permission as below:
>>>
>>> userStoreManager.addRole(roleName, user, null);
>>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>>> PERMISSION_CHANGE_PERMISSION);
>>> userRealm.getAuthorizationManager().authorizeRole(roleName, queueId,
>>> TreeNode.Permission.CONSUME.toString().toLowerCase())

[Dev] [jaggery] Where should I Report Issues in IDEA Jaggery Plugin?

[Chamila Wijayarathna]

Hi all,

I have installed jaggery plugin in IDEA 14.1.3. I observed following
suggestion which is not spelled correctly.

[image: Inline image 1]

Correct function which is supported is "isDebugEnabled", but here it shows
"isDebugEnabeld".

At where should I report this issue?

Thank You!

-- 
*Chamila Dilshan Wijayarathna,*
Software Engineer
Mobile:(+94)788193620
WSO2 Inc., http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] [OSGI] Removal of dynamic imports causes CNF on extention points

[Shani Ranasinghe]

Hi,


On Sun, Oct 18, 2015 at 2:25 PM, KasunG Gajasinghe  wrote:

>
>
> On Fri, Oct 16, 2015 at 4:31 PM, Shani Ranasinghe  wrote:
>
>>
>> Hi,
>>
>> In APIM current code (1.10), we have removed the > >* from all packages at the moment.
>>
>> We faced an issue now, where an extension point would not work with this
>> change. i.e. if we put a external jar into the
>> /repository/components/lib folder, that class will not be picked
>> up by the component OSGI bundle because of the aforementioned reason.
>>
>> Discussing with KasunG, I learned that we cannot remove the 
>> DynamicImport-Package
>> statement, if the components use Class.forName() or 
>> .class.getClassLoader().loadClass();
>> because the OSGI bundle would not be able to identify the external class.
>>
>> As a possible solution, what we thought of is, to move the Class.forName()
>> to a central location, possibily to the org.wso2.carbon.apimgt.impl
>> package, and have the
>> * to that package. Then
>> all other packages that used to have the Class.forName() can be referred to
>> the method introduced in the org.wso2.carbon.apimgt.impl package.
>>
>
> Did you mean the org.wso2.carbon.apimgt.impl component?
>

Yes, that is what I meant. All other components  that use a Class.forName()
refer to this component.

>
>
>> @KasunG, Kishanthan, is this the correct approach?
>>
>> Are there any other approaches that we could look into?
>> --
>> Thanks and Regards
>> *,Shani Ranasinghe*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 2273555
>> Blog: http://waysandmeans.blogspot.com/
>> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>>
>
>
>
> --
>
> *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
> email: kasung AT spamfree wso2.com
> linked-in: http://lk.linkedin.com/in/gajasinghe
> blog: http://kasunbg.org
>
>
>



-- 
Thanks and Regards
*,Shani Ranasinghe*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 2273555
Blog: http://waysandmeans.blogspot.com/
linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Application creation can be failed, if we create the application before the git repo is available in s2git

[Samith Dassanayake]

Hi Amlka,

Please find my comments inline

On Fri, Oct 16, 2015 at 11:15 PM, Amalka Subasinghe  wrote:

>
> Hi,
>
> in the current deployment, in the tenant creation flow , when the SM
> receive the create_subsciption message it creates a git repo in s2git and
> then subscribe the tenant to all 3 AS instances.
> This takes little more time and no response return to front end whether
> that flow completed successfully.
>
 We can simply implement a git hook in s2git to notify to AF side, when a
repo is created.


> regardless of that we allow user to login to AF home and create
> application.
> if the git repo is not available in the s2git at that time, application
> creation can be failed.
>
> Shall we add some logic to check whether the s2git repo is available or
> not, in the beginning of application creation logic, with some waiting
> logic until it creates?
> WDYT? any other ideas?
>
Do we need to wait until it creates? What if we add those
requests(Committing to s2git) to a queue, if the s2git repo is not
available. Then once we get the notification from the s2git, we can execute
those requests from the queue based on the tenant.



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


-- 
Best Regards

Samith Dassanayake
Software Engineer | Cloud TG
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware

Mobile : +947 76207351
Blog : buddycode.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] help with application service error

[Thusitha Thilina Dayaratne]

Remove architecture
adding dev

On Fri, Oct 16, 2015 at 8:04 PM, John Q  wrote:

> Hello, I have created an axis2 service that invokes an external service,
> when I deploy it into AS 5.2.1 I get this error:
>
> Unable to create SOAP connection factory: Provider
> org.apache.axis2.saaj.SOAPConnectionFactoryImpl not found
>
> what do I have to do?
>
> thx
>
> ___
> Architecture mailing list
> architect...@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Thusitha Dayaratne
Software Engineer
WSO2 Inc. - lean . enterprise . middleware |  wso2.com

Mobile  +94712756809
Blog  alokayasoya.blogspot.com
Abouthttp://about.me/thusithathilina
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [AF] Application creation can be failed, if we create the application before the git repo is available in s2git

[Kasun De Silva]

Hi Amalka,

See my comments inline,

>
> Hi,
>
> in the current deployment, in the tenant creation flow , when the SM
> receive the create_subsciption message it creates a git repo in s2git and
> then subscribe the tenant to all 3 AS instances.
> This takes little more time and no response return to front end whether
> that flow completed successfully. regardless of that we allow user to login
> to AF home and create application.
> if the git repo is not available in the s2git at that time, application
> creation can be failed.
>
>
Seems this is an edge case, do we know how much time would it take to
complete the tenant flow, before one should create the first application ?
We better test on this.

Shall we add some logic to check whether the s2git repo is available or
> not, in the beginning of application creation logic, with some waiting
> logic until it creates?
> WDYT? any other ideas?
>

Great point. Big +1 for the idea.

In my understanding this case only valid for the first application creation
after the tenant creation flow. So I think we should limit this logic only
for the first application. Otherwise this will add some latency to the app
creation. (I'm referring to the cloud deployment.)


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

Re: [Dev] [APIM] [OSGI] Removal of dynamic imports causes CNF on extention points

[KasunG Gajasinghe]

On Fri, Oct 16, 2015 at 4:31 PM, Shani Ranasinghe  wrote:

>
> Hi,
>
> In APIM current code (1.10), we have removed the  >* from all packages at the moment.
>
> We faced an issue now, where an extension point would not work with this
> change. i.e. if we put a external jar into the
> /repository/components/lib folder, that class will not be picked
> up by the component OSGI bundle because of the aforementioned reason.
>
> Discussing with KasunG, I learned that we cannot remove the 
> DynamicImport-Package
> statement, if the components use Class.forName() or 
> .class.getClassLoader().loadClass();
> because the OSGI bundle would not be able to identify the external class.
>
> As a possible solution, what we thought of is, to move the Class.forName()
> to a central location, possibily to the org.wso2.carbon.apimgt.impl
> package, and have the
> * to that package. Then
> all other packages that used to have the Class.forName() can be referred to
> the method introduced in the org.wso2.carbon.apimgt.impl package.
>

Did you mean the org.wso2.carbon.apimgt.impl component?


> @KasunG, Kishanthan, is this the correct approach?
>
> Are there any other approaches that we could look into?
> --
> Thanks and Regards
> *,Shani Ranasinghe*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 2273555
> Blog: http://waysandmeans.blogspot.com/
> linked in: lk.linkedin.com/pub/shani-ranasinghe/34/111/ab
>



-- 

*Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc.
email: kasung AT spamfree wso2.com
linked-in: http://lk.linkedin.com/in/gajasinghe
blog: http://kasunbg.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev