On 04/07/12 21:07, Marek Potociar wrote:
> Hello experts,
>
> Just to start a discussion:
> The comments around issue http://java.net/jira/browse/JAX_RS_SPEC-165
> brought up an interesting topic of whether or not should we consider
> adopting Java SE 7 APIs in the JAX-RS 2.0.
>
> As indicated in the issue, we could base our Locale - String conversion
> support on a standard JDK API methods. Also there are other places where
> the Java SE 7 features and API could be used to the benefit of our users
> - e.g. we could change some of our classes and interfaces to implement
> AutoCloseable so that the components can be used in a "try with
> resources" code blocks. There may be also other places where Java SE 7
> constructs could be adopted.
>
> For those of you who are more conservative, before you completely
> dismiss the idea, let me remind you that by the time we release JAX-RS
> 2.0, the Java SE 8 will be most likely out and as such Java SE 6 will
> become EOLed (which means no further public SE 6 update releases anymore).
When exactly will JAX-RS 2.0 be released ?
>
> In any case, just a thought... please share yours.
Well, the current CXF trunk is the very first release that does not
support SE 5 and moved to supporting SE 6. I honestly do not think that
the fact that SE 7 offers some Java API improvements justifies the
JAX-RS 2.0 spec blocking CXF or other frameworks that may take their
time for a number of reasons to support 7.0 from implementing the
spec...unless you expect the spec be released by the end of the next
year or so
Cheers, Sergey
>
> Marek