Web API document of an unknown group answers with an error page and logs an error instead of 404
Description
Problem
A request for the Web API document of a group that does not exist, for example /v3/api-docs/Confluence (the groups are jira and confluence, lower case), is answered with the generic error page and logged as ERROR with a stack trace:
OpenApiResourceNotFoundException: No OpenAPI resource found for group: Confluence (QA, 2026-11-17).
springdoc has its own handler that answers 404 for this exception, but the app's global error handler catches it first.
Change
-
The app's error handler answers a Web API document request for an unknown group with 404 and the JSON message "No OpenAPI resource found for group: <group>", without logging it.
-
The YAML document (
/v3/api-docs.yaml/{group}) of an unknown group answers the same 404 JSON message, whatever the Accept header asks for. -
The documents of the
jiraandconfluencegroups are unchanged.
Acceptance criteria
-
/v3/api-docs/<unknown group>answers 404 with the message "No OpenAPI resource found for group: <group>", and nothing is logged as an error. -
/v3/api-docs/jiraand/v3/api-docs/confluenceanswer as before.
Manual tester notes
-
Open
/v3/api-docs/Confluenceon the QA app address in a browser: it shows the message "No OpenAPI resource found for group: Confluence", not an error page with a code. -
Open
/v3/api-docs/confluenceand/v3/api-docs/jira: both documents load as before.