Thanks for this information Rajiv. Waoo, it's a big change from what we've
been reading here and there. I was hoping to be using @Servlet, @GET and so
on in the future. I'll stay tune and check the next draft of the Servlet 3.0
spec.
Thanks,
Antonio
2008/10/8 Rajiv Mordani <rajiv.mordani_at_sun.com>
> Hi Antonio,
> I am the servlet 3.0 spec lead and thought I should respond to this (Paul
> forwarded the question to me).
>
> Initially when we began discussing annotations for servlet 3.0 we thought
> it would be a good idea to reuse some of the annotations
> like GET, POST etc in Servlet 3.0. However based on discussions it seemed
> like the right thing to do was to continue using
> the HttpServlet / Servlet interface / abstract class for the method
> contracts. So we won't be moving the GET, POST etc annotations
> to Common Annotations and this will be reflected in the upcoming public
> review of the spec.
>
> - Rajiv
>
> Hi,
>> I'm reading the servlet 3.0 specification and in the paragraph 8.1 it says
>> :
>>
>
> "There are a few annotations from the JAX-RS specification that are being
>> reused in this specification namely HttpMethod, GET, PUT, POST, DELETE,
>> HEAD. Eventually these annotations would move to the Common Annotations
>> specification (JSR 250) if it is shared between the JAX-RS specification
>> and this specification."
>>
>
> But I can't find anything in the JAX-RS 1.0 spec about that. The Common
>> Annotations spec is only available on the 1.0 version on the JCP website (
>> http://jcp.org/en/jsr/detail?id=250), I can't find the 1.1. Does anybody
>> know if these annotations will end-up in Commons Annotation ?
>>
>
> Thanks,
>> Antonio
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
--
--
Antonio Goncalves (antonio.goncalves_at_gmail.com)
Software architect
Paris JUG leader : www.parisjug.org
Web site : www.antoniogoncalves.org
Blog: jroller.com/agoncal
LinkedIn: www.linkedin.com/in/agoncal