Re: [Dev] Regarding DAS connection with the external spark cluster

[Anjana Fernando]

Yeah, the docs must be updated. Thanks.

Cheers,
Anjana.

On Tue, Oct 20, 2015 at 12:02 PM, Nayomi Dayarathne  wrote:

> Hi,
>
> Noted. And created a document JIRA[1] to include this information in  DAS
> documents.
>
> [1].https://wso2.org/jira/browse/DOCUMENTATION-2592
>
> Regards,
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>
> On Tue, Oct 20, 2015 at 11:25 AM, Anjana Fernando  wrote:
>
>> Hi Nayomi,
>>
>> Current approach is an acceptable solution, where copying the DAS pack to
>> a target Spark node is not a problem. Having a script or something to
>> compile the list of jars only required for it is just a small convenience
>> mechanism, and is not really that important. Someone may actually just like
>> copying the pack right away, rather than running another command.
>>
>> Cheers,
>> Anjana.
>>
>> On Mon, Oct 19, 2015 at 10:24 PM, Nayomi Dayarathne 
>> wrote:
>>
>>> Hi all,
>>>
>>> Given the current situation in DAS, there should be a DAS distribution
>>> in every spark node in an external spark cluster in order to work DAS with
>>> it.That way, external spark cluster able to access jar files which needs to
>>> work with DAS.
>>>
>>> Since this is not a better approach,I have already reported an
>>> improvement JIRA[1] regarding this.
>>>
>>> Therefore, we want to know whether we are going to implement a solution
>>> according to the JIRA[1] reported or are there any better solution for this
>>> ?
>>>
>>>
>>> [1].https://wso2.org/jira/browse/DAS-197
>>>
>>>
>>> Regards,
>>>
>>> Nayomi Dayarathne
>>>
>>> *Software Engineer-QA*
>>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>>
>>> *nay...@wso2.com *
>>>
>>
>>
>>
>> --
>> *Anjana Fernando*
>> Senior Technical Lead
>> WSO2 Inc. | http://wso2.com
>> lean . enterprise . middleware
>>
>
>


-- 
*Anjana Fernando*
Senior Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Regarding DAS connection with the external spark cluster

[Nayomi Dayarathne]

Hi,

Noted. And created a document JIRA[1] to include this information in  DAS
documents.

[1].https://wso2.org/jira/browse/DOCUMENTATION-2592

Regards,

Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 <+94+(0)+775246619>

*nay...@wso2.com *

On Tue, Oct 20, 2015 at 11:25 AM, Anjana Fernando  wrote:

> Hi Nayomi,
>
> Current approach is an acceptable solution, where copying the DAS pack to
> a target Spark node is not a problem. Having a script or something to
> compile the list of jars only required for it is just a small convenience
> mechanism, and is not really that important. Someone may actually just like
> copying the pack right away, rather than running another command.
>
> Cheers,
> Anjana.
>
> On Mon, Oct 19, 2015 at 10:24 PM, Nayomi Dayarathne 
> wrote:
>
>> Hi all,
>>
>> Given the current situation in DAS, there should be a DAS distribution in
>> every spark node in an external spark cluster in order to work DAS with
>> it.That way, external spark cluster able to access jar files which needs to
>> work with DAS.
>>
>> Since this is not a better approach,I have already reported an
>> improvement JIRA[1] regarding this.
>>
>> Therefore, we want to know whether we are going to implement a solution
>> according to the JIRA[1] reported or are there any better solution for this
>> ?
>>
>>
>> [1].https://wso2.org/jira/browse/DAS-197
>>
>>
>> Regards,
>>
>> Nayomi Dayarathne
>>
>> *Software Engineer-QA*
>> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>>
>> *nay...@wso2.com *
>>
>
>
>
> --
> *Anjana Fernando*
> Senior Technical Lead
> WSO2 Inc. | http://wso2.com
> lean . enterprise . middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] POST message payload from Swagger UI [API M]

[Malintha Amarasinghe]

Hi Nadeesha,

I rechecked with APIM 1.9.1. When I added a resource as a POST, I can see a
default body parameter is by default added. Please refer the screenshots
for publisher and store swagger console. As Madusanka pointed too, this
should be a problem with the swagger.json file. If you need to add a body
parameter it needs to be specified as "in:body" and also we need to specify
a schema. If we don't have a schema we can specify an empty schema like
below. This is by default added when you add a POST resource in APIM 1.9.1.

  /res1:
post:
  x-auth-type: "Application & Application User"
  x-throttling-tier: Unlimited
  parameters:
- schema:
*type: object*
  description: Request Body
  name: Payload
  required: false
  *in: body*
  responses:
"200": {}



Thanks.

On Tue, Oct 20, 2015 at 11:01 AM, Nadeesha Gamage  wrote:

> Thanks, is there any particular reason why the 'body' option is not
> available in the UI?
>
> On Mon, Oct 19, 2015 at 9:11 PM, Madusanka Premaratne  > wrote:
>
>> Hi Nadeesha,
>> You can do this in APIM 1.9.0 and up. In order to post, you need to
>> create a model/definition from the API Publisher. Please refer the petstore
>> sample[1]
>>
>> When defining you need to set the parameter type as  in: body and you
>> need to set the schema. Refer to the attached yaml for schema definition.
>>
>> [1] - http://petstore.swagger.io/​​
>>
>>
>> Thanks,
>> Madusanka
>>
>> On Tue, Oct 20, 2015 at 8:15 AM, Nadeesha Gamage 
>> wrote:
>>
>>> API M 1.9.1
>>>
>>> On Mon, Oct 19, 2015 at 5:42 PM, Malintha Amarasinghe <
>>> malint...@wso2.com> wrote:
>>>
 Hi,

 What is the APIM version you are using? AFAIK this is supported in APIM
 1.9.1 version.

 Thank you.
 Malintha

 On Tue, Oct 20, 2015 at 5:13 AM, Nadeesha Gamage 
 wrote:

> Hi Devs,
> Is it possible to POST a message payload from the Swagger UI in the
> API Store. The current API Manager version doesnt have a 'Body' parameter
> type available to do this. Is there any other way to send a message 
> payload
> from Swagger UI.
>
>
> Thank you,
>
>
> --
> Nadeesha Gamage
> Associate Technical Lead - Solutions Engineering
> T : +94 77 394 5706
> B : https://nadeesha678.wordpress.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

 Mobile : +94 712383306

>>>
>>>
>>>
>>> --
>>> Nadeesha Gamage
>>> Associate Technical Lead - Solutions Engineering
>>> T : +94 77 394 5706
>>> B : https://nadeesha678.wordpress.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Madusanka Premaratne* | Associate Software Engineer
>> WSO2, Inc | lean. enterprise. middleware.
>> #20, Palm Grove, Colombo 03, Sri Lanka
>> Mobile: +94 71 835 70 73| Work: +94 112 145 345
>> Email: madusan...@wso2.com | Web: www.wso2.com
>>
>> [image: Facebook]  [image: Twitter]
>>  [image: Google Plus]
>>  [image:
>> Linkedin]  [image: Instagram]
>>  [image: Skype]
>> 
>>
>>
>
>
> --
> Nadeesha Gamage
> Associate Technical Lead - Solutions Engineering
> T : +94 77 394 5706
> B : https://nadeesha678.wordpress.com/
>



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

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

Re: [Dev] Regarding DAS connection with the external spark cluster

[Anjana Fernando]

Hi Nayomi,

Current approach is an acceptable solution, where copying the DAS pack to a
target Spark node is not a problem. Having a script or something to compile
the list of jars only required for it is just a small convenience
mechanism, and is not really that important. Someone may actually just like
copying the pack right away, rather than running another command.

Cheers,
Anjana.

On Mon, Oct 19, 2015 at 10:24 PM, Nayomi Dayarathne  wrote:

> Hi all,
>
> Given the current situation in DAS, there should be a DAS distribution in
> every spark node in an external spark cluster in order to work DAS with
> it.That way, external spark cluster able to access jar files which needs to
> work with DAS.
>
> Since this is not a better approach,I have already reported an improvement
> JIRA[1] regarding this.
>
> Therefore, we want to know whether we are going to implement a solution
> according to the JIRA[1] reported or are there any better solution for this
> ?
>
>
> [1].https://wso2.org/jira/browse/DAS-197
>
>
> Regards,
>
> Nayomi Dayarathne
>
> *Software Engineer-QA*
> Mobile : +94 (0) 775246619 <+94+(0)+775246619>
>
> *nay...@wso2.com *
>



-- 
*Anjana Fernando*
Senior Technical Lead
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] POST message payload from Swagger UI [API M]

[Nadeesha Gamage]

