Hello,

I thank you all to clear my mind about annotations.
Annotations are probably good to get started with a hello world or minimize
the amount of code you would write. But you lose some compilation checks and
moreover developing further more complex resources will require to
understand how it works (routing/switch logic) and which methods will not be
called because of the use of annotations. If I want to search for resources
class will I have to search for @Resource as well ? How far are we from
annotated Restlets ?

Would it be possible to have ServerResource free of annotation logic and an
AnnotatedServerResource subclass removing the need for isAnnotated ?

Cheers,
Rémi


On Thu, Apr 9, 2009 at 17:47, Rob Heittman <[email protected]>wrote:

> GWT 1.5/1.6 is happy with annotations at compile time ... but if the
> implementation needs to examine them at runtime via reflection, GWT doesn't
> have that capability.  GWT getClass() emulation doesn't have
> getAnnotations() ... or much of anything else.  There's no reflection in the
> Javascript room.
>
> Restlet 1.2's current incarnation is fine with me ... annotations
> optional.  But I agree that the non-annotation and annotation approach
> should use the same vowels and consonants in the same order whenever
> possible  :-)  This helps us bears of very little brain.
>
>
> On Thu, Apr 9, 2009 at 7:06 AM, Tim Peierls <[email protected]> wrote:
>
>> On Thu, Apr 9, 2009 at 4:57 AM, Rob Heittman 
>> <[email protected]>wrote:
>>
>>> ...my only *strong* requirement, that the annotation based solution must
>>> remain a voluntary choice and not the only way to get things done.  It
>>> should remain possible to achieve whatever annotations can achieve in a
>>> non-annotation way.  This allows the basic API outline to work in places
>>> where annotations are not available or work differently enough to cause
>>> friction (pre-1.5 JVM backports, GWT, API ports to other languages, Scala
>>> ...)  It is OK with me if the non-annotation approach requires verbosity or
>>> heavy lifting, it just needs to exist.
>>>
>>
>> Isn't that currently the case with the 1.2 branch? (Does GWT not support
>> annotations yet? I thought it did.)
>>
>> It would be best if the non-annotation approach used the same terminology
>> as the annotations, and I think that's not the case right now.
>>
>> --tim
>>
>
>

------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1625766

Reply via email to