mcgilman opened a new pull request, #11250: URL: https://github.com/apache/nifi/pull/11250
…n is thrown during a web request it doesn't fall through to the ThrowableMapper. # Summary [NIFI-15940](https://issues.apache.org/jira/browse/NIFI-15940) Adds a dedicated JAX-RS `ExceptionMapper` for `ConnectorConfigurationProviderException` so failures originating from a `ConnectorConfigurationProvider` no longer fall through to the generic `ThrowableMapper`. Previously, any exception raised by a provider implementation (during configuration load, save, discard, delete, asset management, etc.) was caught by `ThrowableMapper` and translated into a `500 Internal Server Error` with a canned "An unexpected error has occurred…" body. This obscured the provider's own diagnostic message and prevented clients from surfacing the underlying cause to the user. With this change, `ConnectorConfigurationProviderException` is mapped to `500 Internal Server Error` with the provider-supplied message returned in the `text/plain` response body. The framework cannot classify the failure further without coupling to a specific provider implementation, so a generic 5xx status is appropriate while still preserving the original message for callers to display. This mirrors the precedent set by `AdministrationExceptionMapper`, which handles analogous failures from pluggable framework subsystems. ### Changes - New `ConnectorConfigurationProviderExceptionMapper` in `nifi-web-api`, registered in `NiFiWebApiResourceConfig` alongside the other framework exception mappers. - The mapper logs the exception at `WARN` and returns the exception message verbatim in the response body so clients can render it directly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
