[Dev] WSO2 Stream Processor 4.0.0-M8 Released !

[Minudika Malshan]

Hi All,

The WSO2 Analytics team is pleased to announce the release of WSO2 Stream
Processor Version 4.0.0 Milestone 8.

WSO2 Smart Analytics let digital business creating real-time, intelligent,
actionable business insights, and data products which are achieved by WSO2
Stream Processor's real-time, incremental & intelligent data processing
capabilities.

WSO2 Stream Processor can:

Receive events from various data sources
Process & correlate them in real-time with the sate of the art
high-performance real-time Siddhi Complex Event Processing Engine that
works with easy to learn the SQL-Like query language.
Process analysis that spans for longer time duration with its
incremental processing capability by achieving high performance with low
infrastructure cost.
Uses Machine Learning and other models to drive intelligent insights
from the data
Notifications interesting event occurrences as alerts via multiple
types of transport & let users visualize the results via customizable
dashboards.
WSO2 SP is released under Apache Software License Version 2.0, one of
the most business-friendly licenses available today.

You can find the product at https://github.com/wso2/
product-sp/releases/download/v4.0.0-M8/wso2sp-4.0.0-M8.zip
Documentation at https://docs.wso2.com/display/SP400/
Source code at https://github.com/wso2/product-sp/releases/tag/v4.0.0-M8

*WSO2 SP 4.0.0-M8 includes following*

*New Features*

   -  Feed simulation support in editor
   -  Set keyword for siddhi
   -  Siddhi-io-http
   -  Siddhi App query API
   -  Siddhi store unification

*Reporting Issues*

Issues can be reported using the github issue tracker available at
https://github.com/wso2/product-sp/issues


*Contact us*
WSO2 Stream Processor developers can be contacted via the mailing lists:
Developer List : dev@wso2.org | Subscribe
 | Mail Archive


Alternatively, questions can also be raised in the stackoverflow:

Forum http://stackoverflow.com/questions/tagged/wso2/


*Support *

We are committed to ensuring that your enterprise middleware deployment is
completely supported from evaluation to production. Our unique approach
ensures that all support leverages our open development methodology and is
provided by the very same engineers who build the technology.

For more details and to take advantage of this unique opportunity please
visit http://wso2.com/support/.

For more information on WSO2 Smart Analytics and Smart Analytics Solutions,
visit the WSO2 Smart Analytics Page .


*~ The WSO2 Analytics Team ~*

-- 
*Minudika Gammanpila*
Software Engineer - WSO2

Email   :  minud...@wso2.com
Mobile :  +94715659887
Web :  http://wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] DSS Improvement

[Madhawa Gunasekara]

Yes, In that case, It's a valid point. We will consider this improvement
into next EI 6.2.0 release. Thanks for the suggestion.

Regards,
Madhawa

On Thu, Aug 3, 2017 at 6:29 PM, Ricardo De Souza  wrote:

> Hi Madhawa,
>
> I see.
> We still have some requirements where customers want to expose in both
> format XML and JSON. Said that what is your advice to address this
> scenario?
>
> Thanks
>
>
> *Ricardo Souza |  rica...@wso2.com  *
>
>
> Solution Architect, Latin America | *WSO2* Inc.
>
> Mobile : +55 11 9 7563 8066
>
> 
>
> On Thu, Aug 3, 2017 at 9:21 AM, Madhawa Gunasekara 
> wrote:
>
>> Hi Ricardo,
>>
>> Yes, but I believe the user should handle these namespaces, if a customer
>> needs to get a response in JSON format then the customer should use the
>> JSON mapping, rather using XML mapping. [1]
>>
>> [1]  https://docs.wso2.com/display/DSS350/JSON+Mapping
>>
>> Thanks,
>> Madhawa
>>
>> On Thu, Jul 27, 2017 at 2:24 PM, Ricardo De Souza 
>> wrote:
>>
>>> Hi,
>>>
>>> I do not know if this is the correct channel if it is not please let me
>>> know how I can request this improvements in the product.
>>>
>>> I got an error when trying to get the response in JSON format.
>>> I created two queries with the same grouped by element and row name and
>>> no namespace. The UI allows us to do this.
>>> After adding a namespace for one of the queries it works.
>>> My suggestion is to generate a unique namespace for the row namespace if
>>> the user does not specify one.
>>>
>>> The error I got was:
>>>
>>> DS Code: DATABASE_ERROR
>>> Source Data Service:-
>>> Name: NorthwindDS
>>> Location: \NorthwindDS.dbs
>>> Description: N/A
>>> Default Namespace: br.com.northwind
>>> Current Request Name: _getemployee_employeeid
>>> Current Params: {EmployeeID=8}
>>> Nested Exception:-
>>> DS Fault Message: Error in XML generation at StaticOutputElement.execute
>>> DS Code: UNKNOWN_ERROR
>>> Nested Exception:-
>>> javax.xml.stream.XMLStreamException: Invalid Staring element
>>>
>>> Thanks
>>>
>>>
>>> *Ricardo Souza |  rica...@wso2.com  *
>>>
>>>
>>> Solution Architect, Latin America | *WSO2* Inc.
>>>
>>> Mobile : +55 11 9 7563 8066
>>>
>>> 
>>>
>>
>>
>>
>> --
>> *Madhawa Gunasekara*
>> Senior 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*
Senior 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] Passing Parameters to the Implementation [Production and Sandbox] urls

[Sagar Kapadia]

Right thats what happened. It is necessary to pass the complete url to
test, otherwise there is a 404 error. However, while saving, it is
necessary to remove the duplicated parts of the url. I figured this out by
checking the logs of the implementing web service
sagar

On Thu, Aug 3, 2017 at 2:03 PM, Rasika Perera  wrote:

