Issues with Swagger client generation for Java

I have noticed two problems with the generated Java client code. At the moment, these require manual changes by me in order to use the client API code.

  1. The user ‘pmi’ field is typed as a Java Integer in the InlineResponse20033 model class, but the field is required to have 10-digits. This means that any pmi which represents a number greater than 2147483647 (0x7FFFFFFF) will overflow the Java Integer type, and de-serialization (for example, Jackson libraries) will throw an exception.

  2. The account ‘id’ field is typed as a java.util.UUID in the AccountListAccounts model class, and the UUID type has a specific 36-character format (including 4 dashes). The ids of the test accounts that we have created do not follow this format (they are 22-character strings), and so de-serialization (for example, Jackson libraries) will throw an exception. I am assuming these id’s are generated by the Zoom system.

Thanks
Lloyd

Hey @lweber.bt_dev, thanks for posting and using Zoom!

We are working on fixing the generation of the Java Client Code. I will post back here once it is fixed.

Duplicate Post:

Apologies for the inconvenience.

Thanks,
Tommy

Hey @lweber.bt_dev,

Can you try again? We have updated the Client Code.

Let me know if it works for you! :slight_smile:

Thanks,
Tommy