toggle quoted messageShow quoted text
IMHO it would be a deal breaker, please
do not make strong deps on CDI in JAX-RS API.
It will affect non-EE and non-CDI RI, CXF, RestEasy users who will
get annoyed and move elsewhere and it is in our interests to
ensure it does not happen.
Lets do the best CDI integration ever but avoid losing the
'independence' of the core JAX-RS API.
On 02/06/17 16:32, Pavel Bucek wrote:
consider this as a subthread :)
On 02/06/2017 16:27, Guillermo González de Agüero wrote:
To be absolutely honest, I'd expect CNFE or something like that. I
already wrote a test, which corresponds to what you wrote ;) So
thanks for that info, I wasn't aware of this behavior.
There is a little (forward) issue with this - similarly to any
other "optional" dependency, there will be issues with this when
Java 9 modules are used. Once the dependency on CDI API is
declared in JAX-RS API module-info, CDI API will be required on
the module path of any JAX-RS enabled app/code (at least for
Not saying that is a deal breaker, it's just something we need to