> By the way, I had to give http://192.168.11.65:8000/BizBrainTally/api
>> 
>>  as
>> the end point and not http://192.168.11.65:8000/
>> BizBrainTally/api/ledgers/customers/
>>
>> This
>> allowed the call to succeed but the clicking the test button showed failed
>
> ​Glad to hear it worked! Yes, as I mentioned earlier it depends on how you
> allow clients to call the API. In your case you might call the API with
> https://​:8280/​
> BizBrainTally/api/
> ​1.0/​
> ledgers/
> ​customers/Test".
>
> This allowed the call to succeed but the clicking the test button showed
>> failed
>
> ​AFAIK, Test button simply checks the endpoint with a GET call.​
>  http://192.168.11.65:8000/BizBrainTally/api/
> ​​
>
> 
>
> ​would have sent a 404 in this case.​
>
> On Thu, Aug 3, 2017 at 1:34 PM, Sagar Kapadia  wrote:
>
>> By the way, I had to give http://192.168.11.65:8000/BizBrainTally/api
>> 
>>  as
>> the end point and not http://192.168.11.65:8000/
>> BizBrainTally/api/ledgers/customers/
>> 
>> This allowed the call to succeed but the clicking the test button showed
>> failed
>>
>>
>> On Thu, Aug 3, 2017 at 1:29 PM, Sagar Kapadia  wrote:
>>
>>> Thanks Rasika,
>>> Thanks, I got it working.
>>>
>>> On Thu, Aug 3, 2017 at 1:18 PM, Rasika Perera  wrote:
>>>
 Hi Sagara,

 I think you are confused with API endpoint and the resource paths.
 Please refer [1] as an example. Path parameters are not allowed for the
 "Production EndPoint".

 *Your resource path should be:*
 /{Company}

 *Your endpoint should be : *
 http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/
 

 You can also try "/customers/{Company}" as resource path and "
 http://192.168.11.65:8000/BizBrainTally/api/ledgers/"; as the endpoint
 too. This depends on the granularity and resource paths of the API
 that you are hoping to expose through WSO2 API Manager.

 [1] https://docs.wso2.com/display/AM210/Create+and+Publish+an+API

 On Thu, Aug 3, 2017 at 1:05 PM, Sagar Kapadia 
 wrote:

> Hi Rasika and Abimaran,
>
> I am accepting a parameter on the front end rest api. Now I need to
> pass this parameter to the implementing api. How do I do that.
>
> The following is the implementing api
>
> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customer
> s/{company}
>
> But adding {company} causes the test to fail with invalid message, and
> if I remove {company}, I get a 404 Error from the implementing server.
>
> The test succeeds if I put the following url
> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/Test
> where "Test" is the parameter
>
> I am attaching screen shots to show what I mean.
>
> Sagar
>
> On Thu, Aug 3, 2017 at 12:37 PM, Sagar Kapadia 
> wrote:
>
>> Hi Rasika!
>> Thanks for your reply. I checked via ipconfig and its my IP. sorry
>> for the confusion. I have two ips. Now the next question is how to pass
>> parameters to the implementation endpoint. Or at least, if I can log the
>> request being made to the end point it would be very helpful, since I am
>> not getting any response from the server, but if I call the end point 
>> from
>> the browser, I get a valid response
>> Sagar
>>
>> On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera 
>> wrote:
>>
>>> Hi Sagar,
>>>
>>> Are you using VMware or virtualbox? Please check your network
>>> interfaces. Sometimes WSO2 Server could have binded into a wrong network
>>> interface when there are multiple network interfaces in the host 
>>> machine.
>>>
>>> You can check this with ifconfig(in linux) or ipconfig(in windows).
>>>
>>> Best Regards,
>>> Rasika
>>>
>>> On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia 
>>> wrote:
>>>
 Abimaran,
 Actually, API manager is running on 192.168.11.68 and not 
 192.168.144.2.
 I am making a call to API manager via the swagger definition in the api
 store. However, the end point doesnt get hit because it is pointing to 
 the
 wrong url

Re: [Dev] How to create a websocket implementation of an end point

[Sagar Kapadia]

Hi Arshardh,
Thanks for your reply
Sagar



On Thu, Aug 3, 2017 at 2:28 PM, Arshardh Ifthikar <
arshardhifthi...@gmail.com> wrote:

> Hi Sagar,
> Currently (WSO2 API manager 2.1) it isn't possible to add a websocket
> endpoint to a REST api. This is because currently synapse support
> websockets through inbound endpoints. A websocket endpoint can only be
> added to a Websocket API.
>
> Thank You.
>
> On Thu, Aug 3, 2017 at 12:57 PM, Sagar Kapadia  wrote:
>
>> Hi Abimaran,
>> I got that , thanks. My specific need is a front end REST API with a back
>> end [implementation endpoint] being a web socket.
>> i see options for REST and SOAP and Dynamic Endpoints, but none for a
>> websocket endpoint. Is this possible?
>> If I want to set the production or sandbox url to
>> ws://localhost:1880/api, I cant figure out a way to do this. I entered the
>> url for the websocket in the text field, but then in the store, the api
>> console tab is missing.
>> Sagar
>>
>>
>> On Wed, Aug 2, 2017 at 6:27 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Sagar,
>>>
>>> WebSocket APIs are introduced in 2.1, it's in 'Design' tab as below.
>>>
>>>
>>>
>>> ​
>>>
>>> On Wed, Aug 2, 2017 at 4:20 PM, Sagar Kapadia 
>>> wrote:
>>>
 Hi,
 I cant see a way to create a web socket endpoint implementation .Please
 let me know how to do this
 Sagar

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


>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820 <+94%2077%20392%202820>
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to create a websocket implementation of an end point

[Arshardh Ifthikar]

Hi Sagar,
Currently (WSO2 API manager 2.1) it isn't possible to add a websocket
endpoint to a REST api. This is because currently synapse support
websockets through inbound endpoints. A websocket endpoint can only be
added to a Websocket API.

Thank You.

