Hi experts,
Currently, ParamConverters must currently be activated by a
ParamConverterProvider -- which can be registered via @Provider and
which returnes the programatically chosen ParamConverter.
However, what were the considerations of not making ParamConverters
configurable directly by annotating them with @Provider (and treat the
ParamConverterProvider as 'legacy' or only needed for more sophisticated
type selection solutions)? The corresponding paramConverter would then
be selected automatically by the JAX-RS runtime by the matching type.
IMO it would be helpful to reduce boilerplate code.
Let me know, if you need an example. WDYT?
Cheers,
Sebastian