tp://wso2.com/signature] <http://wso2.com/signature>
>>
>
>
> --
> Mushthaq Rumy
> *Senior Software Engineer*
> Mobile : +94 (0) 779 492140
> Email : musht...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
> <http://wso2.com/
can attach a tier with 'pay as you use' type. Then, usage
will be aggregated daily / or set for each subscriber. At the end of each
month, subscriber will be charged for the aggregated usage.
API provider will be able to see the revenue from each user of their API.
Thanks.
On Mon, Apr
cessfully based on some set policy,
>>>> before taking it as a count to bill. But in the current stats there is no
>>>> such a check when we aggregate the request count and all of them are simply
>>>> added to the count through API Request count Aggregation. So if we
://stripe.com/docs/api/charges?lang=curl
Thanks.
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
have any suggestions.
>>
>> [1] https://getuikit.com/v2/docs/htmleditor.html
>>
>> Thank you and Best Regards,
>>
>> *Varuni Punchihewa*
>> Software Engineer - Intern | *WSO2*
>> *Tel:* +94 71 699 5861
>> <http://wso2.com/signature>
>&g
On Thu, Oct 25, 2018 at 3:14 PM, Chamin Dias wrote:
> Hi all,
>
> We are in the process of doing $subject. We came across few (possible)
> libraries to fulfill the requirement.
>
> Here is the summary of each library (as at 2018/10/25).
>
>
> *Option 1 : reac
ct-markdown.*
Please share if you have any better suggestion than this.
Thanks.
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
e | Mail Archive
-
User List: u...@wso2.org | Subscribe | Mail Archive
Reporting Issues
We encourage you to report issues, documentation faults, and feature
requests regarding WSO2 API Manager through the public API Manager Git Repo
<https://github.com/wso2/product-apim/issues>.
-- The
/resources/store-api.yaml#L3668
>> [2] [Dev] [APIM_REST_API] What are the properties to include in DTO
>>
>>
>> Regards,
>> *Dushani Wellappili*
>> Software Engineer - WSO2
>>
>> Email : dusha...@wso2.com
>> Mobile : +94779367571
>> Web : https://wso2.com/
>&
ena*
> Senior Software Engineer
> WSO2 Inc.
>
> Phone : +94 71 350 5470
> LinkedIn : https://lk.linkedin.com/in/menakajayawardena
> Blog : https://menakamadushanka.wordpress.com/
>
>
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://
;>>>>>>
>>>>>>> Tested the following in API Manager RC4. No issues found.
>>>>>>>
>>>>>>> 1. Basic API and Application flow
>>>>>>> - API Creation, Publishing, Key generation, Subscription and
>>>&
gt; - Block list policies
> 4. Microgateway label add/update REST API
> 5. Test with browser IE 11
> - basic flow (Super tenant/tenant)
> - Label add/update
>
> [+]Stable - go ahead and release
>
> Thanks,
> krishan.
>
>
>
> On Thu, Jun 21, 20
ain why)
*Note : We can still use APIM-Analytics 2.5.0-rc1 for analytics (no issues
reported so far).*
Thanks,
WSO2 API Manager Team.
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
;> On Tue, Jun 19, 2018 at 10:09 AM Vithursa Mahendrarajah <
>>> vithu...@wso2.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have tested following and no issues found.
>>>>
>>>>- Application creation, update and key generati
ion feature
>
>
> [+]Stable - go ahead and release
>
>
> Thanks,
> Chamalee
>
>
>
> On Tue, Jun 19, 2018 at 12:07 AM, Chamin Dias wrote:
>
>> Hi all,
>>
>> We are pleased to announce the third release candidate of WSO2 API
>> Manager
lain why)
Note : We can still use APIM-Analytics 2.5.0-rc1 for analytics (no issues
reported so far).
Thanks,
WSO2 API Manager Team
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Architec
ave to update those.
>
> Hense -1 for the RC2.
>
> Thanks,
> Bhathiya
>
>
>
> On Mon, Jun 18, 2018 at 12:35 PM Chamin Dias wrote:
>
>> Tested : API creation, Application creation, Subscription and API
>> invoking (Mac OS - Chrome) and it worked fine.
>
Tested : API creation, Application creation, Subscription and API invoking
(Mac OS - Chrome) and it worked fine.
[+] Stable - go ahead and release
Thanks.
On Mon, Jun 18, 2018 at 12:04 PM, Chamin Dias wrote:
> Hi all,
>
> We are pleased to announce the second release candidate of
lain why)
*Note : We found an issue
<https://www.mail-archive.com/architecture@wso2.org/msg16436.html> in APIM
2.5.0-rc1 only. Therefore we can still use APIM-Analytics 2.5.0-rc1 for
analytics.*
Thanks,
WSO2 API Manager Team
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
Li
ssues/5493
>
> Thanks
> *Prasanna Dangalla*
> Senior Software Engineer, WSO2, Inc.; http://wso2.com/
> lean.enterprise.middleware
>
> We will fix the issue and release another release candidate as soon as
possible.
Thanks
>
> *cell: +94 718 11 27 51*
> *twitter: @prasa77
oken - do not release (explain why)
Thanks,
WSO2 API Manager Team
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso
regarding WSO2 API Manager through the public API Manager Git Repo
<https://github.com/wso2/product-apim/issues>.
-- The WSO2 API Manager Team --
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
__
>>>>>>>> Senior Software Engineer
>>>>>>>> WSO2 Inc
>>>>>>>> Mobile : +94772338839
>>>>>>>> fazl...@wso2.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>&g
Prasanna
>>
>>>
>>> On Fri, May 4, 2018 at 5:45 PM, Malintha Amarasinghe >> > wrote:
>>>
>>>> Hi,
>>>>
>>>> On Fri, May 4, 2018 at 11:15 AM, Prasanna Dangalla
>>>> wrote:
>>>>
>>>>>
>>&
___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
#x27;re doing this feature for API Manager 2.x and since it has the
> old/monolith Gateway which hosts all APIs anyway, I think its less
> important for the need to have to deploy all APIs on a Microgateway. Which
> lessens the need for a default label.
>
>>
>> @Krishan Wijesena : I think it is better to have a
>> separate table for access urls. In the future, if we need to treat the
>> protocol of the access urls, then having a separate table would be easy.
>> Also, without appending the API table to attach the label id of the API, we
>> should have a separate table for API to label mapping. API can have
>> multiple labels.
>>
>> Thank you!
>> --
>> *Pubudu Gunatilaka*
>> Committer and PMC Member - Apache Stratos
>> Senior Software Engineer
>> WSO2, Inc.: http://wso2.com
>> mobile : +94774078049
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Architect - WSO2, Inc. http://wso2.com
> email : nuw...@wso2.com
> Phone : +94 777 775 729
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
LinkedIn : https://www.linkedin.com/in/chamindias
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
isting labels in the system) and attach. If the
labels are already there, we can just attach them to the newly created API.
This is the initial design for $subject. Please share your thoughts on
this. It is highly appriciated.
Thanks.
--
Chamin Dias
Mobile : 0716097455
Email : cham...@wso2.com
Li
per API? Do we have
any mechanism to handle those kind of scenarios?
Regards,
>> Sivaramya Sivanathan
>> Associate Software Engineer | WSO2
>> Tel: 0770874960 <077%20087%204960>
>> WSO2 Inc : http://wso2.org
>> <http://www.google.com/url?q=http%3A%2F%2Fwso2
this is to address practical issues that take
>>>>>> place when the App owner leaves an organization and there needs to be
>>>>>> some
>>>>>> way to delete/update such an Application.
>>>>>>
>>>>>
ftware Engineering Intern | WSO2 Inc
>>
>> Email : ren...@wso2.com
>> Mobile : +94 76 667 8752 <076%20667%208752>
>> Web : http://wso2.com
>> <http://wso2.com/signature>
>>
>
>
>
> --
>
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +
gt;>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94779109091 <+94%2077%20910%209091>*
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture
configuraton exists in the api-manager.xml then the existing
>>>>> workflow will execute using the "Authorization" header field.
>>>>>
>>>>>
>>>>> ii) Proposed workflow for restricting the access token from being
>>&g
c OS.
>>>
>>>
I think you can get some input from here
<https://github.com/wso2/product-apim/tree/v2.1.0/modules/api-import-export>.
We have addressed few similar situations earlier.
Thanks.
--
Chamin Dias
Mobile : 0716097
sed for querying?
>>>
>>> If you need a search based on "name of the API AND the version of the
API" only, then we can get data by using AM_API table solely. If the search
goes to other tables such as AM_API_TAG_MAPPING (Eg :
name:sampleapi&version:1.0.0&tag:wso2),
hing
> criteria\",\"schema\":{\"type\":\"array\",\"items\":{\"$ref\":\"#/definitions/InventoryItem\"}}},\"400\":{\"description\":\"bad
> input parameter\"}}},\"post\":{\"tags\":[\&q
egards
>>
>> --
>> *Renuka Fernando*
>> Software Engineering Intern | WSO2 Inc
>>
>> Email : ren...@wso2.com
>> Mobile : +94 76 667 8752 <076%20667%208752>
>> Web : http://wso2.com
>> <http://wso2.com/sig
t;> Architecture mailing list
>>>> Architecture@wso2.org
>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>>
>>>>
>>>
>>>
>>> --
>>> Thanks and Regards,
>>>
>>> Isuru H.
>>&g
API Editor which are going to be inherited
from Publisher. The reason is, it will help us to come up with an effective
implementation mechanism (like reusing existing functions etc.). WDYT?
> The Editor application is *run locally* in the API developers machine and
>>> is used primarily
gt;*
> mobile :- *+94 7 <%2B94%2077%202782039>1 4315942*
>
>
>
>
> --
> Thanks & Regards,
>
> *Chamalee De Silva*
> Software Engineer
> *WS**O2* Inc. :http://wso2.com/
>
> Office :- *+94 11 2145345 <%2B94%2011
NAGER-5494>] - Add
useful property values for In, Out and Fault sequences
- [APIMANAGER-5495 <https://wso2.org/jira/browse/APIMANAGER-5495>] -
Bottleneck in throttle policy deployment to Traffic Manager
- [APIMANAGER-5497 <https://wso2.org/jira/browse/APIMANAGER-5497>] - Non
- Use
different keystore for Data Bridge Configuration
- [APIMANAGER-5443 <https://wso2.org/jira/browse/APIMANAGER-5443>] -
Provide "Get API" in store RESTapi's
- [APIMANAGER-5454 <https://wso2.org/jira/browse/APIMANAGER-5454>] -
Manage Alert Types
; --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Team Lead - WSO2 Machine Learner
>> Associate Technical Lead - Data Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>>
>>
> Software Engineer
>>>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20773%20451194>
>>>> E-mail : thili...@wso2.com
>>>>
>>>> WSO2 Inc. www.wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> _
WSO2 Inc.; http://wso2.com
> E-mail: sachith AT wso2.com
> M: +94715518127
> Linked-In: <http://goog_416592669>
> https://lk.linkedin.com/in/sachithwithana
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.or
gt;>> in each month. This is useful for resource allocation purposes.
>>>>>>>>>>>
>>>>>>>>>>> I have attached the class diagram of the REST api. The new stats
>>>>>>>>>>> REST api will be integrated with the existin
www.google.com/profiles/harshana05
>
> On 20 May 2015 at 12:46, Chamin Dias wrote:
>
>> Hi all,
>>
>> A slight modification has been proposed and agreed at the review,
>> regarding the tier check of API Import process. According to that, we
>> decided to im
imported API.
Thanks.
On Thu, May 14, 2015 at 11:56 AM, Nuwan Dias wrote:
> In case of a failure, it should return an HTTP 500 mentioning the reason
> for failure accurately.
>
> Thanks,
> NuwanD.
>
> On Thu, May 14, 2015 at 10:58 AM, Chamin Dias wrote:
>
>> Hi all,
&
s an API archive with the above
>>>>>>>>>mentioned structure and create a new API under current provider.
>>>>>>>>>
>>>>>>>>> *Feature Implementation*
>>>>>>>>>
>>>>>>>
48 matches
Mail list logo