Thanks, is there any particular reason why the 'body' option is not
available in the UI?

On Mon, Oct 19, 2015 at 9:11 PM, Madusanka Premaratne 
wrote:

> Hi Nadeesha,
> You can do this in APIM 1.9.0 and up. In order to post, you need to create
> a model/definition from the API Publisher. Please refer the petstore
> sample[1]
>
> When defining you need to set the parameter type as  in: body and you need
> to set the schema. Refer to the attached yaml for schema definition.
>
> [1] - http://petstore.swagger.io/​​
>
>
> Thanks,
> Madusanka
>
> On Tue, Oct 20, 2015 at 8:15 AM, Nadeesha Gamage 
> wrote:
>
>> API M 1.9.1
>>
>> On Mon, Oct 19, 2015 at 5:42 PM, Malintha Amarasinghe > > wrote:
>>
>>> Hi,
>>>
>>> What is the APIM version you are using? AFAIK this is supported in APIM
>>> 1.9.1 version.
>>>
>>> Thank you.
>>> Malintha
>>>
>>> On Tue, Oct 20, 2015 at 5:13 AM, Nadeesha Gamage 
>>> wrote:
>>>
 Hi Devs,
 Is it possible to POST a message payload from the Swagger UI in the API
 Store. The current API Manager version doesnt have a 'Body' parameter type
 available to do this. Is there any other way to send a message payload from
 Swagger UI.


 Thank you,


 --
 Nadeesha Gamage
 Associate Technical Lead - Solutions Engineering
 T : +94 77 394 5706
 B : https://nadeesha678.wordpress.com/

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


>>>
>>>
>>> --
>>> Malintha Amarasinghe
>>> Software Engineer
>>> *WSO2, Inc. - lean | enterprise | middleware*
>>> http://wso2.com/
>>>
>>> Mobile : +94 712383306
>>>
>>
>>
>>
>> --
>> Nadeesha Gamage
>> Associate Technical Lead - Solutions Engineering
>> T : +94 77 394 5706
>> B : https://nadeesha678.wordpress.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Madusanka Premaratne* | Associate Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 835 70 73| Work: +94 112 145 345
> Email: madusan...@wso2.com | Web: www.wso2.com
>
> [image: Facebook]  [image: Twitter]
>  [image: Google Plus]
>  [image:
> Linkedin]  [image: Instagram]
>  [image: Skype]
> 
>
>


-- 
Nadeesha Gamage
Associate Technical Lead - Solutions Engineering
T : +94 77 394 5706
B : https://nadeesha678.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Committers += Maheshakya Wijewardena

[Rajith Roshan]

Congratz Maheshakya 

On Tue, Oct 20, 2015 at 10:48 AM, Ashen Weerathunga  wrote:

> Congratz Maheshakya!!! :)
>
> On Tue, Oct 20, 2015 at 10:42 AM, Nirmal Fernando  wrote:
>
>> Hi All,
>>
>> It's my pleasure to announce *Maheshakya Wijewardena* as a
>> *WSO2 Committer*. He has been a key contributor to the *WSO2 Machine
>> Learner *Product and in recognition of his excellent work, he had been
>> voted as a WSO2 Committer.
>>
>> Congratulations Maheshakya and keep up the good work!
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Ashen Weerathunga*
> Software Engineer - Intern
> WSO2 Inc.: http://wso2.com
> lean.enterprise.middleware
>
> Email: as...@wso2.com
> Mobile: +94 716042995 <94716042995>
> LinkedIn:
> *http://lk.linkedin.com/in/ashenweerathunga
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: +94-72-642-8350 <%2B94-71-554-8430>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Jaggery] response.sendError() not working for PUT and DELETE

[Thilini Cooray]

Hi,

This is the source.

var uri = request.getRequestURI();

var callPath=uri.replace("/store","");

var action = "list"; // default action list the topics
if(uri != null) {
var uriMatcher = new URIMatcher(callPath);
if (uriMatcher.match("/forum") || uriMatcher.match("/forum/")) {
action = "list";
}
else if (uriMatcher.match("/forum/new")) {
action = "new"; // create topic
}
else if (uriMatcher.match("/forum/new/{id}")) {
action = "new"; // create topic
}
else if (uriMatcher.match("/forum/topic/{id}")) {
var topic = uriMatcher.elements().id;
action = "topic";
} else {
action = "exit";
}
}

if(action == "exit"){
*response.sendError(404);*
} else {

// Logic comes here

}

404 will refer to
/repository/deployment/server/jaggeryapps/store/pages/error-pages/404.html


Thanks.



On Tue, Oct 20, 2015 at 10:39 AM, Sajith Ariyarathna 
wrote:

> Hi Thilini,
>
> Can you share your code here?
>
> I tested following Jaggery code. (Test was executed in* AppM 1.0.0* pack
> and *Advanced Rest Client* was used as the HTTP client)
>
> *URL Mapping in jaggery.conf: *
>
> {
>
> "url": "/test/*",
>
> "path": "/lib/test.jag"
>
> }
>
>
> *File*: *test.jag*
>
> *Code:*
>
> var log = new Log("[testing]");
>
> log.info("Hit for HTTP method " + request.getMethod());
>
> response.sendError(404, "Testing page not found.");
>
>
> *Terminal Output:*
>
> [2015-10-20 10:26:52,885]  INFO - [testing] Hit for HTTP method GET
>
> [2015-10-20 10:26:57,499]  INFO - [testing] Hit for HTTP method POST
>
> [2015-10-20 10:27:02,045]  INFO - [testing] Hit for HTTP method PUT
>
> [2015-10-20 10:27:06,011]  INFO - [testing] Hit for HTTP method DELETE
>
> [2015-10-20 10:27:08,491]  INFO - [testing] Hit for HTTP method HEAD
>
> [2015-10-20 10:27:10,860]  INFO - [testing] Hit for HTTP method OPTIONS
>
>
> *HTTP Output:*
>
> 404 Not Found
>
> 404 Not Found
>
> 404 Not Found
>
> 404 Not Found
>
> 404 Not Found
>
> 404 Not Found
>
>
> Since the expected output was received in above, I believe the issue is on
> your side, not in Jaggery.
>
> Thanks.
>
> On Mon, Oct 19, 2015 at 2:04 PM, Thilini Cooray  wrote:
>
>> Hi,
>>
>> I want to send error messages for invalid URLs from API Manager Store
>> jaggery layer.
>>
>> I use response.sendError(404) for this purpose.
>> For HTTP POST and GET this method returns the correct error page while it
>> doesn't return any message for PUT and DELETE.
>>
>> I debugged [1] and found out that the errors send in all HTTP methods
>> gets hit in
>>
>> rho.response.sendError((Integer) args[0]);
>>
>> Output stream of rho.response also contains the correct error page in all
>> HTTP methods.
>> Yet it doesn't get returned in HTTP PUT and DELETE methods.
>>
>> I am unable to figure out the reason for this behaviour.
>> Any help is appreciated.
>>
>> Thanks.
>>
>> [1]
>> http://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk04/components/jaggery/0.9.0.ALPHA4.wso2v1/hostobjects/org.jaggeryjs.hostobjects.web/src/main/java/org/jaggeryjs/hostobjects/web/ResponseHostObject.java
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sajith Ariyarathna
> Software Engineer; WSO2, Inc.;  http://wso2.com/
> mobile: +94 77 6602284, +94 71 3951048
>



-- 
Best Regards,

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

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

Re: [Dev] WSO2 Committers += Maheshakya Wijewardena

[Ashen Weerathunga]

Congratz Maheshakya!!! :)

On Tue, Oct 20, 2015 at 10:42 AM, Nirmal Fernando  wrote:

> Hi All,
>
> It's my pleasure to announce *Maheshakya Wijewardena* as a
> *WSO2 Committer*. He has been a key contributor to the *WSO2 Machine
> Learner *Product and in recognition of his excellent work, he had been
> voted as a WSO2 Committer.
>
> Congratulations Maheshakya and keep up the good work!
>
> --
>
> Thanks & regards,
> Nirmal
>
> Team Lead - WSO2 Machine Learner
> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Ashen Weerathunga*
Software Engineer - Intern
WSO2 Inc.: http://wso2.com
lean.enterprise.middleware

Email: as...@wso2.com
Mobile: +94 716042995 <94716042995>
LinkedIn:
*http://lk.linkedin.com/in/ashenweerathunga
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Committers += Maheshakya Wijewardena

[Nirmal Fernando]

Hi All,

It's my pleasure to announce *Maheshakya Wijewardena* as a *WSO2 Committer*.
He has been a key contributor to the *WSO2 Machine Learner *Product and in
recognition of his excellent work, he had been voted as a WSO2 Committer.