On Thu, Aug 3, 2017 at 12:57 PM, Sagar Kapadia  wrote:

> Hi Abimaran,
> I got that , thanks. My specific need is a front end REST API with a back
> end [implementation endpoint] being a web socket.
> i see options for REST and SOAP and Dynamic Endpoints, but none for a
> websocket endpoint. Is this possible?
> If I want to set the production or sandbox url to ws://localhost:1880/api,
> I cant figure out a way to do this. I entered the url for the websocket in
> the text field, but then in the store, the api console tab is missing.
> Sagar
>
>
> On Wed, Aug 2, 2017 at 6:27 PM, Abimaran Kugathasan 
> wrote:
>
>> Hi Sagar,
>>
>> WebSocket APIs are introduced in 2.1, it's in 'Design' tab as below.
>>
>>
>>
>> ​
>>
>> On Wed, Aug 2, 2017 at 4:20 PM, Sagar Kapadia  wrote:
>>
>>> Hi,
>>> I cant see a way to create a web socket endpoint implementation .Please
>>> let me know how to do this
>>> Sagar
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thanks
>> Abimaran Kugathasan
>> Senior Software Engineer - API Technologies
>>
>> Email : abima...@wso2.com
>> Mobile : +94 773922820 <+94%2077%20392%202820>
>>
>> 
>> 
>>   
>> 
>>
>>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Passing Parameters to the Implementation [Production and Sandbox] urls

[Rasika Perera]

>
> By the way, I had to give http://192.168.11.65:8000/BizBrainTally/api
>  
> as
> the end point and not http://192.168.11.65:8000/
> BizBrainTally/api/ledgers/customers/
>
> This
> allowed the call to succeed but the clicking the test button showed failed

​Glad to hear it worked! Yes, as I mentioned earlier it depends on how you
allow clients to call the API. In your case you might call the API with
https://​:8280/​
BizBrainTally/api/
​1.0/​
ledgers/
​customers/Test".

This allowed the call to succeed but the clicking the test button showed
> failed

​AFAIK, Test button simply checks the endpoint with a GET call.​
 http://192.168.11.65:8000/BizBrainTally/api/
​​


​would have sent a 404 in this case.​

On Thu, Aug 3, 2017 at 1:34 PM, Sagar Kapadia  wrote:

> By the way, I had to give http://192.168.11.65:8000/BizBrainTally/api
>  
> as
> the end point and not http://192.168.11.65:8000/BizBrainTally/api/ledgers/
> customers/
> 
> This allowed the call to succeed but the clicking the test button showed
> failed
>
>
> On Thu, Aug 3, 2017 at 1:29 PM, Sagar Kapadia  wrote:
>
>> Thanks Rasika,
>> Thanks, I got it working.
>>
>> On Thu, Aug 3, 2017 at 1:18 PM, Rasika Perera  wrote:
>>
>>> Hi Sagara,
>>>
>>> I think you are confused with API endpoint and the resource paths.
>>> Please refer [1] as an example. Path parameters are not allowed for the
>>> "Production EndPoint".
>>>
>>> *Your resource path should be:*
>>> /{Company}
>>>
>>> *Your endpoint should be : *
>>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/
>>> 
>>>
>>> You can also try "/customers/{Company}" as resource path and "
>>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/"; as the endpoint
>>> too. This depends on the granularity and resource paths of the API that
>>> you are hoping to expose through WSO2 API Manager.
>>>
>>> [1] https://docs.wso2.com/display/AM210/Create+and+Publish+an+API
>>>
>>> On Thu, Aug 3, 2017 at 1:05 PM, Sagar Kapadia 
>>> wrote:
>>>
 Hi Rasika and Abimaran,

 I am accepting a parameter on the front end rest api. Now I need to
 pass this parameter to the implementing api. How do I do that.

 The following is the implementing api

 http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/{company}

 But adding {company} causes the test to fail with invalid message, and
 if I remove {company}, I get a 404 Error from the implementing server.

 The test succeeds if I put the following url
 http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/Test
 where "Test" is the parameter

 I am attaching screen shots to show what I mean.

 Sagar

 On Thu, Aug 3, 2017 at 12:37 PM, Sagar Kapadia 
 wrote:

> Hi Rasika!
> Thanks for your reply. I checked via ipconfig and its my IP. sorry for
> the confusion. I have two ips. Now the next question is how to pass
> parameters to the implementation endpoint. Or at least, if I can log the
> request being made to the end point it would be very helpful, since I am
> not getting any response from the server, but if I call the end point from
> the browser, I get a valid response
> Sagar
>
> On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera 
> wrote:
>
>> Hi Sagar,
>>
>> Are you using VMware or virtualbox? Please check your network
>> interfaces. Sometimes WSO2 Server could have binded into a wrong network
>> interface when there are multiple network interfaces in the host machine.
>>
>> You can check this with ifconfig(in linux) or ipconfig(in windows).
>>
>> Best Regards,
>> Rasika
>>
>> On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia 
>> wrote:
>>
>>> Abimaran,
>>> Actually, API manager is running on 192.168.11.68 and not 192.168.144.2.
>>> I am making a call to API manager via the swagger definition in the api
>>> store. However, the end point doesnt get hit because it is pointing to 
>>> the
>>> wrong url [192.168.144.2.] instead of 192.168.11.65
>>> Sagar
>>>
>>> On Wed, Aug 2, 2017 at 6:15 PM, Abimaran Kugathasan <
>>> abima...@wso2.com> wrote:
>>>
 Hi Sagar,

 API Manager runs on 192.168.144.2 and this IP is shown in Store UI.
 If you want to hit the backend directly from your client, then there 
 isn't
 any reason for using API Manager. I don't understand why you are 
 expecting
 to hit backend URL direct

Re: [Dev] Passing Parameters to the Implementation [Production and Sandbox] urls

[Sagar Kapadia]

By the way, I had to give http://192.168.11.65:8000/BizBrainTally/api

