Trace: • Portlet Integration • Asynchronous Communication Using CallBack • Open a “Managed” Custom Dialog • Using XmlSecurityManager • Customize an Application Without Derivation • Push support
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
applications:swagger_filter [2019/04/05 11:54] admin |
applications:swagger_filter [2020/07/01 17:15] (current) cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation) |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ~~Title: REST API Filter~~ | ~~Title: REST API Filter~~ | ||
| - | If you use [[https://swagger.io/tools/swagger-ui/|Swagger UI]] for REST API documentation, it's relevant to set the correct **host** and **basePath** in the specification file. To use the current host and path, simply use the integrated Filter: | + | If you use [[https://swagger.io/tools/swagger-ui/|Swagger UI]] for REST API documentation, it's relevant to set the correct **host** and **basePath** in the specification file. To use the current host and path, simply use the integrated filter. It will replace the **host** and **basePath** with current information: |
| - | It will replace the **host** and **basePath** with current information: | + | |
| <file xml> | <file xml> | ||
| Line 11: | Line 10: | ||
| <async-supported>true</async-supported> | <async-supported>true</async-supported> | ||
| </filter> | </filter> | ||
| + | | ||
| <filter-mapping> | <filter-mapping> | ||
| <filter-name>RestApiFilter</filter-name> | <filter-name>RestApiFilter</filter-name> | ||
| Line 16: | Line 16: | ||
| </filter-mapping> | </filter-mapping> | ||
| </file> | </file> | ||
| + | |||
| + | The filter only supports **json** specification files. | ||