Contact Us 1-800-596-4880
  1. Homepage
  2. Anypoint Code Builder

  3. Implementation Errors

Implementation Errors

logo cloud IDE Cloud IDE

logo desktop IDE Desktop IDE

Open Beta Release: The cloud IDE and AsyncAPI implementation support are in open beta. Any use of Anypoint Code Builder in its beta state is subject to the applicable beta services terms and conditions, available from the IDE.

You might encounter problems when implementing an API.

Something Failed While Scaffolding an API

Anypoint Code Builder does not support the scaffolding of AsyncAPI, OAS, or JSON schema fragment files that are referenced from API specs. The scaffolder does not add these fragments as project dependencies when you import the specification from Exchange. However, you can scaffold and reference fragments that are specified inline, within the spec. RAML fragments imported from Exchange are not affected by this limitation.

If you attempt to scaffold an API that references these types of fragments, you see a message like the following:

Something failed while scaffolding API

The scaffold fails and the flows and other elements aren’t created.

If you use the iterative approach to scaffold the API (using multi-root workspaces), the implementation project folder structure is not created.

To work around this issue, before scaffolding the API:

  1. Add the fragment directly to a folder in your API spec project, such as fragments:

    Fragment folder in the Explorer view

  2. Change the path to the fragment from Exchange to the local folder, for example:

    • Reference Local OAS Fragment

    • Reference OAS Fragment on Exchange

    $ref: fragments/frag-defs.yaml#/components/examples/flightsList
    $ref: exchange_modules/e91cab06-650b-4634-9c6f-5bc4f4fc4d17/frag-defs/1.0.0/frag-defs.yaml#/components/examples/flightsList

  3. Re-scaffold the API.

See Create and Add a Fragment Directly in Your Spec.

See Also