Hi Marek,
Oh, I got it. My misunderstanding here.
> The problem I see with making @GET optional is that it would significantly break backward compatibility with existing
> JAX-RS 1.x applications, as already described by Bill.
Yep, breaking compatibility out of the box is nasty. What the
programmatic config would allow is, someone who *wants* it, to do it
in their projects in a way that better suits them.
Regards
Guilherme Silveira
Caelum | Ensino e Inovação
http://www.caelum.com.br/
On Fri, Mar 11, 2011 at 2:32 PM, Marek Potociar
<marek.potociar_at_oracle.com> wrote:
> Hi Guilherme,
> this one has nothing to do with how I feel about annotations or convention over configuration approach.
>
> The problem I see with making @GET optional is that it would significantly break backward compatibility with existing
> JAX-RS 1.x applications, as already described by Bill.
>
> Marek
>
> On 03/11/2011 06:00 PM, Guilherme Silveira wrote:
>> Hi Marek, would you change your mind if you didnt have to use the
>> annotation, stick to your way of coding and be backward compatible?
>> Meaning that you would remove 90% of the required annotations. That is
>> what I am trying to offer.
>