Removing an OpenAPI Specification
From the External Components Browser, the Remove command in the OpenAPI submenu of the Components menu enables you to remove (delete) the currently selected OpenAPI specification from your JADE schema.
You cannot remove an OpenAPI specification when any references exist to classes belonging to that specification.
To remove an OpenAPI specification
-
In the External Components Browser, select the OpenAPI specification that you want to remove.
-
Select the Remove command from the OpenAPI submenu of the Components menu. A message box is then displayed, to enable you to confirm that you want to remove the selected OpenAPI definition.
-
Click the Yes button to confirm that you do want to delete the selected OpenAPI definition. (Alternatively, click the No button to abandon the deletion.)
The Schema Versioned message box is then displayed, stating that the schema has been versioned. When you click the OK button and you have reorganized the versioned schema, the External Components Browser is then updated to reflect the removal of the selected OpenAPI definition. There may be a momentary delay while this updating occurs.
When you delete an OpenAPI definition, JADE removes:
-
The selected specification.
-
All associated classes; that is, all
Although you can remove OpenAPI REST object classes from the Schema Browser, it is not recommended as it results in the library remaining partially defined in JADE. If you later wanted to add the classes that you deleted, you must first completely remove the OpenAPI specification and then import that specification again.
2020.0.01 and higher
