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. ;-)