as
the end point and not http://192.168.11.65:8000/BizB
rainTally/api/ledgers/customers/

This allowed the call to succeed but the clicking the test button showed
failed


On Thu, Aug 3, 2017 at 1:29 PM, Sagar Kapadia  wrote:

> Thanks Rasika,
> Thanks, I got it working.
>
> On Thu, Aug 3, 2017 at 1:18 PM, Rasika Perera  wrote:
>
>> Hi Sagara,
>>
>> I think you are confused with API endpoint and the resource paths. Please
>> refer [1] as an example. Path parameters are not allowed for the
>> "Production EndPoint".
>>
>> *Your resource path should be:*
>> /{Company}
>>
>> *Your endpoint should be : *
>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/
>> 
>>
>> You can also try "/customers/{Company}" as resource path and "
>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/"; as the endpoint
>> too. This depends on the granularity and resource paths of the API that
>> you are hoping to expose through WSO2 API Manager.
>>
>> [1] https://docs.wso2.com/display/AM210/Create+and+Publish+an+API
>>
>> On Thu, Aug 3, 2017 at 1:05 PM, Sagar Kapadia  wrote:
>>
>>> Hi Rasika and Abimaran,
>>>
>>> I am accepting a parameter on the front end rest api. Now I need to pass
>>> this parameter to the implementing api. How do I do that.
>>>
>>> The following is the implementing api
>>>
>>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/{company}
>>>
>>> But adding {company} causes the test to fail with invalid message, and
>>> if I remove {company}, I get a 404 Error from the implementing server.
>>>
>>> The test succeeds if I put the following url
>>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/Test
>>> where "Test" is the parameter
>>>
>>> I am attaching screen shots to show what I mean.
>>>
>>> Sagar
>>>
>>> On Thu, Aug 3, 2017 at 12:37 PM, Sagar Kapadia 
>>> wrote:
>>>
 Hi Rasika!
 Thanks for your reply. I checked via ipconfig and its my IP. sorry for
 the confusion. I have two ips. Now the next question is how to pass
 parameters to the implementation endpoint. Or at least, if I can log the
 request being made to the end point it would be very helpful, since I am
 not getting any response from the server, but if I call the end point from
 the browser, I get a valid response
 Sagar

 On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera 
 wrote:

> Hi Sagar,
>
> Are you using VMware or virtualbox? Please check your network
> interfaces. Sometimes WSO2 Server could have binded into a wrong network
> interface when there are multiple network interfaces in the host machine.
>
> You can check this with ifconfig(in linux) or ipconfig(in windows).
>
> Best Regards,
> Rasika
>
> On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia 
> wrote:
>
>> Abimaran,
>> Actually, API manager is running on 192.168.11.68 and not 192.168.144.2.
>> I am making a call to API manager via the swagger definition in the api
>> store. However, the end point doesnt get hit because it is pointing to 
>> the
>> wrong url [192.168.144.2.] instead of 192.168.11.65
>> Sagar
>>
>> On Wed, Aug 2, 2017 at 6:15 PM, Abimaran Kugathasan <
>> abima...@wso2.com> wrote:
>>
>>> Hi Sagar,
>>>
>>> API Manager runs on 192.168.144.2 and this IP is shown in Store UI.
>>> If you want to hit the backend directly from your client, then there 
>>> isn't
>>> any reason for using API Manager. I don't understand why you are 
>>> expecting
>>> to hit backend URL directly. API Manager function as a proxy to route 
>>> the
>>> request to the backend which runs on 192.168.11.65.
>>>
>>> There can be many reasons not receiving a response, this might help
>>> you on this [1]. Also, You can try using cURL.
>>>
>>> [1]: http://blog.lakmali.com/2014/11/troubleshooting-issues-
>>> with-swagger-in.html
>>>
>>> On Wed, Aug 2, 2017 at 5:15 PM, Sagar Kapadia 
>>> wrote:
>>>
 Hi Thuistha,
 Thanks for your quick response. I had followed the tutorial below.
 My problem is my pc has ip 192.168.11.68 and not 192.168.144.2.
 when I try to call the api from the api store page via it's swagger
 definition ,there is a call to my server but, i get no response from 
 the
 server. I believe the reason is that the implementation url of the api
 points to an invalid ip (192.168.144.2), instead of the ip i
 specified in production and sandbox url.
 This is my confusion.
 Sagar

 On Aug 2, 2017 4:24 PM, "Thusitha Thilina Dayaratne" <
 thusit

Re: [Dev] Passing Parameters to the Implementation [Production and Sandbox] urls

[Sagar Kapadia]

Thanks Rasika,
Thanks, I got it working.

On Thu, Aug 3, 2017 at 1:18 PM, Rasika Perera  wrote:

> Hi Sagara,
>
> I think you are confused with API endpoint and the resource paths. Please
> refer [1] as an example. Path parameters are not allowed for the
> "Production EndPoint".
>
> *Your resource path should be:*
> /{Company}
>
> *Your endpoint should be : *
> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/
> 
>
> You can also try "/customers/{Company}" as resource path and "
> http://192.168.11.65:8000/BizBrainTally/api/ledgers/"; as the endpoint
> too. This depends on the granularity and resource paths of the API that
> you are hoping to expose through WSO2 API Manager.
>
> [1] https://docs.wso2.com/display/AM210/Create+and+Publish+an+API
>
> On Thu, Aug 3, 2017 at 1:05 PM, Sagar Kapadia  wrote:
>
>> Hi Rasika and Abimaran,
>>
>> I am accepting a parameter on the front end rest api. Now I need to pass
>> this parameter to the implementing api. How do I do that.
>>
>> The following is the implementing api
>>
>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/{company}
>>
>> But adding {company} causes the test to fail with invalid message, and if
>> I remove {company}, I get a 404 Error from the implementing server.
>>
>> The test succeeds if I put the following url
>> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/Test
>> where "Test" is the parameter
>>
>> I am attaching screen shots to show what I mean.
>>
>> Sagar
>>
>> On Thu, Aug 3, 2017 at 12:37 PM, Sagar Kapadia 
>> wrote:
>>
>>> Hi Rasika!
>>> Thanks for your reply. I checked via ipconfig and its my IP. sorry for
>>> the confusion. I have two ips. Now the next question is how to pass
>>> parameters to the implementation endpoint. Or at least, if I can log the
>>> request being made to the end point it would be very helpful, since I am
>>> not getting any response from the server, but if I call the end point from
>>> the browser, I get a valid response
>>> Sagar
>>>
>>> On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera  wrote:
>>>
 Hi Sagar,

 Are you using VMware or virtualbox? Please check your network
 interfaces. Sometimes WSO2 Server could have binded into a wrong network
 interface when there are multiple network interfaces in the host machine.

 You can check this with ifconfig(in linux) or ipconfig(in windows).

 Best Regards,
 Rasika

 On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia 
 wrote:

