Alessio, great to have you here! If you don't mind, I will suggest that you will be added as an additional reviewer for all PRs that look like cross-vendor issues. For this reason, can you please tell me your Github account ID? -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Alessio Soldano
Sent: Dienstag, 27. Februar 2018 12:16
To: jaxrs developer discussions
Subject: Re: [jaxrs-dev] Round of Introductions Oh, well, let's add another introduction. I'm Alessio Soldano, I work for Red Hat and currently lead the RESTEasy project. I'm technically also a committer and PMC member of Apache CXF, even if most of my contributions there in the past have been on the JAX-WS side of the project. I'm definitely willing to be involved in the efforts here and contribute to the success of this spec (and its implementations). Cheers Alessio On Sun, Feb 25, 2018 at 12:26 PM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote: John, welcome at JAX-RS! :-) As you are an active CXF committer: There are some discussions running in the issue tracker where "we" (currently Santiago, Christian, me) like to hear an "official" CXF statement. Would you chime in yourself, or can you tell us whom to ask at CXF? Thanks! -Markus I'll also send my introductions at this point as well. I'm John Ament, I'm a committer on Apache CXF, contributor in the past to JBoss RestEasy and have barely even scratched at the Jersey codebase. I also helped bring the Typesafe Rest Client over to MicroProfile, and can speak to how long I've been using that approach (2013) to building client applications. There's lots of little improvements in the JAX-RS realm that I can see going on. One new feature I just brought to CXF was CDI support for all JAX-RS context objects. I see reactive applications growing and growing, but the JAX-RS APIs are still a bit rigid in this area. I hope to see this spec grow. I didn't aim to join as a committer up front, but who knows what the future will bring. John I'd like to introduce myself! I'm a professional computing practitioner who came of age as a young professional in the dot-com boom while I was still in high school. I was an Eclipse contributor back in 2007 when I worked on a VoiceXML designer workspace called the Voice Tools Project. I'm a long-time user of JAX-RS and Jersey. I've been working off and on for about 4 years on the date-parsing infrastructure in Jersey's content-type negotiation. I'd like to complete that project as Jersey is transferred to the Eclipse Foundation. Not being able to port Jersey's history, pull requests & pre-existing github organization to the Eclipse Foundation is an unfortunate side-effect of the shuffle. Hopefully we don't see forks as a result! (Although license changes might make avoiding forks impossible; I don't know.) Like Andy McCright, I think JAX-RS is long overdue for having a proxy client standard, but I'm actually not sure MP Rest Client 1.0 is the right approach. I've been using jersey-proxy-client's WebResourceFactory since Jersey 1.x, and I feel like it honors JAX-RS's Client library better than MP Rest Client does. For example, jersey-proxy-client uses JAX-RS's ClientBuilder more natively by accepting WebTarget objects gotten from a javax.ws.rs.client.Client instance as its basis of operation. I think a serious effort should be put into comparing & contrasting Jersey's WebResourceFactory & MicroProfile's Rest Client. I joined some of the Rest Client discussions early on to ensure Rest Client would support features that WebResourceFactory is currently lacking (and that I maintain private Jersey builds of to improve), so there is some immediate benefit to the industry having Rest Client 1.0 as-is. In the professional Java world of the midwestern United States, I find that JAX-RS has a very slow adoption rate and is still often (stupidly & incompetently) seen as a technology that is too-new. As a result, I've long considered myself a JAX-RS evangelist dedicated to breaking through the sloth, ineptitude & old-and-moldy preferences of the entrenched Java world. _______________________________________________
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
|
