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 JAXRS.next as in really the next phase of
JAX-RS development/improvement, it is a list of improving of what we
already have, except for
"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
Sergey
>
>
> On 6/2/2014 6:58 AM, Marek Potociar wrote:
>> Hi Bill,
>>
>> Now we already do know a few things that you do not like to see in
>> JAX-RS.next. I would however also would like to know what are the
>> things that you would like to see in JAX-RS.next?
>>
>> Cheers,
>> Marek
>>
>> On 30 May 2014, at 21:11, Bill Burke <bburke_at_redhat.com> 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 JAX-RS.next. 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.
>>>
>>> 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.
>>>
>>> --
>>> Bill Burke
>>> JBoss, a division of Red Hat
>>> http://bill.burkecentral.com
>>
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com