1

Have there been updates made to the response objects from the Model Derivative API as we are having issues mapping the responses from requests for 3D models back into the Manifest and Metadata objects.

Both are throwing Jackson errors.

  1. GetManifest is returning an unhandled role enum
  2. GetMetadataForGuid is throwing - Illegal character ((CTRL-CHAR, code 31))

Thanks

Stevie754
  • 124
  • 7

2 Answers2

1

I got what's wrong with the issue. The response of Get Manifest endpoint did changed a bit recently. There will a property database node aside the geometry nodes for Revit generated manifest. So one new role is 'Autodesk.CloudPlatform.PropertyDatabase'. While the old JAVA object ManifestChildren.JAVA does not declare the role. which caused the failure. enter image description here

To fix it, you can simply add the new role in ManifestChildren.JAVA e.g.

enter image description here

i have requested a commit for JAVA SDK. you could modify it directly at your side if you merge the SDK source code to your project.

Hope this helps.

Xiaodong Liang
  • 2,051
  • 2
  • 9
  • 14
  • how do we keep a track of when objects change shape? I have been unable to find any release notes anywhere detailing the changes? Thanks – Neil_M Dec 01 '17 at 09:52
  • 1
    @Neil_M This sounds a change that is missed to announce. We have raised a request with engineer team to ask to post public notifications on such object change in the future. Apologize for all troubles that caused to your project. – Xiaodong Liang Dec 01 '17 at 14:08
0

This is to answer the second question as references for all.

The problem is due to the header is set to "gzip" format when calling GET :urn/metadata/:guid. If it is not "gzip", all work well. While with other ways such as Postman, the header with gzip can also work.

In the past, when clients used gzip header, actually it doesn't trigger a gzip encoding. So everything is fine. After the release recently, the content returns the content in gzip if gzip is specified, while the SDK doesn't handle it correctly. Postman unzips the gzip to json automatically, so it looks working.

So, the fix could be adding one line in the ApiClient.java at line 115: client.addFilter(new GZIPContentEncodingFilter(false));

I also forked the source github repository in my space with the fixes on the two problems. a pull request is commit to the main repo. that is to allow the response of API call can handle gzip content and unzip it. https://github.com/xiaodongliang/forge-api-java-client

We apologize for the two issues that have affected some projects using SDK.

Xiaodong Liang
  • 2,051
  • 2
  • 9
  • 14