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

Hi Christian. Yes, you are right, that's a "typo". Thanks for letting us know :) Regards, Pavel

Hi Pavel, thanks a lot the explanation. I just had a look at the changes and it looks good. One minor thing. One of the new paragraphs state: All application-supplied providers implement interfaces

FYI: Custom providers without @Provider annotation will have priority value javax.ws.rs.Priorities.USER (value 5000). Also, Priority(100) > Prority(500), so provider with

Hey Pavel, I would like to take the opportunity to describe what MVC did to support internationalization which relates to the issue we are discussing here. As MVC builds on top of JAX-RS, this may (or

Hi Sergey, I recall getting a requests for supporting NTLM/Kerberos and maybe one other scheme - something related to ldap.. Regards, Pavel

Hi Pavel While it is indeed the case there are many authentication options against the target, I wonder how many options are there when we are talking about the HTTP proxies ?

selecting a right locale might be problematic. Imagine you have two resource method, one serving orders and the other one items. Items can be returned in different set of languages than orders.

> 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

Hi Sergey, Andy, Dennis, all, it would definitely make sense, but there are always issues when you need to provide credentials. Since JAX-RS client is generally an object, which should

Hi Andy, Pavel Would it make sense to consider extending the security related part of the API a bit ? It already has some methods for setting up HTTPS the portable way.

Hi Pavel, The java properties will specify proxy host/port for the entire JVM. Some of my customers are using JAX-RS clients in hybrid cloud environments where they may need a proxy server to

Hi Andy, Dennis, proxy port and proxy host can be already be defined by java property (http.proxyHost and http.proxyPort). I'm not sure whether we can add proxy auth schemes at this

Yeah, I think that makes sense. So maybe instead of new methods on the Client/ClientBuilder we could add the following properties to Client: public static final String PROXY_HOST_PROPERTY =

Hi, I too would greatly love to see this happening. CDI alignment IMHO should have been -the- major theme of Java EE and unfortunately too few steps have been made towards that goal. Kind

Hi, Time is quickly running out, and I guess what the plans are regarding CDI alignment. There's an open issue [1] labeled as "2.1-candidate" but it seems no work has been done on that yet. Given the

By annotation I mean something like "@UseThisProviderOnlyIfNonIsBuiltIn" attached to an application-provided provider (certainly with a smarter name). It is unrelated to any JIRA issue. I just

Hi Pavel Thanks, sorry, your note re having a working implementation was not of the most major concern :-), I was only trying to imply that well, sometimes we have to be ready

Hi Sergey, please see inline. yes, exactly. I was trying to offer another point of view on that issue, seemed like you are suggesting that the proposal uses @Priority in

Hi Santiago 4. states it well, I agree in the end of the day this is probably the most pragmatic solution Cheers, Sergey