Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Working with REST | Generating a REST Resource Using the Legacy Approach | About the Folder for REST Resources Created Using the Legacy Approach
 
About the Folder for REST Resources Created Using the Legacy Approach
Designer uses the icon to indicate that the folder corresponds to a REST resource created using the legacy approach. Prior to Designer version 9.10, Designer used a regular folder icon for a REST resource folder. From version 9.10 onwards, Designer uses the icon for a REST resource.
When you change the contents of a folder, Designer analyzes the contents of each existing folder. If the folder contains any child service considered to be a REST resource, specifically _get, _put, _post, _patch, _delete, or _default, Designer changes the regular folder icon to the REST resource folder icon. However, if a folder contains a _delete service and other services used with OData, specifically _retrieve, _update, and _insert, Designer does not change the folder icon to be that of a REST resource folder icon.
Note:
If you upgrade to Integration Server version 9.10 or later from a version of Integration Server prior to 9.10, Designer uses the specified logic to convert regular folders to REST resource folders.
If the contents of a REST resource folder change such that Designer no longer considers the folder and its contents to be a REST resource, Designer replaces the REST resource folder icon with the regular folder icon. For example, suppose that a REST resource folder named topics contains services named _get, _delete, and _default. If you delete all of the services from topics, Designer uses the regular folder icon for the topics folder.