Congratulations Maheshakya and keep up the good work!

-- 

Thanks & regards,
Nirmal

Team Lead - WSO2 Machine Learner
Associate Technical Lead - Data Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Jaggery] response.sendError() not working for PUT and DELETE

[Sajith Ariyarathna]

Hi Thilini,

Can you share your code here?

I tested following Jaggery code. (Test was executed in* AppM 1.0.0* pack
and *Advanced Rest Client* was used as the HTTP client)

*URL Mapping in jaggery.conf: *

{

"url": "/test/*",

"path": "/lib/test.jag"

}


*File*: *test.jag*

*Code:*

var log = new Log("[testing]");

log.info("Hit for HTTP method " + request.getMethod());

response.sendError(404, "Testing page not found.");


*Terminal Output:*

[2015-10-20 10:26:52,885]  INFO - [testing] Hit for HTTP method GET

[2015-10-20 10:26:57,499]  INFO - [testing] Hit for HTTP method POST

[2015-10-20 10:27:02,045]  INFO - [testing] Hit for HTTP method PUT

[2015-10-20 10:27:06,011]  INFO - [testing] Hit for HTTP method DELETE

[2015-10-20 10:27:08,491]  INFO - [testing] Hit for HTTP method HEAD

[2015-10-20 10:27:10,860]  INFO - [testing] Hit for HTTP method OPTIONS


*HTTP Output:*

404 Not Found

404 Not Found

404 Not Found

404 Not Found

404 Not Found

404 Not Found


Since the expected output was received in above, I believe the issue is on
your side, not in Jaggery.

Thanks.

On Mon, Oct 19, 2015 at 2:04 PM, Thilini Cooray  wrote:

> Hi,
>
> I want to send error messages for invalid URLs from API Manager Store
> jaggery layer.
>
> I use response.sendError(404) for this purpose.
> For HTTP POST and GET this method returns the correct error page while it
> doesn't return any message for PUT and DELETE.
>
> I debugged [1] and found out that the errors send in all HTTP methods gets
> hit in
>
> rho.response.sendError((Integer) args[0]);
>
> Output stream of rho.response also contains the correct error page in all
> HTTP methods.
> Yet it doesn't get returned in HTTP PUT and DELETE methods.
>
> I am unable to figure out the reason for this behaviour.
> Any help is appreciated.
>
> Thanks.
>
> [1]
> http://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk04/components/jaggery/0.9.0.ALPHA4.wso2v1/hostobjects/org.jaggeryjs.hostobjects.web/src/main/java/org/jaggeryjs/hostobjects/web/ResponseHostObject.java
>
> --
> Best Regards,
>
> *Thilini Cooray*
> Software Engineer
> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
> E-mail : thili...@wso2.com
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sajith Ariyarathna
Software Engineer; WSO2, Inc.;  http://wso2.com/
mobile: +94 77 6602284, +94 71 3951048
___
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

[Kishanthan Thangarajah]

We are closing this vote and this vote passes with 5 binding(+1) votes and
0 -1s. We will proceed with release of WSO2 Carbon Kernel 4.4.2.

On Tue, Oct 20, 2015 at 8:10 AM, Inosh Goonewardena  wrote:

> Hi All,
>
> I have tested DAS basic scenarios and basic user management
> functionalities in DAS built with kernel-4.4.2.
>
> +1 to release.
>
>
> On Mon, Oct 19, 2015 at 11:04 PM, Kalpa Welivitigoda 
> wrote:
>
>> Hi all,
>>
>> All automation tests are passing for an AS pack built with kernel-4.4.2.
>>
>> [X] Stable - go ahead and release
>>
>> On Mon, Oct 19, 2015 at 7:15 PM, Rajith Vitharana 
>> wrote:
>>
>>> HI,
>>>
>>> Created a public jira for this in [1]
>>>
>>> [1] - https://wso2.org/jira/browse/CARBON-15537
>>>
>>> Thanks,
>>>
>>> On Mon, Oct 19, 2015 at 5:45 PM, KasunG Gajasinghe 
>>> wrote:
>>>


 On Mon, Oct 19, 2015 at 1:58 PM, Rajith Vitharana 
 wrote:

> And I hope it is not a blocker as if we send correct headers, scenario
> works properly(if we send authorization basic header) I observed this
> behavior in ESB 4.9.0 as well.
>
>
 Yes, it's not a blocker then. Can you raise a jira, so we can fix this
 for the next release?

 Thanks


>
> Thanks,
>
> On Mon, Oct 19, 2015 at 1:54 PM, Rajith Vitharana 
> wrote:
>
>> Hi Kernel team,
>>
>> On a side note, there is a minor issue in security scenarios though,
>> when using UT policy, if we doesn't send authorization headers, then 
>> server
>> will throw below exception
>>
>> java.lang.ClassCastException:
>> org.apache.axiom.om.impl.dom.ElementImpl cannot be cast to
>> org.apache.axiom.soap.SOAPHeaderBlock
>> at
>> org.wso2.carbon.security.pox.POXSecurityHandler.isSOAPWithoutSecHeader(POXSecurityHandler.java:362)
>> at
>> org.wso2.carbon.security.pox.POXSecurityHandler.invoke(POXSecurityHandler.java:102)
>> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
>> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
>> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
>> at org.apache.axis2.engine.AxisEngine.sendFault(AxisEngine.java:515)
>> at
>> org.apache.axis2.transport.http.AxisServlet.handleFault(AxisServlet.java:433)
>> at
>> org.apache.axis2.transport.http.AxisServlet.processAxisFault(AxisServlet.java:398)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:188)
>> at
>> org.wso2.carbon.core.transports.CarbonServlet.doPost(CarbonServlet.java:231)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.wso2.carbon.ui.filters.CSRFPreventionFilter.doFilter(CSRFPreventionFilter.java:88)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.wso2.carbon.ui.filters.CRLFPreventionFilter.doFilter(CRLFPreventionFilter.java:59)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>> at
>> org.apache.catalina.auth

Re: [Dev] POST message payload from Swagger UI [API M]

[Madusanka Premaratne]

Hi Nadeesha,
You can do this in APIM 1.9.0 and up. In order to post, you need to create
a model/definition from the API Publisher. Please refer the petstore
sample[1]

When defining you need to set the parameter type as  in: body and you need
to set the schema. Refer to the attached yaml for schema definition.

[1] - http://petstore.swagger.io/​​


Thanks,
Madusanka

On Tue, Oct 20, 2015 at 8:15 AM, Nadeesha Gamage  wrote:

> API M 1.9.1
>
> On Mon, Oct 19, 2015 at 5:42 PM, Malintha Amarasinghe 
> wrote:
>
>> Hi,
>>
>> What is the APIM version you are using? AFAIK this is supported in APIM
>> 1.9.1 version.
>>
>> Thank you.
>> Malintha
>>
>> On Tue, Oct 20, 2015 at 5:13 AM, Nadeesha Gamage 
>> wrote:
>>
>>> Hi Devs,
>>> Is it possible to POST a message payload from the Swagger UI in the API
>>> Store. The current API Manager version doesnt have a 'Body' parameter type
>>> available to do this. Is there any other way to send a message payload from
>>> Swagger UI.
>>>
>>>
>>> Thank you,
>>>
>>>
>>> --
>>> Nadeesha Gamage
>>> Associate Technical Lead - Solutions Engineering
>>> T : +94 77 394 5706
>>> B : https://nadeesha678.wordpress.com/
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Malintha Amarasinghe
>> Software Engineer
>> *WSO2, Inc. - lean | enterprise | middleware*
>> http://wso2.com/
>>
>> Mobile : +94 712383306
>>
>
>
>
> --
> Nadeesha Gamage
> Associate Technical Lead - Solutions Engineering
> T : +94 77 394 5706
> B : https://nadeesha678.wordpress.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Madusanka Premaratne* | Associate Software Engineer
WSO2, Inc | lean. enterprise. middleware.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 71 835 70 73| Work: +94 112 145 345
Email: madusan...@wso2.com | Web: www.wso2.com

[image: Facebook]  [image: Twitter]
 [image: Google Plus]
 [image:
Linkedin]  [image: Instagram]
 [image: Skype]



swagger.yaml
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] POST message payload from Swagger UI [API M]

[Nadeesha Gamage]

API M 1.9.1

On Mon, Oct 19, 2015 at 5:42 PM, Malintha Amarasinghe 
wrote:

