Hi Sameer
This is an interesting point, I'll see if I can bring it to the Open API team leadership.
In the meantime, perhaps
@Henrique Rodrigues can assist to see if there is a way of working round this limitation.
Hope it helps
------------------------------
Jonathan Goldberg
Amdocs Management Limited
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
Original Message:
Sent: Feb 18, 2020 01:51
From: Sameer Uppal
Subject: TMF622 CTK issue due to separate command and query API url
Hi All,
We have enhanced TMF622 and we were trying to evaluate CTK for TMF622. We found below gaps
We are following CQRS pattern in TMF622 and as part of this we have created 2 separate APIs.
- Command API which is catering POST, PATCH operation.
- Query API for GET method.
Product Order Command API Controller
POST/v1/order-command-api/productOrder
Create New ProductOrder
PATCH/v1/order-command-api/productOrder/{id}
updateProductOrderPartially
Product Order Query API Controller
GET/v1/order-query-api/productOrder
getProductOrders
GET/v1/order-query-api/productOrder/{id}
getProductOrderById
GET/v1/order-query-api/productOrder/search
getProductOrderByFilterCriteria
When we checked TM Forum CTK than found that POST, PATCH and GET operation should be on the same path. Because CTK is taking the relative path one time and CTK check all GET, POST and PATCH operation one by one and generate report. Our POST operation is failing because POST is present on separate path.
Kindly suggest how to handle this situation.
Thanks and Regards,
Sameer Uppal
Mobile: +91 9958199197