> Abimaran,
> Actually, API manager is running on 192.168.11.68 and not 192.168.144.2.
> I am making a call to API manager via the swagger definition in the api
> store. However, the end point doesnt get hit because it is pointing to the
> wrong url [192.168.144.2.] instead of 192.168.11.65
> Sagar
>
> On Wed, Aug 2, 2017 at 6:15 PM, Abimaran Kugathasan  > wrote:
>
>> Hi Sagar,
>>
>> API Manager runs on 192.168.144.2 and this IP is shown in Store UI.
>> If you want to hit the backend directly from your client, then there 
>> isn't
>> any reason for using API Manager. I don't understand why you are 
>> expecting
>> to hit backend URL directly. API Manager function as a proxy to route the
>> request to the backend which runs on 192.168.11.65.
>>
>> There can be many reasons not receiving a response, this might help
>> you on this [1]. Also, You can try using cURL.
>>
>> [1]: http://blog.lakmali.com/2014/11/troubleshooting-issues-
>> with-swagger-in.html
>>
>> On Wed, Aug 2, 2017 at 5:15 PM, Sagar Kapadia 
>> wrote:
>>
>>> Hi Thuistha,
>>> Thanks for your quick response. I had followed the tutorial below.
>>> My problem is my pc has ip 192.168.11.68 and not 192.168.144.2.
>>> when I try to call the api from the api store page via it's swagger
>>> definition ,there is a call to my server but, i get no response from the
>>> server. I believe the reason is that the implementation url of the api
>>> points to an invalid ip (192.168.144.2), instead of the ip i
>>> specified in production and sandbox url.
>>> This is my confusion.
>>> Sagar
>>>
>>> On Aug 2, 2017 4:24 PM, "Thusitha Thilina Dayaratne" <
>>> thusit...@wso2.com> wrote:
>>>
 Hi Sagar,

 192.168.144.2 is the IP address of your APIM running instance and
 8280 is the port which exposes your API through the API manager. When 
 you
 invoke the http://192.168.144.2:8280/// it
 will be sent to the production endpoint that you configured through 
 the UI.

 You can refer to APIM Docs[1] for more details

 [1] - https://docs.wso2.com/display/AM210/Create+and+Publish+an+API

 Thanks



 On Wed, Aug 2, 2017 at 4:19 PM, Sagar Ka

Re: [Dev] Why does WSO2 API Manager change the endpoint ip and port addresses to 192.168.144.2:8280

[Sagar Kapadia]

