Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: map rfc-7807 problem details to exceptions #248

Closed
t1 opened this issue Jan 23, 2020 · 1 comment
Closed

Suggestion: map rfc-7807 problem details to exceptions #248

t1 opened this issue Jan 23, 2020 · 1 comment

Comments

@t1
Copy link

t1 commented Jan 23, 2020

Maybe the MP Rest Client should try to map problem detail response entities (as specified in RFC-7807) to standard or custom exceptions.

I've suggested this as a new MP standard. It could be better to add it directly to the MP Rest Client spec.

Otherwise, I'd like to have an official means in my ResponseExceptionMapper to find the client API interface to search for annotations or exceptions.

For more details, see this blog.

What do you think?

@Emily-Jiang
Copy link
Member

Similar issues #839 was rejected by Jakarta REST and then [#1150]( #1150 was raised. @jamezp suggested this issue was better off to be addressed on the server side not on the client. It was agreed that we would like to close this issue and let Jakarta REST address it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants