[jax-rs-spec users] [jsr339-experts] Re: MVC

From: Sergey Beryozkin <>
Date: Tue, 3 Jun 2014 11:52:05 +0100

Hi Bill,
On 30/05/14 20:11, Bill Burke wrote:
> On 5/23/2014 4:36 AM, Sergey Beryozkin wrote:
>> Hi
>> On 22/05/14 22:05, Santiago Pericas-Geertsen wrote:
>>> Dear Experts,
>>> As you may have seen in the Java EE 8 survey, there was significant
>>> interest in adding an MVC framework to the platform in EE 8. After
>>> some analysis, we are convinced that the best place for this work is
>>> in In fact, as many of you may recall, this was on our
>>> list for JAX-RS 2.0 but we've never got a chance to discuss it in any
>>> detail.
>>> I'm aware of some discussion in the JSF alias in relation to MVC in
>>> general, and its support as part of JAX-RS in particular. I plan to
>>> send an e-mail to the JSF alias as a way to establish a liaison
>>> between the two groups. I believe their expertise would be of great
>>> value for us and will help us design a framework that addresses the
>>> requirements of the EE community.
>> Look forward to JAX-RS supporting MVC and SSE. As far as the future
>> JAX-RS MVC is concerned, I hope it will not only target EE users though
>> :-). i.e, it would work even if no JSF is available, but of course the
>> input from JSF experts will be of great interest.
>> Using Jersey MVC as a template would be a nice start IMHO, we have a
>> less involved support for it, but I think it is close enough to the way
>> Jersey does it in some cases.
> I am 100% against MVC in JAX-RS. Are we really going to introduce a
> legacy and now defunct pattern to JAX-RS? The trend and future is
> Angular JS or GWT apps with simple RESTful back ends.
I wonder where is that analysis/conclusion coming from, that all of the
Java HTTP services world is now going to use Angular JS only, and adding
GWT into the mix, I've heard some people say GWT is not that cool at all.

> This is wrong guys. You will regret adding and it will end up on the
> long list of Java EE features that nobody uses and bloat we'll have to
> support.
> SSE and now MVC, I'm really disappointed in the direction of JAX-RS.

I think the good framework is inclusive as opposed to exclusive to what
some of us think is the only way forward with respect to building UI
applications. I see a lot of HTML5/JavaScript applications appearing,
yes, but I'm convinced many productions still successfully use and plan
to use MVC.

I don't share your concern that for the group to work on JAX-RS becoming
a choice for people building UI is a bad idea. For example, adding a
light-weight optional support for whatever is cool but also is used
today for building UI would help popularize JAX-RS even more.

Cheers, Sergey