David,
Thanks for your response. I should have been more clear. I was wondering the
proper way from a service standpoint to return an error.
For example when inheriting from Resource in the server, - if the following code
generates an exception - is it better to return an error via the respons
Hi All,
There's a problem with versions of the org.restlet.ext.jaxrs-1.1 POM
later than 1.1-M4. The version specified for the commons-fileupload
dependency is invalid (@lib-fileupload-version@) and so Maven dependency
resolution fails when building Restlet apps with the JAXRS extension
using M5 or
Hi,
I want to restrict access to the nested directories inside the root
directory but I don't know how to accomplish this. I tried to set
deepaccessible property to false but doesn't work because I'm still
getting access to the directories within the ROOT_DIR.
Here's what I'm trying to do (using
Hi,
This question might have been asked and answered. If so, please excuse. I have
been using Restlet-1.1-SNAPSHOT and the following piece of Code on the Server
Servlet:
protected Component createComponent() {
Component component = null;
// Look for the Component XML configur
Hi Jerome,
I am really excited to read about these plans for RDF integration
into Restlet 1.2 . There is a lot here that could be done, and done
in many different ways. I'd be happy to help out as far as I can.
Perhaps one thing to do would be to meet up and go over some ideas,
and help
Hi Vincent,
We had this discussion a few month ago:
http://thread.gmane.org/gmane.comp.web.services.rest/8046
In short, the conclusion was that a PUT without an entity wasn't
allowed, but a PUT with a "Content-Length: 0" entity was.
Strictly speaking, the query string in the URI is part of t
Thanks alot. I'm able to retrieve descriptions of individual resources
now, when I do a OPTIONS request on the resources URI. The *-targetUri
however doesn't work. I get an empty response. But its okay for me now.
Greetings Ralf
Vincent Ricard schrieb:
Hi Ralf,
Does the WADL extension supp
Hi Stephan
Thanks for your reply and for looking into this.
My expectation was, that path parameters should only be assigned a
single path segment, with the exception of the last path parameter when
the "limited" flag is set to false (but I might be wrong).
Feel free to use my code fragments
Hi,
My application use the PUT methods to update some business objects, but
some of these PUT methods do not expect an entity (the value is a string
passed in the query string). RESTlet returns an HTTP 400 status.
Is it a strict behavior required by the RFC?
I expected the same behavior as the ha
9 matches
Mail list logo