Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager Tooling v3.2.0 RC2

Tested the following, - Exporting/import APIs, API Products, Apps. - Environment specific parameters - Dynamic data scenarios *[+] Stable - Go ahead and release* On Tue, 25 Aug 2020 at 15:45, Naduni Pamudika wrote: > Hi All, > > Tested the following with API Manager Tooling 3.2.0 RC2

Re: [Dev] [DEV] [VOTE] Release WSO2 API Manager Tooling v3.1.0 RC4

Tested the following: Various scenarios involving super tenant, tenant, secondary user store users 1. Generate Keys 2. Export Apps No blockers found [+] Stable - Go ahead and release On Fri, 3 Apr 2020 at 14:16, Naduni Pamudika wrote: > Hi All, > > WSO2 Api Manager team is pleased to

Re: [Dev] [DEV] [VOTE] Release WSO2 API Manager Tooling v3.1.0 RC3

Tested the following: Various scenarios involving super tenant, tenant, secondary user store users 1. Generate Keys 2. Export Apps No blockers found [+] Stable - Go ahead and release On Thu, 2 Apr 2020 at 19:30, Naduni Pamudika wrote: > Hi All, > > WSO2 Api Manager team is pleased to

Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 3.0.0 RC3

Tested Workflows for, - API State change - User Signup - Application Creation - Application Registration - API Subscription - API Product Subscription No blockers found. +1 for release On Fri, 25 Oct 2019 at 17:42, Dushani Wellappili wrote: > Tested the following, > > - Basic flow in API

Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 3.0.0 RC2

Tested Workflows for, - API State change - User Signup - Application Creation - Application Registration - API Subscription - API Product Subscription No blockers found. +1 On Thu, 24 Oct 2019 at 17:35, Ishara Cooray wrote: > Hi All, > > Tested the following. > - API Creation, Publishing,

Re: [Dev] Regarding the HTTP status code to be used if the response is invalid

