-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
javax.ws.rs.core.Application Marked for Removal, but required #1914
Comments
Yes, I mentioned the issue to @mkouba the other day. @mkouba I know I'm a bit repetitive on the subject but with this removable bean feature, it looks like we need to think about all the possible features of each framework and tweak things for each framework as they might rely on unused beans. It really seems fragile to me and a lot of work for the future. Am I mistaken? I think I fail to see why this feature is so useful because if it's just removing beans that the user explicitly declared, I think it's going to be a Pandora box. Could you explain it once and for all so that I'm fully aware of the why and I don't bother you anymore with this? Thanks! |
In any case, I have opened a (small) PR for this specific issue. |
This issue duplicates #1880. As for the |
@dansiviter Could you pls verify whether this issue is solved by #1924? |
Apologies for slow reply. Yes, looks better in v0.13.3. |
It appears
Application
instances are removed although they have useful contents. E.g. if wanting to use Microprofile@LoginConfig
annotation:Is marked for removal:
Is seems the only way to do this is by using
quarkus.smalllrye-jwt.auth-mechanism
andquarkus.smalllrye-jwt.realm-name
properties.The text was updated successfully, but these errors were encountered: