[mailto:tal.li...@threecrickets.com]
Envoyé : dimanche 12 avril 2009 22:08
À : discuss@restlet.tigris.org
Objet : Re: Annotations and Restlet's future
Hi Jerome,
How about instead of calling setAnnotated(false), there would be an
annotation to turn annotation on? Since this doesn't seem like behavior
ies ~ Co-founder~ http://www.noelios.com
De: Rmi
Dewitte [mailto:remidewi...@gmail.com]
Envoy: vendredi 10 avril 2009 08:58
: discuss@restlet.tigris.org
Objet: Re: Annotations and Restlet's future
Hello,
I thank you all to clear my mind about annotations.
Annotations are probabl
Hi Daid,
(It turns out the JAX-RS spec is unusually short and comprehensible,
which is unusual for these enterprisey specs. The downside is that
it's short partly because they left out a little too much, and JAX-RS
is essentially not a stand-alone technology, you pretty much need some
sort
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
://www.restlet.org/
http://www.restlet.org
Noelios Technologies ~ Co-founder ~ http://www.noelios.com
http://www.noelios.com
_
De : Rémi Dewitte [mailto:remidewi...@gmail.com]
Envoyé : vendredi 10 avril 2009 08:58
À : discuss@restlet.tigris.org
Objet : Re: Annotations and Restlet's future
Good treatment, Dave, not too long :-)
I do agree with your thoughts generally ... except to harp on 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
On Wed, Apr 8, 2009 at 8:15 PM, Rob Heittman rob.heitt...@solertium.comwrote:
Or, to solve the confusion, it may be as simple as modulating the
annotation names. I don't know: @ResourceGets(form) instead of
@Get(form) or such. This would make clear that it's a Restlet thing and
not an
On Thu, Apr 9, 2009 at 4:57 AM, Rob Heittman rob.heitt...@solertium.comwrote:
...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
It
seems like I'm the only one here working with non-annotated
ServerResources right now, so I'd chime in and add that you actually
need to override more than method for each REST method as it stands.
There's get(), get(variant), post(entity), post(entity, variant),
put(entity), put(entity,
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
I can see that Jérôme has already answered a great deal of my questions in
this thread :)
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1596334
Rémi
2009/4/8 Rémi Dewitte r...@gide.net
Hello,
I struggle to get convinced to the use of annotations for resources from
Hello,
I struggle to get convinced to the use of annotations for resources from all
I can read from various threads.
I have the feeling to lose most of the reasons to use Java. MediaTypes are
strings, I find the implementation a bit tricky with reflection forced to be
cached to be fast,
Hi Rémi,
Will annotations in restlet the advertised way of creating restlet
application ?
I moved to Restlet 1.2 M2/snapshot without using annotations. I found
no reason why these annotations will help me. Everything works fine
without annotations and I think/hope Restlet won't force us to use
I would agree with that as a guide (and I think it is what Jerome has in
mind) ... the annotations are nice for people who like them. It seems
Jerome is striving for something very terse that supplants boilerplate in a
number of common cases, which I can see is a nice goal. But if annotations
Jerome was on the JSR 311 expert group but Restlet doesn't support it?
--Erik
2009/4/8 Rémi Dewitte r...@gide.net
I can see that Jérôme has already answered a great deal of my questions in
this thread :)
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=1596334
Rémi
JAX-RS = JSR 311. JAX-RS is available as a Restlet extension.
I'll point out one elephant in the room, though: the JAX-RS extension has
not yet received the same level of attention as other Restlet extensions
that were developed by the core Noelios team. Even the Restlet-GWT
extension I lead was
+1 I.e., what Rob said.
Take care,
John
On Apr 8, 2009, at 17:15 , Rob Heittman wrote:
JAX-RS = JSR 311. JAX-RS is available as a Restlet extension.
I'll point out one elephant in the room, though: the JAX-RS
extension has not yet received the same level of attention as other
Restlet
Nicely
put, Rob.
I
have to agree in the general sense. I'd even add that annotations are
one of the most abused features in Java, and I often regret their
introduction into the language. For every problem solved elegantly with
an annotation, you'd find ten solutions made worse. Sometimes, I
Hi All-
Well, I almost can't believe I'm saying this, but I'd like to weigh in
on the side of considering Annotation-based approaches to writing
resources in Restlet. (Although I'm not so sure about Jerome's
current plan.)
I've mostly disliked, and sometimes despised, the use of Annotations
in
19 matches
Mail list logo
