Hi Gunnar, thanks for your response! please see inline. So (and allow me to ask a dumb question, I just need to be extra clear on this) if @ValidateOnExecution(CONSTRUCTORS) is declared on class level

Do we have BeanValidation expert here? ;) Gunnar? I believe the implementation should skip the method validation when @ValidateOnExecution(type = ExecutableType.NONE) is on the method / class. But wha

Hi Christian, seems to be a Jersey bug. Regards, Pavel

JAXB dependency cannot be declared optional, that's a fact. Even if everyone from the EG would be for that, it won't be done. Reasons were already stated on this list. We are not going to say anything

Markus, your description of user definitely doesn't read the spec document, javadocs, etc. So what exactly would be achieved by putting a note into the spec document? My recommendation would be puttin

Well.. the spec says nothing about running on Java 9, since Java 9 won't be final when JAX-RS 2.1 is released. When a user want's to run on Java 9, it is expected that he knows what he's doing (i.e. r

that depends on how the application is ran (on Java 9). If the app is on classpath, the *user* has to --add-module java.xml.bind. Nobody can do that for him. If the app is on module path, there is ano

Hi Markus, we learned that it is not possible to do that in this release. The main issue is that we cannot just deprecate something, there is a strict policy related to making backwards incompatible c

Hi Sergey, I believe that javadoc is the right place for documentation like this. Not to mention that writing the documentation to the annotation string literal is not very convenient, especially when

Hi Sergey, that's true, but does that contradict what we did? (I do see that as a shortcut, which makes sense to have, nothing more). Regards, Pavel

Hi Sebastian, that's easy to write in the spec, the consequences are not so simple to consider and implement. Most of the CDI changes won't be in the API at all - its not about the produced API JAR, t

Dear experts, we are in a stage when we are re-reading spec document and javadoc (you're welcomed to help us - if you have some favorite typo anywhere in JAX-RS and you wan't to get rid of it, now is

Hi Guillermo, I really appreciate your activity around this area, but at this point, I don't think we should consider pursuing any change. We are days from Proposed Final Draft and we still don't have

Please see https://github.com/jax-rs/api/commit/f84db6dbb13801411560368deaac7d0d5004db65 Manifest entry "Automatic-Module-Name" was added (based on http://mail.openjdk.java.net/pipermail/jpms-spec-exp

Dear experts, Thank you for a productive discussion about CDI integration. We now have a good understanding of what can be achieved when using the new CDI 2.0 API. Our recent analysis has concluded th

oops. :) will be fixed in the next milestone. Thanks, Pavel

please see https://github.com/jax-rs/api/commit/d18207327468870ab885120c3790e36a741af26d

Hi Gunnar, I'm sorry to say that, but I don't think that proposal is viable. What if the app (BV layer) knows Locales L1 and L2 and the user (request) asks for L3;q=0.9, L2;q=0.5, L1;q=0.1. In the lat

Hi Guillermo, that certainly is a problem, we do rely on servlet scanning.. Regards, Pavel

Hi Dennis, I can't even if I wanted to - you are not on the OCA page (http://www.oracle.com/technetwork/community/oca-486395.html), so I cannot accept any code contribution from you. I'm still not sur