> Hi,
>
> What is the APIM version you are using? AFAIK this is supported in APIM
> 1.9.1 version.
>
> Thank you.
> Malintha
>
> On Tue, Oct 20, 2015 at 5:13 AM, Nadeesha Gamage 
> wrote:
>
>> Hi Devs,
>> Is it possible to POST a message payload from the Swagger UI in the API
>> Store. The current API Manager version doesnt have a 'Body' parameter type
>> available to do this. Is there any other way to send a message payload from
>> Swagger UI.
>>
>>
>> Thank you,
>>
>>
>> --
>> Nadeesha Gamage
>> Associate Technical Lead - Solutions Engineering
>> T : +94 77 394 5706
>> B : https://nadeesha678.wordpress.com/
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Amarasinghe
> Software Engineer
> *WSO2, Inc. - lean | enterprise | middleware*
> http://wso2.com/
>
> Mobile : +94 712383306
>



-- 
Nadeesha Gamage
Associate Technical Lead - Solutions Engineering
T : +94 77 394 5706
B : https://nadeesha678.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] POST message payload from Swagger UI [API M]

[Malintha Amarasinghe]

Hi,

What is the APIM version you are using? AFAIK this is supported in APIM
1.9.1 version.

Thank you.
Malintha

On Tue, Oct 20, 2015 at 5:13 AM, Nadeesha Gamage  wrote:

> Hi Devs,
> Is it possible to POST a message payload from the Swagger UI in the API
> Store. The current API Manager version doesnt have a 'Body' parameter type
> available to do this. Is there any other way to send a message payload from
> Swagger UI.
>
>
> Thank you,
>
>
> --
> Nadeesha Gamage
> Associate Technical Lead - Solutions Engineering
> T : +94 77 394 5706
> B : https://nadeesha678.wordpress.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


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

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

[Dev] POST message payload from Swagger UI [API M]

[Nadeesha Gamage]

Hi Devs,
Is it possible to POST a message payload from the Swagger UI in the API
Store. The current API Manager version doesnt have a 'Body' parameter type
available to do this. Is there any other way to send a message payload from
Swagger UI.


Thank you,


-- 
Nadeesha Gamage
Associate Technical Lead - Solutions Engineering
T : +94 77 394 5706
B : https://nadeesha678.wordpress.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 developer Studio Kernel 4.0.0 Milestone-0 Released

[Kavith Lokuhewage]

We are pleased to announce the 4.0.0-M0 release of WSO2 developer Studio
Kernel.

P2 repository of WSO2 developer Studio kernel 4.0.0-M0 is available to
download here
.
Source
and Tag Location for this release is available here
.

This is the first step in the new path of WSO2 Developer Studio to separate
the common kernel with WSO2 specific common tooling components and
providing product specific tooling components to be installed on-top of the
Developer Studio kernel.

We are moving into a new development and release architecture from here
on-wards where WSO2 Developer Studio Kernel team will be responsible on
implementing, maintaining and supporting a common kernel platform on-top of
which the respective product teams would be able to develop, install and
run their tooling components.

This approach would be more effective and and would give Developer Studio
users a more holistic tooling experience for all the WSO2 products.

This 4.0.0-M0 release of the kernel contains a initial separation of common
kernel components from the existing WSO2 Developer Studio.

*How to Contribute*

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


*Contact us*

WSO2 developers can be contacted via the mailing lists:

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

Thanks,
Developer Studio Team
-- 
*Kavith Lokuhewage*
Software Engineer
WSO2 Inc. - http://wso2.com
lean . enterprise . middleware
Mobile - +9477-9-145-123 | +9471-455-6-401
Linkedin   Twitter

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

[Dev] Regarding DAS connection with the external spark cluster

[Nayomi Dayarathne]

Hi all,

Given the current situation in DAS, there should be a DAS distribution in
every spark node in an external spark cluster in order to work DAS with
it.That way, external spark cluster able to access jar files which needs to
work with DAS.

Since this is not a better approach,I have already reported an improvement
JIRA[1] regarding this.

Therefore, we want to know whether we are going to implement a solution
according to the JIRA[1] reported or are there any better solution for this
?


[1].https://wso2.org/jira/browse/DAS-197


Regards,

Nayomi Dayarathne

*Software Engineer-QA*
Mobile : +94 (0) 775246619 <+94+(0)+775246619>

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

[Dev] Fwd: Identity SQL exception

[Harshan Liyanage]

adding to @dev


Hi all,

I'm getting this exception when logged into EMM console. Has anyone got any
clue on this?

[2015-10-19 20:15:22,664] ERROR
{org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore}
-  Error while storing session data
org.h2.jdbc.JdbcSQLException: Unique index or primary key violation:
"PRIMARY_KEY_6 ON PUBLIC.IDN_AUTH_SESSION_STORE(SESSION_ID, SESSION_TYPE)";
SQL statement:
INSERT INTO IDN_AUTH_SESSION_STORE(SESSION_ID, SESSION_TYPE,
SESSION_OBJECT, TIME_CREATED) VALUES (?, ?, ?, ?) [23001-140]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:327)
at org.h2.message.DbException.get(DbException.java:167)
at org.h2.message.DbException.get(DbException.java:144)
at org.h2.index.BaseIndex.getDuplicateKeyException(BaseIndex.java:157)
at org.h2.index.PageBtree.find(PageBtree.java:121)
at org.h2.index.PageBtreeLeaf.addRow(PageBtreeLeaf.java:138)
at org.h2.index.PageBtreeLeaf.addRowTry(PageBtreeLeaf.java:93)
at org.h2.index.PageBtreeIndex.addRow(PageBtreeIndex.java:90)
at org.h2.index.PageBtreeIndex.add(PageBtreeIndex.java:81)
at org.h2.table.RegularTable.addRow(RegularTable.java:116)
at org.h2.command.dml.Insert.insertRows(Insert.java:120)
at org.h2.command.dml.Insert.update(Insert.java:82)
at org.h2.command.CommandContainer.update(CommandContainer.java:70)
at org.h2.command.Command.executeUpdate(Command.java:199)
at
org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:141)
at
org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:127)
at
org.wso2.carbon.identity.application.authentication.framework.store.SessionDataStore.persistSessionData(SessionDataStore.java:345)
at
org.wso2.carbon.identity.application.authentication.framework.store.SessionDataPersistTask.run(SessionDataPersistTask.java:53)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

Thanks,

Harshan Liyanage
Software Engineer
Mobile: *+94724423048*
Email: hars...@wso2.com
Blog : http://harshanliyanage.blogspot.com/
*WSO2, Inc. :** wso2.com *
lean.enterprise.middleware.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Incorporated carbon-feature-plugin-2.0.0-m1 in MSS and GW projects

[Afkham Azeez]

I am seeing a lot of introduction of new tags.

e.g. 1. org.wso2.carbon.p2.category.type:server is now written as

org.wso2.carbon.p2.category.type
server


2.
javax.ws.rs:javax.ws.rs-api

is now written as. Also we have the additional burden of specifying the
version again.


   javax.ws.rs-api
${rs-api.version}


Why have we made the configuration more verbose? More XML tags is not
necessarily better.


On Mon, Oct 19, 2015 at 3:42 PM, Dinusha Boteju  wrote:

> Hi all,
>
> I have updated the pom files in WSO2 MSS and WSO2 GW projects to
> incorporate carbon-feature-plugin 2.0.0-m1 and sent pull requests to
> relevant repositories.
>
> jira link for MSS : https://wso2.org/jira/browse/WMS-2
> PR link for MSS : https://github.com/wso2/product-mss/pull/14
>
> jira link for GW   : https://wso2.org/jira/browse/WGW-1
> 
> PR link for GW   : https://github.com/wso2/product-gw/pull/6
>
> Best regards,
> --
> *Dinusha Boteju*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: dinus...@wso2.com 
> phone:(+94) 776640275 <%28%2B94%29%2039736>
>



-- 
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* *
*email: **az...@wso2.com* 
* cell: +94 77 3320919blog: **http://blog.afkham.org*

*twitter: **http://twitter.com/afkham_azeez*

*linked-in: **http://lk.linkedin.com/in/afkhamazeez
*

*Lean . Enterprise . Middleware*
___
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

[Aiyadurai Rajeevan]

Hi All,

What if we implement a pollar which monitor the s2git repo, If the repo is
not ready show a message saying "The environment setup for app creation in
progress, Please wait few moments" and hide that once repo initialization
completed.


Thanks & Regards,
S.A.Rajeevan
Software Engineer WSO2 Inc
E-Mail: rajeev...@wso2.com | Mobile : +94776411636

On Mon, Oct 19, 2015 at 12:08 AM, Samith Dassanayake 
wrote:

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

[Dev] Incorporated carbon-feature-plugin-2.0.0-m1 in MSS and GW projects

[Dinusha Boteju]

Hi all,