The API manager is on my local machine. I am calling the api manager [on
the local host] via the swagger definition in the api store. The
implementation [production] url is on a remote machine
http:/*/192.168.11.65 :*
8000/BizBrainTally/api/ledgers/customers/{company}
I can call the above url from the browser, and it gives the correct
response as can be seen from the screen shot



On Thu, Aug 3, 2017 at 1:05 PM, Rasika Perera  wrote:

> ​Hi Sagara,
>
> Please find inline comments;
>
> Thanks for your reply. I checked via ipconfig and its my IP. sorry for the
>> confusion. I have two ips.
>
> ​You are most welcome! It is a valid requirement to have two network
> interfaces but you might need to configure with [1]. Can you share with us
> the output of the ipconfig command.
>
> Or at least, if I can log the request being made to the end point it would
>> be very helpful, since I am not getting any response from the server, but
>> if I call the end point from the browser, I get a valid response
>
> ​Didn't get what you get by calling from the browser.​
>
> Are you trying this API Manager in a remote host or in a local machine?
> ​
>
> [1] https://docs.wso2.com/display/AM210/Customize+the+
> API+Store+and+Gateway+URLs
>
>
> On Thu, Aug 3, 2017 at 12:37 PM, Sagar Kapadia  wrote:
>
>> Hi Rasika!
>> Thanks for your reply. I checked via ipconfig and its my IP. sorry for
>> the confusion. I have two ips. Now the next question is how to pass
>> parameters to the implementation endpoint. Or at least, if I can log the
>> request being made to the end point it would be very helpful, since I am
>> not getting any response from the server, but if I call the end point from
>> the browser, I get a valid response
>> Sagar
>>
>> On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera  wrote:
>>
>>> Hi Sagar,
>>>
>>> Are you using VMware or virtualbox? Please check your network
>>> interfaces. Sometimes WSO2 Server could have binded into a wrong network
>>> interface when there are multiple network interfaces in the host machine.
>>>
>>> You can check this with ifconfig(in linux) or ipconfig(in windows).
>>>
>>> Best Regards,
>>> Rasika
>>>
>>> On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia 
>>> wrote:
>>>
 Abimaran,
 Actually, API manager is running on 192.168.11.68 and not 192.168.144.2.
 I am making a call to API manager via the swagger definition in the api
 store. However, the end point doesnt get hit because it is pointing to the
 wrong url [192.168.144.2.] instead of 192.168.11.65
 Sagar

 On Wed, Aug 2, 2017 at 6:15 PM, Abimaran Kugathasan 
 wrote:

> Hi Sagar,
>
> API Manager runs on 192.168.144.2 and this IP is shown in Store UI. If
> you want to hit the backend directly from your client, then there isn't 
> any
> reason for using API Manager. I don't understand why you are expecting to
> hit backend URL directly. API Manager function as a proxy to route the
> request to the backend which runs on 192.168.11.65.
>
> There can be many reasons not receiving a response, this might help
> you on this [1]. Also, You can try using cURL.
>
> [1]: http://blog.lakmali.com/2014/11/troubleshooting-issues-
> with-swagger-in.html
>
> On Wed, Aug 2, 2017 at 5:15 PM, Sagar Kapadia 
> wrote:
>
>> Hi Thuistha,
>> Thanks for your quick response. I had followed the tutorial below. My
>> problem is my pc has ip 192.168.11.68 and not 192.168.144.2.
>> when I try to call the api from the api store page via it's swagger
>> definition ,there is a call to my server but, i get no response from the
>> server. I believe the reason is that the implementation url of the api
>> points to an invalid ip (192.168.144.2), instead of the ip i
>> specified in production and sandbox url.
>> This is my confusion.
>> Sagar
>>
>> On Aug 2, 2017 4:24 PM, "Thusitha Thilina Dayaratne" <
>> thusit...@wso2.com> wrote:
>>
>>> Hi Sagar,
>>>
>>> 192.168.144.2 is the IP address of your APIM running instance and
>>> 8280 is the port which exposes your API through the API manager. When 
>>> you
>>> invoke the http://192.168.144.2:8280/// it
>>> will be sent to the production endpoint that you configured through the 
>>> UI.
>>>
>>> You can refer to APIM Docs[1] for more details
>>>
>>> [1] - https://docs.wso2.com/display/AM210/Create+and+Publish+an+API
>>>
>>> Thanks
>>>
>>>
>>>
>>> On Wed, Aug 2, 2017 at 4:19 PM, Sagar Kapadia 
>>> wrote:
>>>


 On Wed, Aug 2, 2017 at 4:18 PM, Sagar Kapadia 
 wrote:

> Hi,
> I tried to create an API in the API manager. Everything is ok,
> except for the fact that the end point ip anddress and port in the
> implementation page are ignored. I get the following ip address and 
> port
> 192.168.

Re: [Dev] Passing Parameters to the Implementation [Production and Sandbox] urls

[Rasika Perera]

Hi Sagara,

I think you are confused with API endpoint and the resource paths. Please
refer [1] as an example. Path parameters are not allowed for the
"Production EndPoint".

*Your resource path should be:*
/{Company}

*Your endpoint should be : *
http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/


You can also try "/customers/{Company}" as resource path and "
http://192.168.11.65:8000/BizBrainTally/api/ledgers/"; as the endpoint too. This
depends on the granularity and resource paths of the API that you are
hoping to expose through WSO2 API Manager.

[1] https://docs.wso2.com/display/AM210/Create+and+Publish+an+API

On Thu, Aug 3, 2017 at 1:05 PM, Sagar Kapadia  wrote:

> Hi Rasika and Abimaran,
>
> I am accepting a parameter on the front end rest api. Now I need to pass
> this parameter to the implementing api. How do I do that.
>
> The following is the implementing api
>
> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/{company}
>
> But adding {company} causes the test to fail with invalid message, and if
> I remove {company}, I get a 404 Error from the implementing server.
>
> The test succeeds if I put the following url
> http://192.168.11.65:8000/BizBrainTally/api/ledgers/customers/Test
> where "Test" is the parameter
>
> I am attaching screen shots to show what I mean.
>
> Sagar
>
> On Thu, Aug 3, 2017 at 12:37 PM, Sagar Kapadia  wrote:
>
>> Hi Rasika!
>> Thanks for your reply. I checked via ipconfig and its my IP. sorry for
>> the confusion. I have two ips. Now the next question is how to pass
>> parameters to the implementation endpoint. Or at least, if I can log the
>> request being made to the end point it would be very helpful, since I am
>> not getting any response from the server, but if I call the end point from
>> the browser, I get a valid response
>> Sagar
>>
>> On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera  wrote:
>>
>>> Hi Sagar,
>>>
>>> Are you using VMware or virtualbox? Please check your network
>>> interfaces. Sometimes WSO2 Server could have binded into a wrong network
>>> interface when there are multiple network interfaces in the host machine.
>>>
>>> You can check this with ifconfig(in linux) or ipconfig(in windows).
>>>
>>> Best Regards,
>>> Rasika
>>>
>>> On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia 
>>> wrote:
>>>
 Abimaran,
 Actually, API manager is running on 192.168.11.68 and not 192.168.144.2.
 I am making a call to API manager via the swagger definition in the api
 store. However, the end point doesnt get hit because it is pointing to the
 wrong url [192.168.144.2.] instead of 192.168.11.65
 Sagar

 On Wed, Aug 2, 2017 at 6:15 PM, Abimaran Kugathasan 
 wrote:

> Hi Sagar,
>
> API Manager runs on 192.168.144.2 and this IP is shown in Store UI. If
> you want to hit the backend directly from your client, then there isn't 
> any
> reason for using API Manager. I don't understand why you are expecting to
> hit backend URL directly. API Manager function as a proxy to route the
> request to the backend which runs on 192.168.11.65.
>
> There can be many reasons not receiving a response, this might help
> you on this [1]. Also, You can try using cURL.
>
> [1]: http://blog.lakmali.com/2014/11/troubleshooting-issues-
> with-swagger-in.html
>
> On Wed, Aug 2, 2017 at 5:15 PM, Sagar Kapadia 
> wrote:
>
>> Hi Thuistha,
>> Thanks for your quick response. I had followed the tutorial below. My
>> problem is my pc has ip 192.168.11.68 and not 192.168.144.2.
>> when I try to call the api from the api store page via it's swagger
>> definition ,there is a call to my server but, i get no response from the
>> server. I believe the reason is that the implementation url of the api
>> points to an invalid ip (192.168.144.2), instead of the ip i
>> specified in production and sandbox url.
>> This is my confusion.
>> Sagar
>>
>> On Aug 2, 2017 4:24 PM, "Thusitha Thilina Dayaratne" <
>> thusit...@wso2.com> wrote:
>>
>>> Hi Sagar,
>>>
>>> 192.168.144.2 is the IP address of your APIM running instance and
>>> 8280 is the port which exposes your API through the API manager. When 
>>> you
>>> invoke the http://192.168.144.2:8280/// it
>>> will be sent to the production endpoint that you configured through the 
>>> UI.
>>>
>>> You can refer to APIM Docs[1] for more details
>>>
>>> [1] - https://docs.wso2.com/display/AM210/Create+and+Publish+an+API
>>>
>>> Thanks
>>>
>>>
>>>
>>> On Wed, Aug 2, 2017 at 4:19 PM, Sagar Kapadia 
>>> wrote:
>>>


 On Wed, Aug 2, 2017 at 4:18 PM, Sagar Kapadia 
 wrote:

> Hi,
> I tried to create an API in the API manager. Everything is ok,
> except for the fact that t

Re: [Dev] Why does WSO2 API Manager change the endpoint ip and port addresses to 192.168.144.2:8280

[Rasika Perera]

​Hi Sagara,

Please find inline comments;

Thanks for your reply. I checked via ipconfig and its my IP. sorry for the
> confusion. I have two ips.

​You are most welcome! It is a valid requirement to have two network
interfaces but you might need to configure with [1]. Can you share with us
the output of the ipconfig command.

Or at least, if I can log the request being made to the end point it would
> be very helpful, since I am not getting any response from the server, but
> if I call the end point from the browser, I get a valid response

​Didn't get what you get by calling from the browser.​

Are you trying this API Manager in a remote host or in a local machine?
​

[1]
https://docs.wso2.com/display/AM210/Customize+the+API+Store+and+Gateway+URLs


On Thu, Aug 3, 2017 at 12:37 PM, Sagar Kapadia  wrote:

> Hi Rasika!
> Thanks for your reply. I checked via ipconfig and its my IP. sorry for the
> confusion. I have two ips. Now the next question is how to pass parameters
> to the implementation endpoint. Or at least, if I can log the request being
> made to the end point it would be very helpful, since I am not getting any
> response from the server, but if I call the end point from the browser, I
> get a valid response
> Sagar
>
> On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera  wrote:
>
>> Hi Sagar,
>>
>> Are you using VMware or virtualbox? Please check your network interfaces.
>> Sometimes WSO2 Server could have binded into a wrong network interface when
>> there are multiple network interfaces in the host machine.
>>
>> You can check this with ifconfig(in linux) or ipconfig(in windows).
>>
>> Best Regards,
>> Rasika
>>
>> On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia  wrote:
>>
>>> Abimaran,
>>> Actually, API manager is running on 192.168.11.68 and not 192.168.144.2.
>>> I am making a call to API manager via the swagger definition in the api
>>> store. However, the end point doesnt get hit because it is pointing to the
>>> wrong url [192.168.144.2.] instead of 192.168.11.65
>>> Sagar
>>>
>>> On Wed, Aug 2, 2017 at 6:15 PM, Abimaran Kugathasan 
>>> wrote:
>>>
 Hi Sagar,

 API Manager runs on 192.168.144.2 and this IP is shown in Store UI. If
 you want to hit the backend directly from your client, then there isn't any
 reason for using API Manager. I don't understand why you are expecting to
 hit backend URL directly. API Manager function as a proxy to route the
 request to the backend which runs on 192.168.11.65.

 There can be many reasons not receiving a response, this might help you
 on this [1]. Also, You can try using cURL.

 [1]: http://blog.lakmali.com/2014/11/troubleshooting-issues-
 with-swagger-in.html

 On Wed, Aug 2, 2017 at 5:15 PM, Sagar Kapadia 
 wrote:

> Hi Thuistha,
> Thanks for your quick response. I had followed the tutorial below. My
> problem is my pc has ip 192.168.11.68 and not 192.168.144.2.
> when I try to call the api from the api store page via it's swagger
> definition ,there is a call to my server but, i get no response from the
> server. I believe the reason is that the implementation url of the api
> points to an invalid ip (192.168.144.2), instead of the ip i
> specified in production and sandbox url.
> This is my confusion.
> Sagar
>
> On Aug 2, 2017 4:24 PM, "Thusitha Thilina Dayaratne" <
> thusit...@wso2.com> wrote:
>
>> Hi Sagar,
>>
>> 192.168.144.2 is the IP address of your APIM running instance and
>> 8280 is the port which exposes your API through the API manager. When you
>> invoke the http://192.168.144.2:8280/// it
>> will be sent to the production endpoint that you configured through the 
>> UI.
>>
>> You can refer to APIM Docs[1] for more details
>>
>> [1] - https://docs.wso2.com/display/AM210/Create+and+Publish+an+API
>>
>> Thanks
>>
>>
>>
>> On Wed, Aug 2, 2017 at 4:19 PM, Sagar Kapadia 
>> wrote:
>>
>>>
>>>
>>> On Wed, Aug 2, 2017 at 4:18 PM, Sagar Kapadia 
>>> wrote:
>>>
 Hi,
 I tried to create an API in the API manager. Everything is ok,
 except for the fact that the end point ip anddress and port in the
 implementation page are ignored. I get the following ip address and 
 port
 192.168.144.2:8280

 The screen shots show the issue
 Sagar

>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Thusitha Dayaratne
>> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>>
>> Mobile  +94712756809 <+94%2071%20275%206809>
>> Blog  alokayasoya.blogspot.com
>> Abouthttp://about.me/thusithathilina
>> 
>>
>>
> _

Re: [Dev] How to create a websocket implementation of an end point

[Sagar Kapadia]

Hi Abimaran,
I got that , thanks. My specific need is a front end REST API with a back
end [implementation endpoint] being a web socket.
i see options for REST and SOAP and Dynamic Endpoints, but none for a
websocket endpoint. Is this possible?
If I want to set the production or sandbox url to ws://localhost:1880/api,
I cant figure out a way to do this. I entered the url for the websocket in
the text field, but then in the store, the api console tab is missing.
Sagar


On Wed, Aug 2, 2017 at 6:27 PM, Abimaran Kugathasan 
wrote:

> Hi Sagar,
>
> WebSocket APIs are introduced in 2.1, it's in 'Design' tab as below.
>
>
>
> ​
>
> On Wed, Aug 2, 2017 at 4:20 PM, Sagar Kapadia  wrote:
>
>> Hi,
>> I cant see a way to create a web socket endpoint implementation .Please
>> let me know how to do this
>> Sagar
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thanks
> Abimaran Kugathasan
> Senior Software Engineer - API Technologies
>
> Email : abima...@wso2.com
> Mobile : +94 773922820
>
> 
> 
>   
> 
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Why does WSO2 API Manager change the endpoint ip and port addresses to 192.168.144.2:8280

[Sagar Kapadia]

Hi Rasika!
Thanks for your reply. I checked via ipconfig and its my IP. sorry for the
confusion. I have two ips. Now the next question is how to pass parameters
to the implementation endpoint. Or at least, if I can log the request being
made to the end point it would be very helpful, since I am not getting any
response from the server, but if I call the end point from the browser, I
get a valid response
Sagar

On Thu, Aug 3, 2017 at 11:59 AM, Rasika Perera  wrote:

> Hi Sagar,
>
> Are you using VMware or virtualbox? Please check your network interfaces.
> Sometimes WSO2 Server could have binded into a wrong network interface when
> there are multiple network interfaces in the host machine.
>
> You can check this with ifconfig(in linux) or ipconfig(in windows).
>
> Best Regards,
> Rasika
>
> On Wed, Aug 2, 2017 at 8:28 PM, Sagar Kapadia  wrote:
>
>> Abimaran,
>> Actually, API manager is running on 192.168.11.68 and not 192.168.144.2.
>> I am making a call to API manager via the swagger definition in the api
>> store. However, the end point doesnt get hit because it is pointing to the
>> wrong url [192.168.144.2.] instead of 192.168.11.65
>> Sagar
>>
>> On Wed, Aug 2, 2017 at 6:15 PM, Abimaran Kugathasan 
>> wrote:
>>
>>> Hi Sagar,
>>>
>>> API Manager runs on 192.168.144.2 and this IP is shown in Store UI. If
>>> you want to hit the backend directly from your client, then there isn't any
>>> reason for using API Manager. I don't understand why you are expecting to
>>> hit backend URL directly. API Manager function as a proxy to route the
>>> request to the backend which runs on 192.168.11.65.
>>>
>>> There can be many reasons not receiving a response, this might help you
>>> on this [1]. Also, You can try using cURL.
>>>
>>> [1]: http://blog.lakmali.com/2014/11/troubleshooting-issues-
>>> with-swagger-in.html
>>>
>>> On Wed, Aug 2, 2017 at 5:15 PM, Sagar Kapadia 
>>> wrote:
>>>
 Hi Thuistha,
 Thanks for your quick response. I had followed the tutorial below. My
 problem is my pc has ip 192.168.11.68 and not 192.168.144.2.
 when I try to call the api from the api store page via it's swagger
 definition ,there is a call to my server but, i get no response from the
 server. I believe the reason is that the implementation url of the api
 points to an invalid ip (192.168.144.2), instead of the ip i specified
 in production and sandbox url.
 This is my confusion.
 Sagar

 On Aug 2, 2017 4:24 PM, "Thusitha Thilina Dayaratne" <
 thusit...@wso2.com> wrote:

> Hi Sagar,
>
> 192.168.144.2 is the IP address of your APIM running instance and 8280
> is the port which exposes your API through the API manager. When you 
> invoke
> the http://192.168.144.2:8280/// it will be
> sent to the production endpoint that you configured through the UI.
>
> You can refer to APIM Docs[1] for more details
>
> [1] - https://docs.wso2.com/display/AM210/Create+and+Publish+an+API
>
> Thanks
>
>
>
> On Wed, Aug 2, 2017 at 4:19 PM, Sagar Kapadia 
> wrote:
>
>>
>>
>> On Wed, Aug 2, 2017 at 4:18 PM, Sagar Kapadia 
>> wrote:
>>
>>> Hi,
>>> I tried to create an API in the API manager. Everything is ok,
>>> except for the fact that the end point ip anddress and port in the
>>> implementation page are ignored. I get the following ip address and port
>>> 192.168.144.2:8280
>>>
>>> The screen shots show the issue
>>> Sagar
>>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Thusitha Dayaratne
> WSO2 Inc. - lean . enterprise . middleware |  wso2.com
>
> Mobile  +94712756809 <+94%2071%20275%206809>
> Blog  alokayasoya.blogspot.com
> Abouthttp://about.me/thusithathilina
> 
>
>
 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> Thanks
>>> Abimaran Kugathasan
>>> Senior Software Engineer - API Technologies
>>>
>>> Email : abima...@wso2.com
>>> Mobile : +94 773922820 <+94%2077%20392%202820>
>>>
>>> 
>>> 
>>>   
>>> 
>>>
>>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> With Regards,
>
> *Rasika Perera*
> Senior Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> 
>
> WSO2 Inc. www.wso2.com
> lean.enterprise.middleware
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/c