| Re: [jaxrs-dev] Guidance for adoption of Reactive APIs |
James, thank you for sharing this information! Please note that the EF's policy with EE4J (according to Mike Milinkovic) is to look at the existing production code and then wrap an API around that; in particular we shall not invent APIs upfront and the demand vendors to add them into the products ("code first approach" vs. "spec first approach"). So if RESTeasy, CXF, Jersey, etc. ALL agree to support a feature, we may then define an API around it -- but not the other way around. -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of James Roper Hi all, I just wanted to bring to everyones attention a document that we're creating in MicroProfile for guidance in adopting reactive APIs. I understand that JAX-RS 2.1 already has some support for CompletionStage, and that future releases are likely to include support for Reactive Streams (indeed some implementations already do support it). Although JAX-RS technically isn't under the MicroProfile banner, this document will hopefully be used at least for inspiration, if not adopted in some form, in Jakarta EE. It would be great if some JAX-RS people could review it and comment accordingly. Cheers, James |