I have updated the pom files in WSO2 MSS and WSO2 GW projects to
incorporate carbon-feature-plugin 2.0.0-m1 and sent pull requests to
relevant repositories.

jira link for MSS : https://wso2.org/jira/browse/WMS-2
PR link for MSS : https://github.com/wso2/product-mss/pull/14

jira link for GW   : https://wso2.org/jira/browse/WGW-1

PR link for GW   : https://github.com/wso2/product-gw/pull/6

Best regards,
-- 
*Dinusha Boteju*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: dinus...@wso2.com 
phone:(+94) 776640275 <%28%2B94%29%2039736>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Carbon] DSS DB Console is not available in kernel 4.4.0

[Madhawa Gunasekara]

Hi All,

Issue was fixed by enabling dynamic imports in db console component.
@KasunG I will move this jira to DSS.

Thanks,
Madhawa

On Mon, Oct 19, 2015 at 2:48 PM, Madhawa Gunasekara 
wrote:

> and also this h2 database dependency is bundled by the
> org.wso2.carbon.core.common.feature in Carbon kernel
>
> On Mon, Oct 19, 2015 at 2:44 PM, Madhawa Gunasekara 
> wrote:
>
>> Hi KasunG,
>>
>> I have installed DBConsole feature successfully in DSS. I think Kernel is
>> restricting the H2 db console ui. In dss side we simply expose dbConsole by
>> using an IFrame. because this db Console UI is a built in feature in H2
>> embedded database. That's why I have reported the issue in kernel.
>>
>> Thanks,
>> Madhawa
>>
>> On Fri, Oct 16, 2015 at 4:04 PM, KasunG Gajasinghe 
>> wrote:
>>
>>>
>>> Did you install the dbconsole feature in DSS? Why is this reported
>>> against kernel?
>>>
>>> On Fri, Oct 16, 2015 at 3:57 PM, Madhawa Gunasekara 
>>> wrote:
>>>
 Hi KasunG,

 Yes, I know that thing, but my point is we can't access the mentioned
 urls, I'm getting following response.
 HTTP Status 405 - HTTP method GET is not supported by this URL

 Thanks,
 Madhawa

 On Fri, Oct 16, 2015 at 3:47 PM, KasunG Gajasinghe 
 wrote:

> Hi Madhawa,
>
> We never shipped the dbconsole in kernel. AFAIK, only DSS shipped this
> feature.
>
>
> On Fri, Oct 16, 2015 at 3:45 PM, Madhawa Gunasekara  > wrote:
>
>> Hi Carbon Team,
>>
>> Please find the created jira [1]. This is a regression issue.
>>
>> Previously in DSS 3.2.2 (4.2.0), users were able to view db console
>> using https://localhost:9443/dbconsole/login.jsp and
>> https://localhost:9443/carbon/dbconsole/login.jsp urls.
>>
>> But in Crabon 4.4.0 users can't find the db console.
>>
>> Any help on this matter is highly appreciated.
>>
>> [1] https://wso2.org/jira/browse/CARBON-15524
>>
>> Thanks,
>> Madhawa
>>
>> --
>> *Madhawa Gunasekara*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 719411002 <+94+719411002>
>> blog: *http://madhawa-gunasekara.blogspot.com
>> *
>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>> *
>>
>
>
>
> --
>
> *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
>
>
>



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

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

>>>
>>>
>>>
>>> --
>>>
>>> *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
>>>
>>>
>>>
>>
>>
>>
>> --
>> *Madhawa Gunasekara*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 719411002 <+94+719411002>
>> blog: *http://madhawa-gunasekara.blogspot.com
>> *
>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>> *
>>
>
>
>
> --
> *Madhawa Gunasekara*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 719411002 <+94+719411002>
> blog: *http://madhawa-gunasekara.blogspot.com
> *
> linkedin: *http://lk.linkedin.com/in/mgunasekara
> *
>



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

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Architecture] [Connector + Inbound] RSS/Atom feed Connector + Inbound for WSO2 ESB

[Rajjaz Mohammed]

Hi ,

@ Malaka/kathees
Can you Review my PR https://github.com/wso2/esb-connectors/pull/338

@Nisrin
Can you Review my Documentation
https://docs.wso2.com/pages/viewpage.action?pageId=47520145

On Fri, Oct 16, 2015 at 9:47 AM, Malaka Silva  wrote:

> I think this is good for the initial version. Can you work with kathees
> and add this to the store.
>
> I guess this is in production ready state now. Have we done the load and
> long running tests?
>
> On Fri, Oct 16, 2015 at 9:10 AM, Rajjaz Mohammed  wrote:
>
>> Hi Malaka,
>> i sent the PR for both inbound and connector, and i finish the
>> Documentation for inbound. Since connector only work with testing feed
>> server documentation in pending stage.
>> On 16 Oct 2015 08:40, "Malaka Silva"  wrote:
>>
>>> Hi Rajjaz,
>>>
>>> Guess this is not added to the store yet? Can you please give an update?
>>>
>>> On Thu, Aug 27, 2015 at 12:40 PM, Rajjaz Mohammed 
>>> wrote:
>>>
 Hi Mlaka,
 Since ATOM is an IETF standard while RSS is not[1] I’m using Apache
 abdera Framework[2] because its support with Atom Feed. even when we
 consume the feeds as RSS using  our inbound I’m converting it into Atom and
 then inject it as atom feed to ESB. Since we are using filter operation in
 inbound we can only use mandatory parameters for filter operation otherwise
 it will return NullPointException. So the mandatory parameters for Atom and
 RSS are  title , description/summery and link only.

 [1]
 https://shafiq2410.wordpress.com/2012/08/05/rss-vs-atom-which-one-is-better/
 [2] https://cwiki.apache.org/confluence/display/ABDERA/


 On Thu, Aug 27, 2015 at 11:12 AM, Malaka Silva  wrote:

> Hi Rajjaz,
>
> Can we do this according to the spec.
>
> https://validator.w3.org/feed/docs/rss2.html
>
> On Thu, Aug 27, 2015 at 10:43 AM, Rajjaz Mohammed 
> wrote:
>
>> Hi All,
>> In My case Atom/RSS feed Inbound + Connector I’m working with these
>> parameters so is there any Suggestions on it? because we can expand the
>> feed elements[1] more but it may create errors . below one is the 
>> standard
>> Structure and common for all feeds(Atom/RSS) .
>>
>> mandatory parameters
>>
>> titleThe title of the item.
>> descriptionThe item synopsis.
>>
>> optional parameters
>> authorOwner of the feed
>> pubDateIndicates when the item was published
>>
>>
>>
>> [1] http://www.rssboard.org/rss-specification
>>
>> On Thu, Aug 27, 2015 at 10:38 AM, Rajjaz Mohammed 
>> wrote:
>>
>>> *sorry to all above mails are sent because of short key press
>>>
>>>
>>>
>>> On Thu, Aug 27, 2015 at 10:37 AM, Rajjaz Mohammed 
>>> wrote:
>>>
 Hi All,
 In My case Atom/RSS feed Connector

 mandatory parameters

 *Element**Description*
 *title*The title of the item.
 *link*The URL of the item.
 *description*The item synopsis.

 authorEmail   address of the author of the item
 pubDateIndicates when the item was published

 On Thu, Aug 27, 2015 at 10:36 AM, Rajjaz Mohammed 
 wrote:

> Hi All,
> In My case Atom/RSS feed Connector
>
> mandatory parameters
>
> *Element**Description*
> *title*The title of the item.
> *link*The URL of the item.
> *description*The item synopsis.
>
> authorEmail address of the author of the item
>
>
>
> On Thu, Aug 13, 2015 at 12:38 PM, Rajjaz Mohammed  > wrote:
>
>> Hi All,
>> In My case Atom/RSS feed Connector I’m getting challenge is 3rd
>> party backends are not allowing 3rd party to modify access to feeds 
>> but we
>> can produce the feeds our self. in case Blogger feed editing is not
>> available in api Documentation but it can possible using apache 
>> abdera
>> framework Libraries (According to they Documentation) but when i try 
>> using
>> they authentication method I’m getting null value reply from google 
>> and for
>> the case of wordpress they not allowing to edit feeds rather then 
>> read
>> feeds.
>>
>> i have an idea that using our vfs(file) protocol we can read the
>> files in hosting and most of the feeds are storing inside the site 
>> in XML
>> format so can we access that files using vfs and edit that XML files 
>> and
>> update it back to the site? is that possible?
>>
>> On Tue, Aug 11, 2015 at 3:35 PM, Rajjaz Mohammed > > wrote:
>>
>>> Use Case Diagram
>>>
>>>
>>> https://docs.google.com/a/wso2.com/document/d/1XpqU3z7xbKUb20N5ttvje3wdIR4DuydKqz1

