On 18.03.2011, at 12:29, Guilherme Silveira wrote:
>> Yet to me, allowing people to completely use their own convention is a non-goal for this spec.
> Understood... thats what I am looking for... the goal of the spec is
> to continue the current work or change the path taken. If it is not
> then it is not, there is nothing someone can do about it.
>
>>> *DRY + CoC should be a main theme across all specs in Java EE 7*
>> I thought it is the Cloud... http://jcp.org/en/jsr/detail?id=342 ;)
> I think what Adam means is that it should, not that it is :) (I've got
> the same point of view).
Thanks! -> what made Java EE 6 so popular were the conventions. They should be just more consistently applied across the specs.
>
> Regards
>
> Guilherme Silveira
> Caelum | Ensino e Inovação
> http://www.caelum.com.br/
>
>
>
> On Fri, Mar 18, 2011 at 7:23 AM, Marek Potociar
> <marek.potociar_at_oracle.com> wrote:
>>
>>
>> On 03/17/2011 10:05 PM, Adam Bien wrote:
>>> IMHO readability of the code is the best without any annotations :-)
>>
>> What I mean by readability should be actually renamed to understandability. :)
>> It means that one can look at the code and directly infer from it what it does, without a broader context or without
>> having to consult additional information sources. Annotations bloat code to certain extent, but at the same time they
>> provide useful additional meta data about the code to make it more understandable.
>>
>>>
>>> Putting the name of the method inside @Path would violate the DRY principle.
>>
>> Not if it is considered just a coincidence, which is also our case.
>>
>>>
>>> *DRY + CoC should be a main theme across all specs in Java EE 7*
>>
>> I thought it is the Cloud... http://jcp.org/en/jsr/detail?id=342 ;)
>>
>> Marek
>>