Contact Free trial Login

Using Published RAML API Specifications in Studio 7.x and Mule Runtime 4.x

As described in Modify Published RAML API Specifications to Conform Completely to RAML 0.8 or 1.0, the code editor in Design Center is now (as of January 10, 2019) more precise in ensuring that the RAML in your API specifications is valid. The only way in which the changes to the editor will affect how published RAML API specifications are used in Studio 7.x and Mule Runtime 4.x will be to prevent a small percentage of cases where a specification published as valid from the code editor is flagged with invalid RAML in Studio. With the changes, the code editor and Studio will be consistent in how they check for invalid RAML.

Scenarios involving Anypoint Studio 7.x and Mule Runtime 4.x

  • Both before and after the release of the changes to the code editor, in the majority of cases, a valid RAML API specification that is published to Exchange from the code editor will not be flagged with additional RAML errors when opened in Studio 7. Moreover, the implementation that is created in Studio 7 will be able to run without errors in Mule Runtime 4.

  • Before before and after the release of the changes to the code editor, it is possible in some cases to publish to Exchange an API specification that still has invalid RAML according to the code editor, yet open the specification in Studio 7 and see no invalid RAML flagged. Also, the implementation that is created in Studio 7 will be able to run without errors in Mule Runtime 4.

  • In a very small number of cases before the release of the changes to the code editor, a RAML API specification that the code editor considers to be valid and that is published to Exchange could be flagged with additional RAML errors when opened in Studio 7. In such cases, it will not be possible to create an implementation of the API specification and then run the implementation in Mule Runtime 4. If you experience this problem, contact MuleSoft Technical Support.

Scenarios involving Mule Runtime 4.x

  • In all cases, both before and after the release of the changes to the code editor, a valid RAML API specification that is published to Exchange from API Designer can be deployed as an API proxy in Mule Runtime 4.

We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used and to tailor advertising. You can read more and make your cookie choices here. By continuing to use this site you are giving us your consent to do this.