Re: [Dev] [Architecture] carbon-feature-plugin 2.0.0 Milestone 1 Released

[Kishanthan Thangarajah]

Great work Dinusha.

I think we are already working an a migration tool (java and python based)
to ease the migration effort from previous plugin configuration. These
tools will be helpful for users with migration effort.

We have already used this with C5 M5 release. And as the testing effort,
both products GW and MSS can also make use of this new plugin.

On Mon, Oct 19, 2015 at 2:55 PM, Dinusha Boteju  wrote:

> Hi Kasun,
>
> I've mentioned following in the mail; "We are in the process of
> converting this documentation into a document in WSO2 wiki.". So looking
> forward to contact documentation team and add this to wso2 carbon
> documentation.
>
> -Dinusha
>
> On Mon, Oct 19, 2015 at 2:51 PM, Sameera Jayasoma 
> wrote:
>
>> +1. Lets do that with the alpha release of this plugin.
>>
>> Nilmini, we can add this document to C5 doc space. We will let you know
>> once this document is finalized.
>>
>> On Mon, Oct 19, 2015 at 2:18 AM, KasunG Gajasinghe 
>> wrote:
>>
>>> Hi Dinusha,
>>>
>>> Looks good. Could you please share the documentation that is accessible
>>> without a Google login? May be we can add this to wso2 carbon documentation?
>>>
>>> Thanks.
>>>
>>> On Mon, Oct 19, 2015 at 2:43 PM, Dinusha Boteju 
>>> wrote:
>>>
 WSO2 Carbon Feature plugin 2.0.0 - Milestone 01 Released!

 We are pleased to inform you the 1st milestone release of carbon
 feature plugin 2.0.0 is now available to use. Source for this release is
 available here
 .


 carbon-feature-plugin (formerly known as carbon-p2-plugin) is a maven
 plugin developed within the WSO2. With the new 2.0.0 - M1 release we have
 changed the architecture of the tool, changed few maven goals existed in
 previous versions, introduced new features and made the configuration of
 the plugin consistent than before.


 *Features*


- Generate Carbon features
- Generate p2 repositories
- Publish a product into p2 repository
- Generate product Profiles
- Install carbon features into a product profile
- Uninstall carbon features from a product


 These goals are achieved through 6 maven goals defined in the plugin;

- maven goal for generate carbon features  : generate (formerly
known as p2-feature-gen)
- maven goal for generate repositories: generate-repo
(formerly known as p2-repo-gen)
- maven goal for publishing a product  : publish-product
- maven goal for generate profiles   : generate-profile
(formerly known as materialize-product)
- maven goal for install features into a product : install
(formerly known as p2-profile-gen)
- maven goal for uninstalling features  : uninstall

 In the new version, the plugin configuration is different from that of
 the previous versions. Thus please refer the documentation when you use the
 new carbon feature plugin.

 Documentation for WSO2 carbon feature plugin 2.0.0 - M1 can be found
 from here
 .
  We
 are in the process of converting this documentation into a document in WSO2
 wiki.

 *Reporting Issues*

 Since carbon-feature-plugin 2.0.0 - M1 is at it's early stage, please
 report bugs you come across, documentation faults and feature requests
 through the public issue tracking system
 .
 ​
  Carbon-Feature-Plugin documentation
 
 ​

 Thanks,
 WSO2 Carbon Team

 --
 *Dinusha Boteju*
 *WSO2, Inc. http://wso2.com  *
 *lean.enterprise.middleware.*

 email: dinus...@wso2.com 
 phone:(+94) 776640275 <%28%2B94%29%2039736>

>>>
>>>
>>>
>>> --
>>>
>>> *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
>>>
>>>
>>
>>
>> --
>> Sameera Jayasoma,
>> Software Architect,
>>
>> WSO2, Inc. (http://wso2.com)
>> email: same...@wso2.com
>> blog: http://blog.sameera.org
>> twitter: https://twitter.com/sameerajayasoma
>> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>> Mobile: 0094776364456
>>
>> Lean . Enterprise . Middleware
>>
>>
>
>
> --
>
> *Dinusha Boteju*
> *Associate Tech Lead,*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: dinus...@wso2.com 
> phone:(+94) 776640275 <%28%2B

Re: [Dev] carbon-feature-plugin 2.0.0 Milestone 1 Released

[Dinusha Boteju]

Hi Kasun,

I've mentioned following in the mail; "We are in the process of converting
this documentation into a document in WSO2 wiki.". So looking forward to
contact documentation team and add this to wso2 carbon documentation.

-Dinusha

On Mon, Oct 19, 2015 at 2:51 PM, Sameera Jayasoma  wrote:

> +1. Lets do that with the alpha release of this plugin.
>
> Nilmini, we can add this document to C5 doc space. We will let you know
> once this document is finalized.
>
> On Mon, Oct 19, 2015 at 2:18 AM, KasunG Gajasinghe 
> wrote:
>
>> Hi Dinusha,
>>
>> Looks good. Could you please share the documentation that is accessible
>> without a Google login? May be we can add this to wso2 carbon documentation?
>>
>> Thanks.
>>
>> On Mon, Oct 19, 2015 at 2:43 PM, Dinusha Boteju 
>> wrote:
>>
>>> WSO2 Carbon Feature plugin 2.0.0 - Milestone 01 Released!
>>>
>>> We are pleased to inform you the 1st milestone release of carbon feature
>>> plugin 2.0.0 is now available to use. Source for this release is available
>>> here
>>> .
>>>
>>>
>>> carbon-feature-plugin (formerly known as carbon-p2-plugin) is a maven
>>> plugin developed within the WSO2. With the new 2.0.0 - M1 release we have
>>> changed the architecture of the tool, changed few maven goals existed in
>>> previous versions, introduced new features and made the configuration of
>>> the plugin consistent than before.
>>>
>>>
>>> *Features*
>>>
>>>
>>>- Generate Carbon features
>>>- Generate p2 repositories
>>>- Publish a product into p2 repository
>>>- Generate product Profiles
>>>- Install carbon features into a product profile
>>>- Uninstall carbon features from a product
>>>
>>>
>>> These goals are achieved through 6 maven goals defined in the plugin;
>>>
>>>- maven goal for generate carbon features  : generate (formerly
>>>known as p2-feature-gen)
>>>- maven goal for generate repositories: generate-repo
>>>(formerly known as p2-repo-gen)
>>>- maven goal for publishing a product  : publish-product
>>>- maven goal for generate profiles   : generate-profile
>>>(formerly known as materialize-product)
>>>- maven goal for install features into a product : install (formerly
>>>known as p2-profile-gen)
>>>- maven goal for uninstalling features  : uninstall
>>>
>>> In the new version, the plugin configuration is different from that of
>>> the previous versions. Thus please refer the documentation when you use the
>>> new carbon feature plugin.
>>>
>>> Documentation for WSO2 carbon feature plugin 2.0.0 - M1 can be found
>>> from here
>>> .
>>>  We
>>> are in the process of converting this documentation into a document in WSO2
>>> wiki.
>>>
>>> *Reporting Issues*
>>>
>>> Since carbon-feature-plugin 2.0.0 - M1 is at it's early stage, please
>>> report bugs you come across, documentation faults and feature requests
>>> through the public issue tracking system
>>> .
>>> ​
>>>  Carbon-Feature-Plugin documentation
>>> 
>>> ​
>>>
>>> Thanks,
>>> WSO2 Carbon Team
>>>
>>> --
>>> *Dinusha Boteju*
>>> *WSO2, Inc. http://wso2.com  *
>>> *lean.enterprise.middleware.*
>>>
>>> email: dinus...@wso2.com 
>>> phone:(+94) 776640275 <%28%2B94%29%2039736>
>>>
>>
>>
>>
>> --
>>
>> *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
>>
>>
>
>
> --
> Sameera Jayasoma,
> Software Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://blog.sameera.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> Mobile: 0094776364456
>
> Lean . Enterprise . Middleware
>
>


-- 

*Dinusha Boteju*
*Associate Tech Lead,*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: dinus...@wso2.com 
phone:(+94) 776640275 <%28%2B94%29%2039736>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] carbon-feature-plugin 2.0.0 Milestone 1 Released

[Sameera Jayasoma]

+1. Lets do that with the alpha release of this plugin.

Nilmini, we can add this document to C5 doc space. We will let you know
once this document is finalized.

On Mon, Oct 19, 2015 at 2:18 AM, KasunG Gajasinghe  wrote:

