quot;this is another reply",
>> "timestamp":"x03"
>> }
>> ]
>>},
>>{
>> "id":"12438",
>> "comment":"this is another parent comment",
>&g
entId}
> For each commentReply in replyList{
>Display commentReply;
> }
> }
> }
But the drawback in here is that there will be two database calls when
listing a single comment with replies.
What do you think about this?
Thank you!
--
Wasura Wat
Hi all,
Sorry for the inconvenience. The methods that I have already implemented
are not visible in the above mail. Check below for the methods.
[image: Capture.PNG]
Thanks!
On Sat, Oct 27, 2018 at 12:00 PM Wasura Wattearachchi
wrote:
> Hi all,
>
> This is related to the mail thread
; Thanks
>
> On Mon, Oct 29, 2018 at 8:36 AM Wasura Wattearachchi
> wrote:
>
>> Hi all,
>>
>> Will move the logic to the backend as Bhathiya has suggested, and will
>> get the response similar to the dummy comments json in the UI.
>>
>> T
comments for API " + apiId;
throw new APIMgtDAOException(DAOUtil.DAO_ERROR_PREFIX +
errorMessage, e);
}
return commentList;
}
Thanks,
Wasura
On Mon, Oct 29, 2018 at 8:31 AM Wasura Wattearachchi
wrote:
> Hi all,
>
> Will move the logic to the backend as Bhathiya has suggested
.
>>> (m) +94 (71) 9143658 | (w) +94 (11) 2145345 | (e) nad...@wso2.com
>>> [image: http://wso2.com/signature] <http://wso2.com/signature>
>>>
>>>
>>
>> --
>> *Rajith Roshan* | Associate Technical Lead | WSO2 Inc.
>> (m) +94-717-064-
[-] Broken - Do not release *(explain why)
>
>
>
> Best Regards,
> WSO2 API Manager Team
>
> --
> *Naduni Pamudika* | Senior Software Engineer | WSO2 Inc.
> (m) +94 (71) 9143658 | (w) +94 (11) 2145345 | (e) nad...@wso2.com
> [image: http://wso2.com/signature] <ht
curity Vulnerability
Reporting Guidelines
<https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines>
when
reporting the security issues.
*-- The WSO2 API Manager Team --*
--
*Wasura Wattearachchi* | Software Engineer | WSO2 Inc.
(m) +94775396038 | (e) was
Hi all,
*Bug Fixes And Improvements in API Manager Tooling 2.0.9*
>
The above heading in the above mail should be changed to *Bug Fixes And
Improvements in API Manager Tooling 2.0.10*.
Sorry for the inconvenience caused.
Thanks!
--
*Wasura Wattearachchi* | Software Engineer | WSO2 Inc.
ocs.wso2.com/en/3.2.0/install-and-setup/upgrading-wso2-api-manager/upgrading-process/
>>>>>>>>>>
>>>>>>>>>> Please download, test the product and vote.
>>>>>>>>>>
>>>>>>>>>> [+] Stable - go ahead and release
>>>>>>&g
>>> Kubernetes API operator to deploy and manage APIs in the Kubernetes
>>>>> cluster
>>>>> by reducing additional overheads for the DevOps.
>>>>>
>>>>> Please find the new features, improvements and fixes related to this
>>
Vulnerability
Reporting Guidelines
<https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines>
when
reporting the security issues.
*-- The WSO2 API Manager Team --*
--
*Wasura Wattearachchi* | Software Engineer | WSO2 Inc.
(m) +94775396038 | (e) was...@wso2.com
mail : musht...@wso2.com
> WSO2, Inc.; http://wso2.com/
> lean . enterprise . middleware.
>
> <http://wso2.com/signature>
>
--
*Wasura Wattearachchi* | Software Engineer | WSO2 Inc.
(m) +94775396038 | (e) was...@wso2.com | (b) Medium
<https://medium.com/@wasuradananjith>
[image: http:
minda
>
> On Sun, Aug 16, 2020 at 4:25 PM Wasura Wattearachchi
> wrote:
>
>> Hi all,
>>
>> I tested the following scenarios in APIM 3.2.0 RC5.
>>
>>- Reverse Proxy
>>- Product Profiles
>> - Traffic Manager
>> - Key Manager
14 matches
Mail list logo
