Arjan and Andy, great to have Payara, IBM and Apache in the boat! :-) This allows is us to find really broad cross-vendor agreements, which is definitively a target of mine. Let's see who speaks up here next from Red Hat's RestEasy team. Until then feel free to pull the current sources and set up your build environment. -Markus From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Andy McCright Sent: Sonntag, 18. Februar 2018 03:46 To: jaxrs developer discussions Subject: Re: [jaxrs-dev] Round of Introductions Hi All, My name is Andy McCright, and I am a part of the IBM team that works on WebSphere Liberty and OpenLiberty. I am also a frequent contributor to Apache CXF and the MicroProfile Rest Client projects. I participated in the JAX-RS 2.1 Expert Group, and am excited to be at it again in the Eclipse Foundation. Like Arjan, I'm interested in making security easier for JAX-RS applications. I'd also be interested in moving the MP Rest Client into the JAX-RS spec - it seems like it would fit nicely under the ClientBuilder API. I'm learning more about the MVC spec, and I agree with Christian that we should improve the JAX-RS spec to make it play together nicely. Thanks for getting this thread started - looking forward to working with all of you! On Sat, Feb 17, 2018 at 12:08 PM, Christian Kaltepoth <christian@xxxxxxxxxxxx> wrote: Hi Markus, thanks a lot for the warm welcome. I agree that having separate JSRs for JAX-RS and MVC was the correct decision back then. However, good integration with JAX-RS is a very important success factor for us and therefore I would love to help moving JAX-RS forward. I agree that it may be a bit early to start discussions about issues on GitHub. But I hope that we can get more people on this mailing list soon. I agree with Kevin that it would be a good idea to send some kind of invitation to the old JAX-RS list on groups.io. There are currently about 50 members on this list and it would be great to get them on the new list. Hello Christian, I am very glad to have you in the boat, as I do see MVC API -besides the compliant runtimes and applications- as an important stakeholder for the JAX-RS API! I remember very well when I proposed to split up the JAX-RS EG into one for JAX-RS and one for MVC, and while I still think it was the correct decision back then, sharing contributors is a great thing to get our APIs aligned, indeed. I noticed that you already started some threads in the Github issues tracker, which is great! Please don't mind if discussions will start slowly, as not all committers have access to Github and the mailing list as of today, but day after day more committers do enter, so (hopefully) we have lively discussions rather soon! CU -Markus Hi everyone, I would like to take the opportunity to introduce myself. Even though I'm not (yet) a committer. :-) My name is Christian Kaltepoth. I'm specification lead for JSR 371 (MVC 1.0) and also was in the EG for JSR 380 (Bean Validation 2.0). As MVC 1.0 is built on top of JAX-RS, I'm very interested in JAX-RS's future. As part of my work on MVC 1.0 many JAX-RS related issues came up, which I reported to the JAX-RS EG. Unfortunately most of them are still unresolved and I would love to help getting them fixed. Beside that I'm also using JAX-RS almost daily in my job, so I have quite some experience with the API and know about the good parts and what could be improved. ;-) _______________________________________________ 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
|