Re: [Dev] Issue in accessing same boss and worker group in HTTP carbon transport from MSF4J and Siddhi together

Hi Shafreen, Thank you for the information. Regards, Yasara. On Thu, Aug 3, 2017 at 11:02 AM, Shafreen Anfar wrote: > Hi Yasara, > > As part of the restructuring [1] we will be providing a way to create > server connectors with separate event loop groups. > > [1]

Re: [Dev] Issue in accessing same boss and worker group in HTTP carbon transport from MSF4J and Siddhi together

Hi Yasara, As part of the restructuring [1] we will be providing a way to create server connectors with separate event loop groups. [1] "Restructuring CarbonMessageProcessor, CarbonMessage and CarbonCallBack" On Tue, Aug 1, 2017 at 1:34 AM, Yasara Dissanayake wrote: > Hi

Re: [Dev] DSS Improvement

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

Re: [Dev] [IOTS] Use maven build source in windows 7, the command line over the windows Maximum Length of Command Line String

You can try moving your folders closer to D drive. That will remove the lengthy repetitive string appearing for every jar file. On Aug 3, 2017 8:01 AM, "姜仁杰" wrote: > hi all: > > > > > ​ > > > When use maven build source in windows 7, the command line over the > windows

[Dev] [IOTS] Use maven build source in windows 7, the command line over the windows Maximum Length of Command Line String

hi all: ​ When use maven build source in windows 7, the command line over the windows Maximum Length of Command Line String Does anyone has an idea on how to fix this? Thanks jiangrenjie ___ Dev mailing list Dev@wso2.org

[Dev] [API-MGR] Error! You have partially created keys.

Hi, I am facing a weird issue. I have an app on Api Manager and I am able to generate the keys for that app. But if I leave the APP page, and go back to it to see the keys, I got this error message: Error! You have partially created keys. Please click the Clean Up button and try again. And if

Re: [Dev] EI-610 - Broker Issue

I don't know exactly why, but after restarting the server it starts working correctly. Thanks, 2017-08-01 15:46 GMT-03:00 Júnior : > Hi, > > I have a broker clustered, and after a restart, one of the nodes keep > throwing the following error: > > > TID: [-1] [] [2017-08-01

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

Abimaran, Can we have separate named endpoint to the socket? i.e. say api.myProduct.com for REST endpoint and ws.myProduct.com for Socket? Both of them are served by a same host / WSO2 API server. Regards, Ashvin Savani | *CEO* *Avinashi Group of Companies* | *Excellence Everywhere!*

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

Thanks a lot abimaran 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

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

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,

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

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

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

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

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

Hi Abimaran, Thanks for your reply. Does that mean that i can ignore the displayed url. But when i call the api through swagger definition in api store page, call goes through correctly, but actual end point is not hit. What could the reason be? Sagar On Aug 2, 2017 5:01 PM, "Abimaran Kugathasan"

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

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

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

Hi Sagar, Production URL shown in publisher UI is your real backend production URL and Production and Sandbox URL shown in Store is Gateway's (or API Manager) URL for that API, not the real backend URL. And you are supposed to use that to invoke the API. On Wed, Aug 2, 2017 at 4:24 PM, Thusitha

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

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

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

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

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

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 >

Re: [Dev] Please review and merge the pull request

Hi Isuri, PR merged. Thanks On Wed, Aug 2, 2017 at 3:56 PM, Isuri Anuradha wrote: > changed the commit message. > > [1] -https://github.com/wso2/carbon-kernel/pull/1460 > > Regards, > Isuri Anuradha. > > On Wed, Aug 2, 2017 at 3:33 PM, Isuri Anuradha wrote: >

Re: [Dev] Please review and merge the pull request

changed the commit message. [1] -https://github.com/wso2/carbon-kernel/pull/1460 Regards, Isuri Anuradha. On Wed, Aug 2, 2017 at 3:33 PM, Isuri Anuradha wrote: > Pull request URL. > > [1] - https://github.com/wso2/carbon-kernel/pull/1460 > > Thanks. > > On Wed, Aug 2, 2017 at

Re: [Dev] Please review and merge the pull request

Pull request URL. [1] - https://github.com/wso2/carbon-kernel/pull/1460 Thanks. On Wed, Aug 2, 2017 at 3:10 PM, Isuri Anuradha wrote: > Hi! > > Please merge the pull request [1] which contains the fix for [2]. > > [1]- https://github.com/wso2/carbon-kernel/pull/1460 > [2]-

Re: [Dev] Error while building the product-is

Hi all, As suggested by Darshana, this issue happens when the certificates are not trusted by the Oracle VM as mentioned in [1]. This can happen if the tycho certificate has been removed from the Oracle VM. [1] - Mail subject: "[Dev] Cannot generate P2 metadata: P2 publisher return code was 13"

Re: [Dev] Supporting attributes feature for SCIM filtering

On Wed, Aug 2, 2017 at 2:30 PM, Pulasthi Mahawithana wrote: > Hi Johann, > > Both the "attributes" and "filter" can be used together in IS 5.3.0. > Please see the last example at [1]. > Oh great! Now I am trying to remember where I got this problem originally from :). Will

Re: [Dev] Supporting attributes feature for SCIM filtering

Hi Johann, Both the "attributes" and "filter" can be used together in IS 5.3.0. Please see the last example at [1]. [1] https://medium.com/@pulasthi7/scim-list-users-with-given-attributes-in-wso2-identity-server-5-3-0-8360522d3ea9 On Wed, Aug 2, 2017 at 2:10 PM, Johann Nallathamby

Re: [Dev] Supporting attributes feature for SCIM filtering

Pulasthi has already added this feature [1] [1] https://medium.com/@pulasthi7/scim-list-users-with-given-attributes-in-wso2-identity-server-5-3-0-8360522d3ea9 On Wed, Aug 2, 2017 at 2:10 PM, Johann Nallathamby wrote: > Hi Chamila, > > On Wed, Aug 2, 2017 at 2:06 PM, Chamila

Re: [Dev] Supporting attributes feature for SCIM filtering

Hi Chamila, On Wed, Aug 2, 2017 at 2:06 PM, Chamila Wijayarathna < cdwijayarat...@gmail.com> wrote: > Hi Johann, > > Sorry for the confusion, I didn't knew about SCIM attributes > implementation previously. Is this only available for SCIM 2.0 or is this > available in SCIM 1.x implementation as

Re: [Dev] Supporting attributes feature for SCIM filtering

Hi Johann, Sorry for the confusion, I didn't knew about SCIM attributes implementation previously. Is this only available for SCIM 2.0 or is this available in SCIM 1.x implementation as well? If it is supported in SCIM list, it should be there in filter also. Because AFAIK, filter is parameter

Re: [Dev] Supporting attributes feature for SCIM filtering

On Tue, Jul 11, 2017 at 6:52 PM, Chamila Wijayarathna < cdwijayarat...@gmail.com> wrote: > Hi Johann, > > In IS 5.0 > filter=username eq name > gave the result that you are expecting here, but we changed it to return > only meta data since retrieving all attributes is costly. Spec also > mentions

Re: [Dev] [IS] Admin/Tenant Admin Users cannot be filtered to get the SCIM ID

Hi, We have the same issue for admin group. Created another JIRA to track the that issue. https://wso2.org/jira/browse/IDENTITY-6205 Thanks, On Fri, Jul 21, 2017 at 2:37 PM, Indunil Upeksha Rathnayake < indu...@wso2.com> wrote: > Hi, > > > > On Fri, Jul 21, 2017 at 2:29 PM, Gayan Gunawardana