2017-06-20 13:43 GMT+02:00 Pavel Bucek <pavel.bucek@...>: Yes, right. The @VOE given on the class-level could be overridden by @VOE on a specific method, though. Check out the JavaDocs of @VOE

2017-06-20 9:34 GMT+02:00 Pavel Bucek <pavel.bucek@...>: That's right. So if Jersey still is executing the validation in this case, it seems to be a bug. Using this on a method (as opposed to a

Hi Pavel, 2017-06-05 11:07 GMT+02:00 Pavel Bucek <pavel.bucek@...>: The fallback mechanism of the JDK ResourceBundle API will kick in which depends on the relationship between requested locales

Hi Pavel, Any chance for considering the latest proposal for passing the (highest-quality) request locale to Bean Validation? Thanks, --Gunnar 2017-06-02 14:48 GMT+02:00 Pavel Bucek <pavel.bucek@oracl

One option to consider is to add the "Automatic-Module-Name" header to the spec JAR's MANIFEST.MF. This header entry is foreseen by JPMS (some background) to specify a module name, should a non-modula

I see, thanks for clarifying the details, Christian! To me it seems that'd be a very reasonable default behaviour for JAX-RS; people still could plug in a custom LocaleResolver based on their custom r

Hi Christian, This seems very useful, pretty much like what could be useful within JAX-RS itself. That selected Locale could then be used with a specifically set up message interpolator, just as JSF d

> Note that Accept-Language is a list of languages, not a single one Ah, that's a good point, I wasn't aware of that. My feeling is that JAX-RS should select the right Locale (however that would look

Bean Validation spec lead here, thanks a lot for considering this feature! > Since there is no way how to get a list of supported locales Why is it that you need to get the list of locales? The Locale