> Hi Dinusha,
>
> Looks good. Could you please share the documentation that is accessible
> without a Google login? May be we can add this to wso2 carbon documentation?
>
> Thanks.
>
> On Mon, Oct 19, 2015 at 2:43 PM, Dinusha Boteju  wrote:
>
>> WSO2 Carbon Feature plugin 2.0.0 - Milestone 01 Released!
>>
>> We are pleased to inform you the 1st milestone release of carbon feature
>> plugin 2.0.0 is now available to use. Source for this release is available
>> here 
>> .
>>
>>
>> carbon-feature-plugin (formerly known as carbon-p2-plugin) is a maven
>> plugin developed within the WSO2. With the new 2.0.0 - M1 release we have
>> changed the architecture of the tool, changed few maven goals existed in
>> previous versions, introduced new features and made the configuration of
>> the plugin consistent than before.
>>
>>
>> *Features*
>>
>>
>>- Generate Carbon features
>>- Generate p2 repositories
>>- Publish a product into p2 repository
>>- Generate product Profiles
>>- Install carbon features into a product profile
>>- Uninstall carbon features from a product
>>
>>
>> These goals are achieved through 6 maven goals defined in the plugin;
>>
>>- maven goal for generate carbon features  : generate (formerly known
>>as p2-feature-gen)
>>- maven goal for generate repositories: generate-repo
>>(formerly known as p2-repo-gen)
>>- maven goal for publishing a product  : publish-product
>>- maven goal for generate profiles   : generate-profile
>>(formerly known as materialize-product)
>>- maven goal for install features into a product : install (formerly
>>known as p2-profile-gen)
>>- maven goal for uninstalling features  : uninstall
>>
>> In the new version, the plugin configuration is different from that of
>> the previous versions. Thus please refer the documentation when you use the
>> new carbon feature plugin.
>>
>> Documentation for WSO2 carbon feature plugin 2.0.0 - M1 can be found from
>> here
>> .
>>  We
>> are in the process of converting this documentation into a document in WSO2
>> wiki.
>>
>> *Reporting Issues*
>>
>> Since carbon-feature-plugin 2.0.0 - M1 is at it's early stage, please
>> report bugs you come across, documentation faults and feature requests
>> through the public issue tracking system
>> .
>> ​
>>  Carbon-Feature-Plugin documentation
>> 
>> ​
>>
>> Thanks,
>> WSO2 Carbon Team
>>
>> --
>> *Dinusha Boteju*
>> *WSO2, Inc. http://wso2.com  *
>> *lean.enterprise.middleware.*
>>
>> email: dinus...@wso2.com 
>> phone:(+94) 776640275 <%28%2B94%29%2039736>
>>
>
>
>
> --
>
> *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
>
>


-- 
Sameera Jayasoma,
Software Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://blog.sameera.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
Mobile: 0094776364456

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

Re: [Dev] [Carbon] DSS DB Console is not available in kernel 4.4.0

[Madhawa Gunasekara]

and also this h2 database dependency is bundled by the
org.wso2.carbon.core.common.feature in Carbon kernel

On Mon, Oct 19, 2015 at 2:44 PM, Madhawa Gunasekara 
wrote:

> Hi KasunG,
>
> I have installed DBConsole feature successfully in DSS. I think Kernel is
> restricting the H2 db console ui. In dss side we simply expose dbConsole by
> using an IFrame. because this db Console UI is a built in feature in H2
> embedded database. That's why I have reported the issue in kernel.
>
> Thanks,
> Madhawa
>
> On Fri, Oct 16, 2015 at 4:04 PM, KasunG Gajasinghe 
> wrote:
>
>>
>> Did you install the dbconsole feature in DSS? Why is this reported
>> against kernel?
>>
>> On Fri, Oct 16, 2015 at 3:57 PM, Madhawa Gunasekara 
>> wrote:
>>
>>> Hi KasunG,
>>>
>>> Yes, I know that thing, but my point is we can't access the mentioned
>>> urls, I'm getting following response.
>>> HTTP Status 405 - HTTP method GET is not supported by this URL
>>>
>>> Thanks,
>>> Madhawa
>>>
>>> On Fri, Oct 16, 2015 at 3:47 PM, KasunG Gajasinghe 
>>> wrote:
>>>
 Hi Madhawa,

 We never shipped the dbconsole in kernel. AFAIK, only DSS shipped this
 feature.


 On Fri, Oct 16, 2015 at 3:45 PM, Madhawa Gunasekara 
 wrote:

> Hi Carbon Team,
>
> Please find the created jira [1]. This is a regression issue.
>
> Previously in DSS 3.2.2 (4.2.0), users were able to view db console
> using https://localhost:9443/dbconsole/login.jsp and
> https://localhost:9443/carbon/dbconsole/login.jsp urls.
>
> But in Crabon 4.4.0 users can't find the db console.
>
> Any help on this matter is highly appreciated.
>
> [1] https://wso2.org/jira/browse/CARBON-15524
>
> Thanks,
> Madhawa
>
> --
> *Madhawa Gunasekara*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 719411002 <+94+719411002>
> blog: *http://madhawa-gunasekara.blogspot.com
> *
> linkedin: *http://lk.linkedin.com/in/mgunasekara
> *
>



 --

 *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



>>>
>>>
>>>
>>> --
>>> *Madhawa Gunasekara*
>>> Software Engineer
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: +94 719411002 <+94+719411002>
>>> blog: *http://madhawa-gunasekara.blogspot.com
>>> *
>>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>>> *
>>>
>>
>>
>>
>> --
>>
>> *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
>>
>>
>>
>
>
>
> --
> *Madhawa Gunasekara*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 719411002 <+94+719411002>
> blog: *http://madhawa-gunasekara.blogspot.com
> *
> linkedin: *http://lk.linkedin.com/in/mgunasekara
> *
>



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

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] carbon-feature-plugin 2.0.0 Milestone 1 Released

[KasunG Gajasinghe]

Hi Dinusha,

Looks good. Could you please share the documentation that is accessible
without a Google login? May be we can add this to wso2 carbon documentation?

Thanks.

On Mon, Oct 19, 2015 at 2:43 PM, Dinusha Boteju  wrote:

> WSO2 Carbon Feature plugin 2.0.0 - Milestone 01 Released!
>
> We are pleased to inform you the 1st milestone release of carbon feature
> plugin 2.0.0 is now available to use. Source for this release is available
> here .
>
>
> carbon-feature-plugin (formerly known as carbon-p2-plugin) is a maven
> plugin developed within the WSO2. With the new 2.0.0 - M1 release we have
> changed the architecture of the tool, changed few maven goals existed in
> previous versions, introduced new features and made the configuration of
> the plugin consistent than before.
>
>
> *Features*
>
>
>- Generate Carbon features
>- Generate p2 repositories
>- Publish a product into p2 repository
>- Generate product Profiles
>- Install carbon features into a product profile
>- Uninstall carbon features from a product
>
>
> These goals are achieved through 6 maven goals defined in the plugin;
>
>- maven goal for generate carbon features  : generate (formerly known
>as p2-feature-gen)
>- maven goal for generate repositories: generate-repo
>(formerly known as p2-repo-gen)
>- maven goal for publishing a product  : publish-product
>- maven goal for generate profiles   : generate-profile
>(formerly known as materialize-product)
>- maven goal for install features into a product : install (formerly
>known as p2-profile-gen)
>- maven goal for uninstalling features  : uninstall
>
> In the new version, the plugin configuration is different from that of the
> previous versions. Thus please refer the documentation when you use the new
> carbon feature plugin.
>
> Documentation for WSO2 carbon feature plugin 2.0.0 - M1 can be found from
> here
> .
>  We
> are in the process of converting this documentation into a document in WSO2
> wiki.
>
> *Reporting Issues*
>
> Since carbon-feature-plugin 2.0.0 - M1 is at it's early stage, please
> report bugs you come across, documentation faults and feature requests
> through the public issue tracking system
> .
> ​
>  Carbon-Feature-Plugin documentation
> 
> ​
>
> Thanks,
> WSO2 Carbon Team
>
> --
> *Dinusha Boteju*
> *WSO2, Inc. http://wso2.com  *
> *lean.enterprise.middleware.*
>
> email: dinus...@wso2.com 
> phone:(+94) 776640275 <%28%2B94%29%2039736>
>



-- 

*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

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

[Fazlan Nazeem]

Hi Nifras,

It is actually in a serialized binary format. So there is no way to read it
through a text editor. But you can use this serialized model file in any of
the mentioned methods which are specified in the documentation link I
provided.




On Mon, Oct 19, 2015 at 2:38 PM, NIFRAS ISMAIL 
wrote:

