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

Make exceptions part of the specification #248

Open
wwebers opened this issue Mar 16, 2022 · 0 comments
Open

Make exceptions part of the specification #248

wwebers opened this issue Mar 16, 2022 · 0 comments

Comments

@wwebers
Copy link

wwebers commented Mar 16, 2022

In JAX-RS exceptions and error handling is a substantial part of its specification. This enables the handling of exceptions possible on applicationlevel even in cases where exceptions are thrown outside without being forced to bind directly to the implementors exception classes.

This is because every implementor has to throw exceptions being instances of those standard WebApplicationException classes.

This is not the case for Microprofile JWT. If applications like to catch those implementors exceptions (smallrye for example), such applications have to realize a strong binding to exactly those implementors. This could be seen contraproductive to using standards, will say one would like to easily switch vendors/implementors of the Microprofile JWT specification.

Right now one has to to conclude: Microprofile JWT = smallrye

Proposal is going towards going the same route like JAX-RS. Same could be said för the remaining parts of Microprofile.

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

1 participant