Open APIs

  • 1.  TMF630 GET with url encoded values

    Posted 16 days ago
    Hello guys.
    I need some clarification regarding the GET option with url-encoded values. according to the document :
    "TMF630_REST_API_Design_Guidelines_Part_1_v4.2.0.pdf" on the page 32 of the document there is this example :

    •GET /api/troubleTicket?dateTime%3E2013-04-20&status=acknowledged

    Unfortunately if I try to send this url to my Java spring boot based application , dateTime value arrives as a null and it works just in case I add "=" between string and values, as it here:

    • GET /api/troubleTicket?dateTime=%3E2013-04-20&status=acknowledged.

    Unfortunately the client defined the requirements according to the document and does not want to change it without any evidence from the forum.
    Can  you explain ,please, if I can make any tweaks in my code or to use any special api for that to work or there is an error in the document?
    My code in java looks this way:


    @RequestMapping(value = "/test", method = RequestMethod.GET, consumes = MediaType.APPLICATION_FORM_URLENCODED_VALUE)
    public ResponseEntity<List<Object>> listService(
    @RequestParam(value = "date", required = false) String dateTime,
    @RequestParam(value = "state", required = false) String status) {
    ...some logic here
    }

    Thank you very much,
    Alex Etin


    ------------------------------
    Alexander Etin
    TO BE VERIFIED
    ------------------------------


  • 2.  RE: TMF630 GET with url encoded values

    TM Forum Member
    Posted 14 days ago
    This appears to be a duplicate post, please go to the other post here.

    ALL - Please note that when you post on the community for the first time, your post is subject to moderation so you won't necessarily see it immediately.
    Be patient and please don't submit the post again.

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