Josiah Noel
Josiah Noel
Each controller is indeed a http feature, with each route within the controller registered in order of appearance. Filters are technically categorized as a route as well so you can...
Weight of regular controller routes rarely matter, as filters always go before routes even if registered after
> Perhaps we are over thinking it in that the simplest approach is to Closing unless more details are added for why the above wouldn't work
EDIT: [moved](https://github.com/avaje/avaje-config/pull/176#issuecomment-2445226938)
I also don't like jedis
You should be able to make it work with toolchain
The way I've done it with other libs I've worked was to have an extensible [Validator](https://github.com/avaje/avaje-http/blob/master/http-api/src/main/java/io/avaje/http/api/Validator.java) interface which clients can extend to provide custom validation. Example [hibernate impl](https://github.com/avaje/avaje-http/blob/master/http-hibernate-validator/src/main/java/io/avaje/http/hibernate/validator/BeanValidator.java) and [avaje...
> Is it a trade-off of a reflection-free solution Jakarta validation is mainly reflection-based so we couldn't fully implement its interfaces. Hence why we took a page from spring in...
You're going to have to take that up with the JDK, nothing we can really do about it because we have to generate the jsonb components in the last round....
You can open the generated code and see, it's a registry of all the generated adapters. This class is loaded for the library to actually register the adapters to the...