Interaction with JAX-RS annotations?
See original GitHub issueHi,
I was wondering if it could be possible either through extending the OASFilter or other fluent builders implementations to interact more with JAX-RS annotations? An example would be defining security schemes with open api annotations and let the filter pick up on @RolesAllowed
annotations set on classes or methods.
BR
David
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Chapter 13 Building RESTful Web Services with JAX-RS
Developers decorate Java programming language class files with JAX-RS annotations to define resources and the actions that can be performed on those resources....
Read more >Developing a JAX-RS RESTful Service - dennis-xlc
Consumes annotation applied to createCustomer() specifies which media type the method is expecting in the message body of the HTTP input request. If...
Read more >Overview of JAX-RS (Part 1) - Medium
Annotations in the JAX-RS API are used to provide meta-data around the web resource. A typical example is to use the @GET annotation...
Read more >RESTful Java with JAX-RS 2.0, 2nd Edition [Book] - O'Reilly
There are a lot of different things JAX-RS annotations can inject. Here is a list of those provided by the specification: @javax.ws.rs.PathParam: This ......
Read more >REST API: JAX-RS vs Spring - Baeldung
Indeed, those annotations help us to abstract the low-level details of the client-server communication. To simplify their implementations, it ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think an annotation scanner hook is an interesting idea but might need to be vendor specific rather than in the spec. Not all impls will process annotations the same way. Although perhaps it could be done in a way that didn’t force a specific impl. In that case it could be pretty cool.
Discussed in Sept 10 hangout and agreed to pursue this in the Smallrye community via issue https://github.com/smallrye/smallrye-open-api/issues/15