+1 for Santiago's plan including Arjan's ideas, but is it realistic to actually get the spec text in Q1? -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of arjan tijms
Sent: Mittwoch, 30. Januar 2019 17:43
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] Revisiting Roadmap Hi Santiago, Thanks for the update, these sounds great! Indeed, it depends on the legal issues being resolved, but I too have hope it will be done soon indeed. As for JAX-RS 2.3, I'd like to propose including non-disruptive CDI features to that release, for instance the ability to inject the JAX-RS artefacts into class fields using either @Context or @Inject. IMHO that should be a relative simple and well understood change. Hi All, Some months ago we discussed the following roadmap for JAX-RS: Naturally, some of the dates need to be revised. Now that the EE4J work is wrapping up, and with the hope that the legal issues are resolved in the very near future, I think we should revisit this. Here are my current thoughts: [JAX-RS 2.2 - Q1 2019] Main new feature is Bootstrap API. Ideally, this new version should include a new section in the spec document (once received) and one or more TCKs. [JAX-RS 2.3 - Q2 2019] Purpose of this release is the deprecation of @Context. At the time of the release, we should have done the necessary investigation on the desired 3.0 features. [JAX-RS 3.0 - Q4 2019] A non-backward compatible version of JAX-RS that only uses CDI for injection. This version would require significant changes to the docs and TCKs. We need commitment from development teams given the impact on the existing JAX-RS implementations. I’m intentionally leaving out 2.4 and 3.1 as I see them way into the future and not worth discussing at this point. _______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jaxrs-dev
|