> Hi,
> Finally I have download the file on .model format. How can i open and
> read? How can i make use of it?
>
> OMG. I didn't hear how to do this?
>
> I am an Linux one.
>
> Note: I have attached the output model on attachments.
>
> Thank you
>
> Regards.
> *M. Nifras Ismail*
> [image: LinkedIn] 
>
>
>
> On Mon, Oct 19, 2015 at 12:16 PM, Fazlan Nazeem  wrote:
>
>> 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
>>
>
>


-- 
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] [Carbon] DSS DB Console is not available in kernel 4.4.0

[Madhawa Gunasekara]

Hi KasunG,

I have installed DBConsole feature successfully in DSS. I think Kernel is
restricting the H2 db console ui. In dss side we simply expose dbConsole by
using an IFrame. because this db Console UI is a built in feature in H2
embedded database. That's why I have reported the issue in kernel.

Thanks,
Madhawa

On Fri, Oct 16, 2015 at 4:04 PM, KasunG Gajasinghe  wrote:

>
> Did you install the dbconsole feature in DSS? Why is this reported against
> kernel?
>
> On Fri, Oct 16, 2015 at 3:57 PM, Madhawa Gunasekara 
> wrote:
>
>> Hi KasunG,
>>
>> Yes, I know that thing, but my point is we can't access the mentioned
>> urls, I'm getting following response.
>> HTTP Status 405 - HTTP method GET is not supported by this URL
>>
>> Thanks,
>> Madhawa
>>
>> On Fri, Oct 16, 2015 at 3:47 PM, KasunG Gajasinghe 
>> wrote:
>>
>>> Hi Madhawa,
>>>
>>> We never shipped the dbconsole in kernel. AFAIK, only DSS shipped this
>>> feature.
>>>
>>>
>>> On Fri, Oct 16, 2015 at 3:45 PM, Madhawa Gunasekara 
>>> wrote:
>>>
 Hi Carbon Team,

 Please find the created jira [1]. This is a regression issue.

 Previously in DSS 3.2.2 (4.2.0), users were able to view db console
 using https://localhost:9443/dbconsole/login.jsp and
 https://localhost:9443/carbon/dbconsole/login.jsp urls.

 But in Crabon 4.4.0 users can't find the db console.

 Any help on this matter is highly appreciated.

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

 Thanks,
 Madhawa

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

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

>>>
>>>
>>>
>>> --
>>>
>>> *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
>>>
>>>
>>>
>>
>>
>>
>> --
>> *Madhawa Gunasekara*
>> Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 719411002 <+94+719411002>
>> blog: *http://madhawa-gunasekara.blogspot.com
>> *
>> linkedin: *http://lk.linkedin.com/in/mgunasekara
>> *
>>
>
>
>
> --
>
> *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
>
>
>



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

mobile: +94 719411002 <+94+719411002>
blog: *http://madhawa-gunasekara.blogspot.com
*
linkedin: *http://lk.linkedin.com/in/mgunasekara
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] carbon-feature-plugin 2.0.0 Milestone 1 Released

[Dinusha Boteju]

WSO2 Carbon Feature plugin 2.0.0 - Milestone 01 Released!

We are pleased to inform you the 1st milestone release of carbon feature
plugin 2.0.0 is now available to use. Source for this release is available
here .


carbon-feature-plugin (formerly known as carbon-p2-plugin) is a maven
plugin developed within the WSO2. With the new 2.0.0 - M1 release we have
changed the architecture of the tool, changed few maven goals existed in
previous versions, introduced new features and made the configuration of
the plugin consistent than before.


*Features*


   - Generate Carbon features
   - Generate p2 repositories
   - Publish a product into p2 repository
   - Generate product Profiles
   - Install carbon features into a product profile
   - Uninstall carbon features from a product


These goals are achieved through 6 maven goals defined in the plugin;

   - maven goal for generate carbon features  : generate (formerly known as
   p2-feature-gen)
   - maven goal for generate repositories: generate-repo (formerly
   known as p2-repo-gen)
   - maven goal for publishing a product  : publish-product
   - maven goal for generate profiles   : generate-profile
   (formerly known as materialize-product)
   - maven goal for install features into a product : install (formerly
   known as p2-profile-gen)
   - maven goal for uninstalling features  : uninstall

In the new version, the plugin configuration is different from that of the
previous versions. Thus please refer the documentation when you use the new
carbon feature plugin.

Documentation for WSO2 carbon feature plugin 2.0.0 - M1 can be found from
here
.
We
are in the process of converting this documentation into a document in WSO2
wiki.

*Reporting Issues*

Since carbon-feature-plugin 2.0.0 - M1 is at it's early stage, please
report bugs you come across, documentation faults and feature requests
through the public issue tracking system
.
​
 Carbon-Feature-Plugin documentation

​

Thanks,
WSO2 Carbon Team

-- 
*Dinusha Boteju*
*WSO2, Inc. http://wso2.com  *
*lean.enterprise.middleware.*

email: dinus...@wso2.com 
phone:(+94) 776640275 <%28%2B94%29%2039736>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

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

[NIFRAS ISMAIL]

Hi,
Finally I have download the file on .model format. How can i open and read?
How can i make use of it?

OMG. I didn't hear how to do this?

I am an Linux one.

Note: I have attached the output model on attachments.

Thank you

Regards.
*M. Nifras Ismail*
[image: LinkedIn] 



On Mon, Oct 19, 2015 at 12:16 PM, Fazlan Nazeem  wrote:

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


myanalysis2.Model.2015-10-19_00-35-24
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Jaggery] response.sendError() not working for PUT and DELETE

[Thilini Cooray]

Hi,

I want to send error messages for invalid URLs from API Manager Store
jaggery layer.

I use response.sendError(404) for this purpose.
For HTTP POST and GET this method returns the correct error page while it
doesn't return any message for PUT and DELETE.

I debugged [1] and found out that the errors send in all HTTP methods gets
hit in

rho.response.sendError((Integer) args[0]);

Output stream of rho.response also contains the correct error page in all
HTTP methods.
Yet it doesn't get returned in HTTP PUT and DELETE methods.

I am unable to figure out the reason for this behaviour.
Any help is appreciated.

Thanks.

[1]
http://svn.wso2.org/repos/wso2/carbon/platform/tags/turing-chunk04/components/jaggery/0.9.0.ALPHA4.wso2v1/hostobjects/org.jaggeryjs.hostobjects.web/src/main/java/org/jaggeryjs/hostobjects/web/ResponseHostObject.java

-- 
Best Regards,

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

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

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

[Sanjeewa Malalgoda]

Here idea is easily manage the tests and web application.
Since web application purely depend on swagger definition it will
automatically generate beans, service skeletons etc.

So in same way if we implement test cases we don't have to go and edit test
case code after we adding new parameters or something like that.
What we can simply do is change sample data set feed into test.



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

> Hi Nuwan
>
> Thanks for pointing that out, in that case test can be version-ed so auto
> generated tests for version 1.0.0 should work with API 1.0.1 ...
>
> WDYT?
>
> Regards
> Jo
>
> On Mon, Oct 19, 2015 at 12:29 PM, Nuwan Dias  wrote:
>
>> 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.
>>
> I don't get how we loose advantage here.
If we don't want to change service API we don't have to edit swagger json
and that is it.
Then it will not change service API, neither test client or data set feed
in to test.
If we consider both integration and unit tests those will be released
anyway with product and component release.
So tests will be automatically version-ed with component/product version.

Thanks,
sanjeewa.


>
>> 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 <
> sanje...@wso2.com> 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,

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

[Dharshana Warusavitharana]

Hi Jo,

If so the issue is how you eliminate the client generation on normal
product build. So if there is a requirement of maintaining API as it is it
is a bad idea it generate test client on demand.
So in bottom line you only expect API change for 1.0.0 in next main release
2.0.0. So this won't be a issue to refine clients when it comes to major
release.

You can mountain all API definitions on a single place referring base class
method. So changes would be minimal when you do a major release with API
change.

Thank you,
Dharshana.

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

> Hi Nuwan
>
> Thanks for pointing that out, in that case test can be version-ed so auto
> generated tests for version 1.0.0 should work with API 1.0.1 ...
>
> WDYT?
>
> Regards
> Jo
>
> On Mon, Oct 19, 2015 at 12:29 PM, Nuwan Dias  wrote:
>
>> 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 <
> sanje...@wso2.com> 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/
>> 
>>
>>

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

[Joseph Fonseka]

Hi Nuwan

Thanks for pointing that out, in that case test can be version-ed so auto
generated tests for version 1.0.0 should work with API 1.0.1 ...

WDYT?

Regards
Jo

On Mon, Oct 19, 2015 at 12:29 PM, Nuwan Dias  wrote:

> 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