Open APIs

 View Only

  • 1.  TMF641 Characteristic Value

    Posted Sep 19, 2019 08:58

    We're currently looking at using TMF641. We're using standard tools (swagger-code-gen @ https://github.com/swagger-api/swagger-codegen) to convert the Swagger spec. for 641 to some POJO models. FWIW, we're using V.18.5, also referenced as version 4.0.0 in the swagger file itself, not sure which version is the 'correct' reference.

    Now, the trouble is that the value of the "Characteristic" is of type "Any". I see from Open APIs that it can be "any json object". Which is fine, except it's not possible to set the value of an "Any". Now, the thread mentions that a provider should set a @type / @schemaLocation for this object, but that doesn't help much with using generated code based of the swagger spec. Or is the intent that the provider would take the base swahher spec, customise it and publish that?

    Or have I missed something?

    Thanks,

    Greg

    ​​


  • 2.  RE: TMF641 Characteristic Value

    Posted Mar 19, 2020 07:49
    I am facing the exact same issue while trying to implement TMF 641. Any type is not being accepted. Can anyone please shed some light if they have a workaround for this.

    ------------------------------
    Zayn AS
    TO BE VERIFIED
    ------------------------------



  • 3.  RE: TMF641 Characteristic Value

    Posted Mar 19, 2020 10:11
    Please see my post from today in this thread https://engage.tmforum.org/communities/community-home/digestviewer/viewthread?GroupId=31&MessageKey=06abec6e-393f-4729-9f9e-cf6cec91c8d5&CommunityKey=d543b8ba-9d3a-4121-85ce-5b68e6c31ce5&tab=digestviewer&ReturnUrl=%2fcommunities%2fcommunity-home%2fdigestviewer%3fcommunitykey%3dd543b8ba-9d3a-4121-85ce-5b68e6c31ce5%26tab%3ddigestviewer 

    It's in the middle of the thread, explaining upcoming changes to the Characteristic pattern to fix the Any concern.

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


Related Content