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

From: Bill Burke <>
Date: Tue, 03 Jun 2014 08:59:41 -0400

On 6/3/2014 6:56 AM, Sergey Beryozkin wrote:
> Hi Bill
> On 02/06/14 13:32, Bill Burke wrote:
>> So far I just have little things that I've run into over the past year:
>> * Basic Auth support in the client API
>> * Allow ContainerRequestContext and ContainerResponseContext to be
>> injectable via @Context.
>> * add method for obtaining client IP address to ContainerRequestContext
>> * Injectable ContainerRequestContext allows properties to be viewed/set
>> in JAX-RS methods
>> * Injectable ContainerResponseContext allows Locators to add things like
>> cookies to the response.
>> * Some standard way of doing a forward like in Servlet spec.
>> * Allow filters to be bindable via a @Path expression.
>> * @Context should work directly with application class. i.e. you should
>> be able to inject
>> class MyApplication extends Application {}
>> via
>> @Context MyApplication app;
> All of it is possibly a very good list of improvements but I'm not
> seeing it qualifying for as in really the next phase of
> JAX-RS development/improvement, it is a list of improving of what we
> already have, except for

Why the urge or need to create a Are you bored? Minus some
incremental improvement, JAX-RS is done IMO. There's always this
propensity to "rule the world".

> "Some standard way of doing a forward like in Servlet spec."
> I read it as "support MVC" :-). I'm not 100% sure how Jersey does,
> probably via RequestDispatcher.forward too, but this is how CXF
> 'controls' binding the 'model' to the 'view' handlers

No, it just means i want a way to forward to static resources. Big
difference from creating a full-blown MVC framework.

Bill Burke
JBoss, a division of Red Hat