Dmitry, great to hear from you! (1) I know; mainly was targeting other vendors. In fact, I'm currently waiting for Jan's approval of the PR I filed against Jersey to merge the first large JAX-RS 2.2 API change into the Jersey code base. (2) If just somebody could tell us *what detail* both sides cannot agree upon, we possibly could provide proposals for consensus. (3) Glad to read that. In fact I hoped that vendors would share some vision about *what* and *when*. :-) -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Kornilov
Sent: Mittwoch, 29. August 2018 17:38
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] Vendor commitments
1) Vendor involvement is important. Agree. Markus, I am suggesting you talking with Jan Supol from Jersey. We may consider working on some early JAX-RS API 2.2 support.
2) We (the community) either need to continue to press Oracle to release the spec doc and TCK - and find a suitable workaround. This is an agreement between Oracle and Eclipse Foundation. It’s not only Oracle responsibility. You should understand it and apply pressure on both sides (if you want to).
3) IBM is invested in the success of JAX-RS and Jakarta EE.
This is really disappointing. IIUC then IBM will never implement any of the features we agreed upon if Oracle and the EF never find an agreement? That is very sad to hear, because what users actually expect from vendors is working features, neither certificates of compliance, nor spec documents (in reality the latter are only really essential for vendors to enable marketing, as we simply could cross-check our products with very small effort, if we just would like to). So if we would rename JAX-RS and use a different package name, then IBM will be out of the boat? Good to know for people right now choosing their product! That's what your posting reads like, at least to me. And waiting six months after 2.2 may sound like a bad joke given the EF's four-releases-per-year cadence and the fact that it took me just few weeks (as an external contributor) to add Java SE Bootstrap to Jersey. So I hope I simply have completely misunderstood your posting! I would love to see an answer of yours convincing me that I failed with my interpretation! :-) -Markus I completely agree that the success of JAX-RS (and Jakarta EE) depends on the rapid (but still high quality, performant, etc.) implementation of multiple vendors. Where I am stuck is that we still don’t have a spec document or a TCK to confirm that an implementation is compatible with the spec. Since JAX-RS 2.1.1 (Jakarta) is supposed to be compatible with JAX-RS 2.1 (Oracle) most vendors could probably claim that they have a compatible implementation already - IMO that would violate the spirit of the open source community because only vendors who paid Oracle for the rights to the EE CTS could truly claim compliance. And there would not be any way for users or third parties to verify compatibility. That said, my hope (I cannot commit) is that Liberty (Open and the commercial WebSphere Liberty) would release a compatible implementation within 6 months of the spec release - ideally sooner. In the past we have released betas that are mostly compatible earlier - I would expect that we’d do the same thing for JAX-RS 2.2 and beyond. Dear JAX-RS Vendors, now that JAX-RS 2.1.1 soon will be published, we need to look ahead on the upcoming release 2.2 and on the releases of your products. With your kind approval we already added the first feature to JAX-RS 2.2, and more will come. To make the JAX-RS project a success, there must be implementations, as we provide only an API. As many people "out there" are waiting to actually use our new stuff, you can imagine that many are waiting for a time frame for "their" favorite implementing product, not just for the API. Hence I think it is a good time for some commitment. I'd like to kindly ask all vendors to commit to our agreed schedule (at least 2.1.1 and 2.2) and tell the public here, which release of their product will support which version of JAX-RS 2.1.1 / 2.2, and when people can actually hold it in their hands. Thanks a lot! -Markus _______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev
_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev |
