toggle quoted messageShow quoted text
Makes sense as long as CDI is not
mandatory for 2.1.
I'm not sure you've heard what I was trying to say about the
importance of keeping the core JAX-RS as neutral as possible, I
see some won't have a problem at all if JAX-RS becomes owned truly
and finally by EE only, I'm not going to keep spending my time any
longer on this argument
On 02/06/17 17:43, Markus KARG wrote:
do not say we have to break everything. I said we should
mandate to _bundle_ CDI if needed. This does not break
anything, it provides additional features.
please remember that JAXB became conditional, which also
means to break things in some cases!
can still support the old annotations to keep old code
running on JAX-RS 2.x, but we should allow to write new
applications using latest technology, and we should push
people into using latest stuff by _deprecating_ old
annotations starting with JAX-RS 3.x.
So lets us just break everything and be
happy, how inspiring...
On 02/06/17 17:29, Markus KARG wrote:
would really love to see everything replaced by CDI which
is duplicated in any Java EE API. If this means that a
JAX-RS implementation has to provide CDI, then we should
add this to the specification as being mandatory. For me,
CDI is such a fundamental API that I even would love to
have it being part of Java SE !
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 :)
02/06/2017 16:27, Guillermo González de Agüero wrote:
Ad @Stereotype - I'd need to check whether we
can easily do that, since it would create a
dependency on javax.enterprise.inject. I don't
understand the remark about that annotation
not being there in the runtime - it will be
there, it has retention runtime (otherwise it
I meant CDI will only be
needed at (JAX-RS implementation) compile time.
Applications won't need it as annotations not
present on the classpath are just erased at
runtime. So people using Spring or wathever
non-CDI framework won't see any difference. Hope
it clearer now?
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
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 compilation).
Not saying that is a deal breaker, it's just something we
need to consider.