I think 422 is the most appropriate given your use case of validating if a message matches a given schema. So you can receive a valid JSON or XML(it's not malformed hence it is not a bad request(400)), but it may not match with the message schema definition you are matching against. The specs

Re: [Dev] Test fails due to NoClassDefFoundError: Could not initialize class

Since this is a unit test you have no option but to use power mock in order to mock the PrivilegedCarbonContext.endTenantFlow() static function using PowerMockito.mockStatic. I think we must be doing this already, not sure why the test is suddenly failing. We have done this in APIProviderImplTest.

Re: [Dev] Issue in getting the fileName when getting the API Documents content via REST API

Won't that make the table > grow faster and make querying slower? How about keeping a separate table > for this? Then we can have a foreign key as well. > > Thanks, > Bhathiya > > On Mon, Oct 22, 2018 at 2:57 PM Uvindra Dias Jayasinha > wrote: > >> +1, CONTENT is

Re: [Dev] Issue in getting the fileName when getting the API Documents content via REST API

DOC_CONTENT VARCHAR(1024) > > *AM_API_RESOURCES* > RESOURCE_NAME VARCHAR(255) > > And I think we can change it DOC_CONTENT to CONTENT . > WDYT? > > Thanks & Regards, > Mushthaq > > On Mon, Oct 22, 2018 at 2:35 PM Uvindra Dias Jayasinha > wrote: > >> HI Mushtaq,

Re: [Dev] Issue in getting the fileName when getting the API Documents content via REST API

TA_DATA > (*DOC_CONTENT column*) *and content of FILE of API documents will be > saved in *AM_API_RESOURCES *which will have a reference in > *AM_API_DOC_META_DATA > (*RESOURCE_ID column*)*. > > Thanks & Regards, > Mushthaq > > > On Fri, Oct 19, 2018 at 9:23 PM Hars

Re: [Dev] Issue in getting the fileName when getting the API Documents content via REST API

Here is my take on this. When I originally designed the schema I wasn't taking into consideration any of the practical implications associated with API resources being saved and retrieved at DB level. But now that we are at implementation stage some of these implications are much more clearer now.

Re: [Dev] [APIM 2.6.0 to 3.0.0 Migration] Error handling in CLI tool

I think the method currently used by the tool(log and handle at source of issue) is fine. We don't gain anything by throwing this up to another level and handling it there, it will just complicate the code. This style currently used by the CLI tool is adequate since it is not a server that needs

Re: [Dev] [APIM2xx] how to add an api level throttling policy for "Apply to API" using updateAPI from publisher rest api?

If someone tries to create a new API via REST API specifying a tier that does not exist we should simply reject the creation of that API. We need to validate that the specified tiers are valid in the API creation request On 1 February 2018 at 12:41, Irham Iqbal wrote: > I have

Re: [Dev] Did we thought about APIM 3.0.0 Audit log?

There is a JIRA[1] for this that I moved to github [1] https://wso2.org/jira/browse/APIMANAGER-5802 On 30 August 2017 at 11:07, Rukshan Premathunga wrote: > Hi all, > > In c4 we had separate log file to audit API and application related stuff. > Is this already done in AM 3?

Re: [Dev] [APIM][C5] Splitting "Generate Keys" operation in Store REST API

+1 On 20 June 2017 at 14:47, Bhathiya Jayasekara wrote: > Hi all, > > In the current implementation of store REST API, we have a single > operation (aka. Generate Keys) to create OAuth application and generate > access tokens, which requires 2 calls to key manager. IMO, if we

Re: [Dev] [C5] How to configure Data source configuration

C5 uses HikariCP[1] in the carbon-datasources[2] implementation which is dependent on a separate *-datasources.xml file to read configurations. The problem Ishara has highlighted is the need for having separate databases per a tenant. Due to this we cannot hard code the database name in the

Re: [Dev] [DEV][APIM][C5] - Caching requirement for OAuth2 protected microservices

Its great if we can have some feedback about this, active C5 development needs this moving forward. @Azeez and @Kishanthan, do we have any preferences? On 24 February 2017 at 13:12, Sagara Gunathunga <sag...@wso2.com> wrote: > > > > > > On Fri, Feb 24, 2017 at 7:28 AM

Re: [Dev] [DEV][APIM][C5] - Caching requirement for OAuth2 protected microservices

This will function like any of the local container classes we use(example: HashMap). I think its fine to use one of the available implementations(such as Guava since we already have it as a dependency) for this. Testing will reveal its suitability but I don't anticipate any issues since this is

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

ara <madha...@wso2.com> > wrote: > >> So what will happen if the user sends a space? So It's better to add a >> configuration to avoid these situations. then user can handle this. WDYT ? >> >> On Tue, Jan 10, 2017 at 10:54 AM, Uvindra Dias Jayasinha < >>

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

; So what will happen if the user sends a space? So It's better to add a > configuration to avoid these situations. then user can handle this. WDYT ? > > On Tue, Jan 10, 2017 at 10:54 AM, Uvindra Dias Jayasinha <uvin...@wso2.com > > wrote: > >> To be more precise, if a user

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

17 at 10:41, Uvindra Dias Jayasinha <uvin...@wso2.com> wrote: > Note that there is a clear break in the UX of the REST API if we allow > pass empty strings to Oracle(due to the conversion to NULL). Oracle treats > "" as NULL but this is incorrect in the REST/JSO

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

tring if there's a space. > > Thanks, > Akalanka. > > On Tue, Jan 10, 2017 at 10:23 AM, Lahiru Cooray <lahi...@wso2.com> wrote: > >> >> >> On Mon, Jan 9, 2017 at 7:54 AM, Isuru Haththotuwa <isu...@wso2.com> >> wrote: >> >>> >>&

Re: [Dev] [Oracle] How to handle insertion of empty string in oracle.

Setting a default value for empty fields being sent seems to be best. Furthermore we can have default values set in our DTO objects in case a given field is omitted altogether. So handling both the above scenarios can overcome the limitation in Oracle. But I dont know if this is good for the

Re: [Dev] [Architecture] [C5] MSF4J Interceptors need to be configurable.

Hi Ishara, Another possibility for supporting multiple auth types with what you have proposed is to have a collection Authenticator interfaces(using a Map possibly) at the RestAPISecurityInterceptor level. Depending on some condition you could selectively choose what implementation to use at

Re: [Dev] [dev][APIM 1.7] Alternatives for API creation/deletion audit logs

HI Thilini, If all you want to check is when an API is added or deleted then the same approach of using trigger for AM_API table is enough. But what information exactly do you need to collect for the audit? On 27 October 2016 at 14:23, Thilini Cooray wrote: > Hi, > > APIM

Re: [Dev] Do we support viewing user information (profiles) across tenants?

+1 to *Option 1*, I don't think we should try and get user profile details from across tenants. If you want to, you should login to the respective tenant explicitly to get that information. I think knowing the name of the tenant user is enough in this case. On 26 October 2016 at 13:40, Chamin

Re: [Dev] Why not ship creator and publisher roles pre-built in API-M?

Thats a good point Samisa. We have the subscriber role by default because we need it to set the permissions for users that sign up from the API store. All other user creations need to happen through the carbon admin console anyway so I guess we havent added those other roles by default. But I

Re: [Dev] Opening the JSON interface instead of SOAP to the clients(applications)

You can simply write a standard JAX-RS application that supports application/json and deploy this in WSO2 AS which can be exposed to external users to call. Here[1] is an example. [1] http://www.mkyong.com/webservices/jax-rs/json-example-with-jersey-jackson/ On 12 September 2016 at 11:50, 郑文兴

Re: [Dev] [VOTE][RC3] Release - WSO2 API Manager mediation policy tooling 2.0.0 RC3.

[+] Stable - go ahead and release On 30 August 2016 at 17:28, Roshan Wijesena wrote: > Hi All, > > This is the 3rd Release Candidate of WSO2 API Manager mediation policy > tooling 2.0.0. > > Please download, test the product and vote. The vote will be open for 72 > hours or as

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC5

Tested below with secure vault with custom key store 1. API creation and publication with different user roles and invocation tenant/super tenant 2. Stats tenant/super tenant(Store and Publisher) 3. Log Analyzer tenant/super tenant 4. API creation and publication with different user roles for

Re: [Dev] [Architecture] [VOTE] Release WSO2 API Manager 2.0.0 RC4

Tested below with secure vault with custom key store 1. API publication and invocation tenant and super tenant 2. Stats tenant and super tenant(Store and Publisher) 3. Log Analyzer tenant and super tenant No issues found [+] Stable - go ahead and release. On 22 July 2016 at 12:20, Roshan

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

Thanks Viraj On 5 July 2016 at 15:52, Viraj Senevirathne <vir...@wso2.com> wrote: > PR is merged https://github.com/wso2/carbon-mediation/pull/671. > > On Tue, Jul 5, 2016 at 3:44 PM, Uvindra Dias Jayasinha <uvin...@wso2.com> > wrote: > >> Ping! >> >

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

Ping! ESB Team can we get the above PR merged please? On 27 June 2016 at 19:26, Uvindra Dias Jayasinha <uvin...@wso2.com> wrote: > Thanks Kishanthan > > If we were to fix this by calling startTenantFlow() the fix would be a lot > more complicated and may lead to other issues

Re: [Dev] [API Store] Switching through Side Panes and them moving around while switching does not look cool

I found the moving side pain very distracting as well, what are we achieving by moving the side pain in that way? Normally with the fixed panel you grow accustomed to the position of things over time and you can click on these quickly without having to directly look at them. But now you need to

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

27, 2016 at 12:13 PM, Uvindra Dias Jayasinha <uvin...@wso2.com > > wrote: > >> Before I just apply the stated fix I would like some feedback from the >> Carbon team regarding what maybe causing this issue. >> >> So here is what we are seeing so

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

Ping! Need your feedback Carbon team. On 27 June 2016 at 12:13, Uvindra Dias Jayasinha <uvin...@wso2.com> wrote: > Before I just apply the stated fix I would like some feedback from the > Carbon team regarding what maybe causing this issue. > > So here is what we are se

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

this be the cause? On 24 June 2016 at 14:44, Uvindra Dias Jayasinha <uvin...@wso2.com> wrote: > Problem is the issue is intermittent so its difficult to verify but I will > test the fix out and send a PR > > On 24 June 2016 at 13:52, Chanaka Fernando <chana...@wso2.com> wrote: >

Re: [Dev] Fixing APIMANAGER-4202 at carbon-mediation level

On Fri, Jun 24, 2016 at 1:02 PM, Uvindra Dias Jayasinha <uvin...@wso2.com> > wrote: > >> Hi All, >> >> The original issue encountered in [1] was fixed via the resolution of [2]. >> >> But now this has been reopened and in this case the same issue has g

[Dev] Fixing APIMANAGER-4202 at carbon-mediation level

Hi All, The original issue encountered in [1] was fixed via the resolution of [2]. But now this has been reopened and in this case the same issue has got exposed, but on this occasion the call stack is different. This is happening when setting the tenant info at [3]. So we need to apply the same

Re: [Dev] [APIM] Issue while using Conditional Group

Hi Amila, I think it defeats the purpose if we need to evaluate conditions again on the GW side(GW starts to do part of the decision manager role), is it possible to fix this by asking CEP to provide the aggregate result of all the available conditions? On 11 June 2016 at 12:12, Amila De Silva

Re: [Dev] [GREG] Invalid value error for REG_CREATED_TIME column in REG_RESOURCE with mysql 5.7

ttps://docs.wso2.com/display/CLUSTER44x/Configuring+the+Identity+Server+5.1.0+as+a+Key+Manager+with+API+Manager+1.10.0 > > Sewmini Jayaweera > *Software Engineer - QA Team* > Mobile: +94 (0) 773 381 250 > sewm...@wso2.com > > On Fri, Jun 10, 2016 at 5:02 PM, Uvindra D

Re: [Dev] [GREG] Invalid value error for REG_CREATED_TIME column in REG_RESOURCE with mysql 5.7

ry OK, 0 rows affected (0.01 sec) > > Query OK, 0 rows affected (0.01 sec) > > Query OK, 0 rows affected (0.01 sec) > > Query OK, 0 rows affected (0.01 sec) > > Query OK, 0 rows affected (0.01 sec) > > Query OK, 0 rows affected (0.01 sec) > > Query OK, 0 rows affe

Re: [Dev] [GREG] Invalid value error for REG_CREATED_TIME column in REG_RESOURCE with mysql 5.7

s, > > Sewmini > > Sewmini Jayaweera > *Software Engineer - QA Team* > Mobile: +94 (0) 773 381 250 > sewm...@wso2.com > > On Thu, Jun 9, 2016 at 10:56 PM, Uvindra Dias Jayasinha <uvin...@wso2.com> > wrote: > >> Note that the above feature(auto initial

Re: [Dev] [GREG] Invalid value error for REG_CREATED_TIME column in REG_RESOURCE with mysql 5.7

at 22:50, Uvindra Dias Jayasinha <uvin...@wso2.com> wrote: > Lets just try DEFAULT CURRENT_TIMESTAMP for all TIMESTAMP fields. > > Avoid using ON UPDATE CURRENT_TIMESTAMP, our code already explicitly > updates time stamp fields where required so we do not want MySQL to do this >

Re: [Dev] [GREG] Invalid value error for REG_CREATED_TIME column in REG_RESOURCE with mysql 5.7

Lets just try DEFAULT CURRENT_TIMESTAMP for all TIMESTAMP fields. Avoid using ON UPDATE CURRENT_TIMESTAMP, our code already explicitly updates time stamp fields where required so we do not want MySQL to do this for us. On 9 June 2016 at 22:43, Sewmini Jayaweera wrote: >

Re: [Dev] [APIM] Changing Default Tier Limits and Names

I think we need to setup a meeting to discuss the impact on existing users, there could be lots of things we need to consider. On 26 May 2016 at 11:31, Sam Sivayogam wrote: > What if we ship the 2.0.0 with the new tier definitions(new tier names, > new limits) and during

Re: [Dev] APIM snapse file system migration

I think the only way is to complicate the migration instructions, If user has customized any sequences they need to copy them over manually to latest pack and we will use those.(Discalimer to user: You maybe missing out on the latest changes shipped with the default sequences in the latest pack)

Re: [Dev] APIM snapse file system migration

On 13 January 2016 at 07:26, Nuwan Dias <nuw...@wso2.com> wrote: > > > On Wed, Jan 13, 2016 at 5:51 PM, Uvindra Dias Jayasinha <uvin...@wso2.com> > wrote: > >> I think the only way is to complicate the migration instructions, >> >> If user has customi

Re: [Dev] APIM snapse file system migration

consumed. On 13 January 2016 at 07:47, Nuwan Dias <nuw...@wso2.com> wrote: > > > On Wed, Jan 13, 2016 at 6:07 PM, Uvindra Dias Jayasinha <uvin...@wso2.com> > wrote: > >> Ok if we allow these to be extended then we should not be adding our >> logic from the pr

Re: [Dev] APIM snapse file system migration

? On 13 January 2016 at 09:48, Uvindra Dias Jayasinha <uvin...@wso2.com> wrote: > Ya this is fine but it has a real impact on complicating the migration. > This issue has been there with migrating previous releases as well. We need > to put more thought into reducing migration complexity

Re: [Dev] APIM snapse file system migration

sitory/resources/apim-synapse-config and then migration client will >>> blindly replace old sequences with those. >>> >>> On 13 January 2016 at 17:56, Nuwan Dias <nuw...@wso2.com> wrote: >>> >>>> >>>> >>>> On Wed

Re: [Dev] Null pointer exception from api gateway component when logging as the tenant-admin

Hi Harsha, This seems to be happening because you dont have the default sequences that are shipped with the APIM pack. When you login to the tenant for the first time the sequence are copied over to that tenant space, but you dont have these in the MDM pack. The Error and Warning above the NPE

Re: [Dev] Null pointer exception from api gateway component when logging as the tenant-admin

deploys synapse artifacts upon > a TenantLoading) is only registered, if the Gateway type is Synapse. If we > set it to None, then that task should not get registered. > > > On Thursday, October 15, 2015, Uvindra Dias Jayasinha <uvin...@wso2.com> > wrote: > >> Hi Hars

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

. This will be handled at velocity template level. On 24 July 2015 at 15:04, Uvindra Dias Jayasinha uvin...@wso2.com wrote: I found the following on SO[1] which is the exact same problem we are discussing here. The solution for it provided here[2]. So is this the way we should go about it? We can

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

, 2015 at 2:41 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Im referring to the attribute in the* resource* tag, that how we are triggering the different functionalities On 24 July 2015 at 14:39, Isuru Udana isu...@wso2.com wrote: In both scenarios you can see, HTTP Endpoint contains

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

from writing an API in this manner. On 24 July 2015 at 14:23, Isuru Udana isu...@wso2.com wrote: On Fri, Jul 24, 2015 at 2:10 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: In our velocity template we are conditionally deciding when the url-mapping attribute or uri-template attribute

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

/ /endpoint On Fri, Jul 24, 2015 at 2:35 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Attached are two synpase files generated with API Manager for the above use cases. Ok end of the day we need to support both attributes, its critical to API Manager functionality. Do

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

implementation now. If we cannot revert back, For ESB, we can simply remove the REST_URL_POSTFIX from the config and for AM, we need a easy way to do that from UI. On Fri, Jul 24, 2015 at 1:31 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: We need to come up with $subject. The issue

[Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

We need to come up with $subject. The issue related to this has been highlighted in [1] The REST_URL_POSTFIX property appends the url-mapping of a given resource to the end of the api endpoint in synapse. This is applied by synapse for all APIs that are defined. For example, *API URL* -

Re: [Dev] How to handle REST_URL_POSTFIX property when Query Parameter values are defined

and the fix will be seamless from a user perspective. [1] http://stackoverflow.com/questions/19978652/wso2-esb-http-endpoint-uri-parameters [2] http://stackoverflow.com/questions/19774923/wso2-esb-4-7-0-api-url-mapping On 24 July 2015 at 14:49, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Ok

Re: [Dev] Error when generating/refreshing keys in APIM 1.9.0

According to the exception seems there is a duplicate entry value when trying to insert into AM_APPLICATION_REGISTRATION table. Seems that the same Application is getting registered multiple times. Can you let us know the exacts steps you are following? On 24 July 2015 at 16:13, Amalka Subasinghe

Re: [Dev] API Manager associating a new version of an API with its previous version

22, 2015 at 12:44 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The correct way I can think of solving this is to store the apiID of the version that is being copied from in the newly created api object so that we can make the association later on when we are publishing the new api

[Dev] API Manager associating a new version of an API with its previous version

This applies to API Manager 1.9.0, but this is true for previous versions as well. When trying to fix the following ticket[1] I came across this scenario, 1. API named *foo* with versions *1.0.0* and *2.0.0* has existing subscriptions. 2. Create a new version of the same API *3.0.0* from

Re: [Dev] API Manager associating a new version of an API with its previous version

to store this, hence Im trying to see if there is an alternative. On 22 July 2015 at 12:38, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Thanks for the suggestion Ruwan, but we are not on ES yet and wont be for sometime so we wont be able to exploit that feature. On 22 July 2015 at 12:32

Re: [Dev] API Manager associating a new version of an API with its previous version

...@wso2.com wrote: Hi Uvindra, What if we keep the parent apiID in the asset itself, rather than in new DB column. (by adding the field to api.rxt) Cheers, Ruwan On Wed, Jul 22, 2015 at 12:44 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The correct way I can think of solving

Re: [Dev] Source code for wso2 API Manager 1.8

Hi Rohit, API Manager 1.8.0 is not on github and is only available via our public svn repo, please refer[1]. API Manager source code is here[2] and you will need to refer to this pom[3] to identify which component source versions to refer to for API Manager 1.8.0 [1]

Re: [Dev] API Manager associating a new version of an API with its previous version

to the new API we can simply do a duplicate check before trying to insert subscription data which is a simple fix. So which is the correct functionality? On 22 July 2015 at 14:36, Uvindra Dias Jayasinha uvin...@wso2.com wrote: @Sajith, we already have those options you have mentioned in API

Re: [Dev] API Manager associating a new version of an API with its previous version

Ticket has been updated with the requirement, please add 1.10 release to API Manager JIRA to set the fix version so that this can be prioritised. On 22 July 2015 at 15:10, Nuwan Dias nuw...@wso2.com wrote: On Wed, Jul 22, 2015 at 2:55 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Let

Re: [Dev] API Manager associating a new version of an API with its previous version

the parent apiID in the asset itself, rather than in new DB column. (by adding the field to api.rxt) Cheers, Ruwan On Wed, Jul 22, 2015 at 12:44 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The correct way I can think of solving this is to store the apiID of the version that is being

Re: [Dev] The table 'UM_USER_ROLE' is full

Doesn't look like an issue with the script itself, this could happen because you have run out of disk space on the DB cluster or the table has reached its max allocated size, see following links, http://stackoverflow.com/questions/730579/error-1114-hy000-the-table-is-full

Re: [Dev] [APIM][1.6] Authorization scheme not checked for access token generation

Currently we are not taking any action using the auth scheme hence we dont process it at all. Since this is a specialized endpoint we are not we only dealing with auth Headers. We could check the auth scheme for the sake of simply sending an error message back if it is invalid but other than that

Re: [Dev] Writing wire logs to a separate file other than the wso2carbon.log

for writing the wso2carbon.log) On 10 June 2015 at 12:37, Uvindra Dias Jayasinha uvin...@wso2.com wrote: I've defined a custom appender in the log4j.properties of ESB 4.8.1 as follows. # WIRE_LOGFILE is set to be a DailyRollingFileAppender using a PatternLayout. log4j.appender.WIRE_LOGFILE=org.wso2

[Dev] Writing wire logs to a separate file other than the wso2carbon.log

I've defined a custom appender in the log4j.properties of ESB 4.8.1 as follows. # WIRE_LOGFILE is set to be a DailyRollingFileAppender using a PatternLayout. log4j.appender.WIRE_LOGFILE=org.wso2.custom.logging.appenders.WireDailyRollingFileAppender # Log file will be overridden by the

Re: [Dev] [APIM] Modifying Key Caches on API Manager

+1, Looks good to me. On 6 May 2015 at 11:34, Amila De Silva ami...@wso2.com wrote: Hi All, When caching is enabled on Gateway, KeyValidationInfoDTO object is kept in the cache against a cache key having the following structure; cacheKey = accessToken + : + apiContext + / + apiVersion +

Re: [Dev] [APIM] Modifying Key Caches on API Manager

Dias Jayasinha uvin...@wso2.com wrote: +1, Looks good to me. On 6 May 2015 at 11:34, Amila De Silva ami...@wso2.com wrote: Hi All, When caching is enabled on Gateway, KeyValidationInfoDTO object is kept in the cache against a cache key having the following structure; cacheKey

Re: [Dev] API Manager - deleting an API

Hi Chalitha, You should first remove any existing subscriptions[1] before you delete a given API. What is your use case for deleting APIs without user authentication? [1] https://docs.wso2.com/display/AM180/Store+APIs#StoreAPIs-RemoveaSubscription On 17 April 2015 at 14:45, Chalitha

Re: [Dev] [APIM] Adding sequence to a API to log In-flow messages not working. API Manager 1.9.0 SNAPSHOT

If you havent updated the velocity_template in API Manager with your custom handler then you will loose it from the synapse configuration when you do a save and publish. publishing will cause the contents of the synapse config to get updated with the default values in the template. On 1 April

Re: [Dev] Don't commit to APIM old test modules

If anyone is in the middle of writing a test in the module please reply to this thread. We need to ensure that we have stable pack with all tests in newly created modules passing before we can remove the old test modules. Lets try and get this done ASAP. I think there are a few new team members

Re: [Dev] API Manager New integration module structure for framework version 4.3.1.

Since APIM 1.9.0 was on svn earlier we were using the automation framework 4.2.7. But now since 1.9.0 has moved to git(but we are still using Carbon 4.2.0) do we need to change anything? We are still using version 4.2.7 of TAF. On 19 February 2015 at 10:27, Dharshana Warusavitharana

Re: [Dev] API Manager 1.8.0 - Help with velocity template file

No need to apologize, that is exactly what this mailing list is for. You need to use to escape the '$' character, try this, http://velocity.apache.org/tools/devel/generic/EscapeTool.html#getDollar%28%29 On 10 February 2015 at 06:06, satheesh sathee...@gmail.com wrote: I apologize for asking

Re: [Dev] Converting JSON to SOAP and vise versa in ESB

: application/json X-Powered-By: ASP.NET Cache-Control: private, max-age=0,public Date: Sun, 08 Feb 2015 03:48:50 GMT Server: WSO2-PassThrough-HTTP Transfer-Encoding: chunked {Temp:{Faran:53.6}} Thanks, Harsha On Sat, Feb 7, 2015 at 9:55 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote

Re: [Dev] Converting JSON to SOAP and vise versa in ESB

, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The Premature end of file exception is still happening even when I add those two properties in, this is a parser error happening on our end in the insequence itself. I still cant understand why this isnt working. On 7 February 2015 at 12:15, Chanaka

Re: [Dev] Converting JSON to SOAP and vise versa in ESB

=true scope=axis2/property Try the above properties prior to the send mediator. Thanks, Chanaka On Fri, Feb 6, 2015 at 11:28 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Ok tried that Dushan, but now I get a different exception when I hit the insequence 23:24:38,849 LogMediator

Re: [Dev] Converting JSON to SOAP and vise versa in ESB

=0,public Date: Fri, 06 Feb 2015 17:19:20 GMT Server: WSO2-PassThrough-HTTP Transfer-Encoding: chunked {Temp:53.6}xxx-xxx-Pro:bin xx$ On Thu, Feb 5, 2015 at 1:10 AM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Thanks Sampath and Asanka, Tried both your suggestions and now Im getting

Re: [Dev] Converting JSON to SOAP and vise versa in ESB

-Type:application/json' -d '{celsius:12}' http://IP Address:8280/api context Thanks, Asanka D On Wed, Feb 4, 2015 at 9:03 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Im trying out Payload and Script mediator functionality to call this SOAP service, http://www.w3schools.com/webservices

[Dev] Converting JSON to SOAP and vise versa in ESB

Im trying out Payload and Script mediator functionality to call this SOAP service, http://www.w3schools.com/webservices/tempconvert.asmx?op=CelsiusToFahrenheit by simulating a REST API using ESB 4.8.1, here is the synapse configuration I have defined api xmlns=http://ws.apache.org/ns/synapse;

Re: [Dev] Greg build failure in APIM features installation

Hi Roshan, Your pull request has been merged On 22 January 2015 at 11:12, Roshan Wijesena ros...@wso2.com wrote: [Looping Ruwan] On Thu, Jan 22, 2015 at 11:10 AM, Roshan Wijesena ros...@wso2.com wrote: Hi Nuwan/Ruwan Please merge the pull request to wso2-dev/apimgt [1].

[Dev] [DEV][Synapse] Sending a JSON response to an API invocation

Hi All, Im trying to send a simple JSON response when an API gets invoked, but I can only manage a SOAP envelope as the response, here is the synapse configuration, ?xml version=1.0 encoding=UTF-8?api xmlns= http://ws.apache.org/ns/synapse; name=HealthCheck_API context=/check_health resource

Re: [Dev] [DEV][Synapse] Sending a JSON response to an API invocation

This is using API Manager 1.4 which uses synapse version 2.1.1.wso2v5 On 16 December 2014 at 11:11, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Hi All, Im trying to send a simple JSON response when an API gets invoked, but I can only manage a SOAP envelope as the response, here

Re: [Dev] [DEV][Synapse] Sending a JSON response to an API invocation

, but when this is commented and the below formatter is enabled instead, messageFormatter contentType=application/json class=org.apache.axis2.json.JSONMessageFormatter/ it works. Thanks Shafreen. On 16 December 2014 at 11:16, Uvindra Dias Jayasinha uvin...@wso2.com wrote: This is using

Re: [Dev] [DEV][Synapse] Sending a JSON response to an API invocation

build the message using the builder mediator at the API. builder class=org.apache.axis2.json.JSONBuilder formatterClass=org.apache.axis2.json.JSONMessageFormatter/builder Thanks. On Tue, Dec 16, 2014 at 11:39 AM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Okay Shafreen helped diagnose

[Dev] [DEV][IS] LDAP vs JDBC user store

What is the advantage/disadvantage(if any) of using the embeded LDAP user store Vs a JDBC user store in IS? Thanks -- Regards, Uvindra Mobile: 33962 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [DEV][API-M] - SSO Cofiguration Documentation issue

Even if that works still we will need to do the change to the documentation, since if we follow the official documented method for enabling SSO it does not work for tenant users. On 29 October 2014 20:39, Nuwan Dias nuw...@wso2.com wrote: What if you define the SP as a 'SaaS Application',

Re: [Dev] API Manager 1.8.0 pack 20-10-2014

/jira/browse/APIMANAGER-3021 Regards, Evanthika On Wed, Oct 22, 2014 at 3:22 PM, Yasassri Ratnayake yasas...@wso2.com wrote: Thanks, We will be using the provided scripts for time being. On Wed, Oct 22, 2014 at 2:52 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Ticket has been

Re: [Dev] API Manager 1.8.0 pack 20-10-2014

I am looking into this, the script has been changed recently On 22 October 2014 07:53, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, There seems to be an Syntax error in the mysql DB scripts(apim scripts), and due to this some of the tables do not get created. I have reported this at

Re: [Dev] API Manager 1.8.0 pack 20-10-2014

did not cause any issues. On 22 October 2014 09:41, Uvindra Dias Jayasinha uvin...@wso2.com wrote: I am looking into this, the script has been changed recently On 22 October 2014 07:53, Yasassri Ratnayake yasas...@wso2.com wrote: Hi All, There seems to be an Syntax error in the mysql DB

Re: [Dev] API Manager 1.8.0 pack 20-10-2014

Uvindra, I'm using *mysql 5.5.40*. Till you fix this issue is it OK if we use the scripts from the 6th October pack since this issue is blocking us. With regards, On Wed, Oct 22, 2014 at 9:50 AM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: The change to the script was introduced via

Re: [Dev] API Manager 1.8.0 pack 20-10-2014

to create databases for your testing On 22 October 2014 10:02, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Yes you can use the scripts from the previous pack to continue but refrain from testing any *work flow* related functionality until we resolve this for the moment. We will change

Re: [Dev] API Manager 1.8.0 pack 20-10-2014

p2-repo has also been uploaded to the above svn location On 21 October 2014 10:27, Uvindra Dias Jayasinha uvin...@wso2.com wrote: will do, still building it On 21 October 2014 10:24, Abimaran Kugathasan abima...@wso2.com wrote: Hi Uvindra, Is it possible to commit p2 repo also here

Re: [Dev] API Manager 1.8.0 pack 20-10-2014

will do, still building it On 21 October 2014 10:24, Abimaran Kugathasan abima...@wso2.com wrote: Hi Uvindra, Is it possible to commit p2 repo also here? On Mon, Oct 20, 2014 at 7:22 PM, Uvindra Dias Jayasinha uvin...@wso2.com wrote: Hi All, $subject can be found at, https://svn.wso2

  1   2   >