-
Enhancement
-
Resolution: Unresolved
-
Major
-
36.0.0.Final
-
None
Currently, only one deployment containing REST applications may register an OpenAPI endpoint for a given host.
Subsequent deployments will log a message such as "MicroProfile OpenAPI endpoint already registered for host '...'. Skipping OpenAPI documentation of '...'."
This jira seeks to enhance the MicroProfile OpenAPI subsystem to allow multiple deployments to publish to the same endpoint.
- is blocked by
-
WFWIP-688 MicroProfile OpenAPI and multiple deployments: an identical operation is not documented correclty based on each deployment that declares it
-
- Resolved
-
-
WFWIP-697 MicroProfile OpenAPI and multiple deployments: conflicting root level ".tags" definitions appear in the final OpenAPI document with the same name
-
- Closed
-
-
WFWIP-692 MicroProfile OpenAPI and multiple deployments: duplicate server records
-
- Open
-
-
WFWIP-693 MicroProfile OpenAPI and multiple deployments: RequestSchemaBody annotations carrying identical class names generate wrong OpenAPI documentation
-
- Open
-
-
WFWIP-694 MicroProfile OpenAPI and multiple deployments: conflicting @SecurityScheme occurrences generate wrong OpenAPI documentation
-
- Open
-
-
WFWIP-696 MicroProfile OpenAPI and multiple deployments: conflicting root level ".security" definitions appear in the final OpenAPI components element, but not at root level
-
- Open
-
- is incorporated by
-
WFLY-19792 Define and document our support for MicroProfile with multiple deployments
-
- Pull Request Sent
-