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
Why not making it optional ? As for me, I quite like extension names and
would keep it enabled because it makes uri comprehensives. Examples
http://server/path/resource?media=xml
http://server/path/resource?media=json
http://server/path/resource?media=xls
Easy to guess or try the others for an end
Can someone give me an example on how to use the HttpAmazonS3Helper class?
Thanks in advance,
Matt
--
View this message in context:
http://n2.nabble.com/HttpAmazonS3Helper-tp2609388p2609388.html
Sent from the Restlet Discuss mailing list archive at Nabble.com.
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
Hi Jerome,
Shortly after posting that I realized we had a couple of DNS/reverse proxy
issues. Now that's been sorted it's working fine.
Sorry to have wasted your time,
Matt
Hi Matt,
Are you using some kind of reverse proxy or port mapping/firewall software
in front of your Restlet
Rhett,
I agree on the setAttachment semantics. I'd still like to see
something like the setDefaultAttachment method (e.g. setNoPath
attachment) without using the setAttachments method as it is a lot
simpler to configure. For all other cases the current router works fine.
Another option
Did you read my subsequent e-mail that talked about opening an issue to make
this more robust?
There is currently no standard concurrent map with weak keys, although
MapMaker in Google Collections provides this and much more. An effort to put
something like this into Java 7 is under way, but
Hi Jerome,
Can you please be more specific?? I alerady looked at the below link which
you provided, but I still couldn't understand which part exactly accepts the
request XML.
My request XML would be in following format:
customerinfo
fnameTest/fname
lnameFoo/lname
/customerinfo
On Wed, Apr 8, 2009 at 9:42 AM, Jerome Louvel jerome.lou...@noelios.comwrote:
Hi all,
Beautiful! This new solution is available in SVN trunk.
Thanks Dave for the report and Tim for the clever fix!
You're welcome. ;-)
This fix will do for now, but it could be made more robust. Having
Jerome,
I like the compactness of what you are proposing. My concern is orthogonal
to this, however, and I apologize if I'm making too much of a fuss over this
one point:
Relying exclusively on string values in annotations raises the possibility
of spelling errors that are not detected at
Hi Jerome,
Thanks for the reply. I looked at the below URL already but still I'm not
clear couldn't find it. Can you please be more specific tell me which Java
file which method are you referring to exactly?
What I'm really looking for is something like the below request XML would be
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,
Hi all,
[...]
Some comments against that release:
[...]
I like to add another point: Rename ServerResource#isExists to
isExisting(). isExists hurts me. ;) It would make sense to rename
setExists(boolean) as well.
Best regards,
Lars
--
http://www.semagia.com
Oh, I didn't mean synchronizing the whole map. I
actually didn't mean much beyond suggesting that we brainstorm a way to
use WeakReferences as keys in this particular case. I still don't have
a complete solution in mind.
Another idea: Perhaps we can use a ReentrantReadWrite lock around a
Oops,
sorry Remi, I didn't mean to imply that I'd want to disable the way
TunnelService works, only to imply that perhaps we should call these
strings it uses something else, something that's not mixed up with
filename extensions, and have it in a registry separate from the
Extensions.
This
Hello all,
I'm running JDK 1.6 with Restlet 1.2 and the included FreeMarker all
being served from a Tomcat 6 container. My FreeMarker templates are in
the web content root under the directory freemarker-templates.
I used to cast the context to a ServletContextAdapter before 1.2, and
was able
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
18 matches
Mail list logo
