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
------------------------------
Original Message:
Sent: Sep 03, 2019 11:46
From: Greg Thomas
Subject: TMF641 Characteristic Value
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