Hi all,
I've added a new method on Series: getValuesArray(String name):String[].
There is already a getValues(String name):String method so I had to prepend
the 'Array' suffix. Code checked in SVN trunk.
Paul, the Series class address the lack of a structure maintaining a list of
named entries.
Hi Dan,
In order to help you, I'd like to understand what you want to achieve. I'm
not familiar with Mule so any link to an architecture diagram would help.
Do you want to leverage the Mule infrastructure from the Restlet API, just
for client connectors or something else?
Best regards,
Jerome
Hi Kevin,
Why not, but what would be the use case for making such a request? If a
client application isn't interested in the entity, it can always issue a
HEAD request.
Best regards,
Jerome
-Message d'origine-
De : Kevin Conaway [mailto:[EMAIL PROTECTED]
Envoyé : samedi 22 mars
Hot off the presses:
http://mule.mulesource.org/display/RESTLET/User%27s+Guide
Basically I would like this code:
Engine engine = new Engine(false);
engine.getRegisteredClients().add(new MuleClientHelper());
Engine.setInstance(engine);
Client client = new Client(Protocol.HTTP);
to be like
Jerome, I think you misunderstood me. I was suggesting it might be useful
to allow the client to tell Restlet to read and store the response entity to
be consumed later.
If the response entity is read right away and stored, there would be no need
to keep the connection open and the entire
What is the appropriate way to report an error back to the caller of a
HTTP REST call from a Resource class?
For example, what if I'm using JSON and there is some kind of JSON
parsing error? Obviously, it would be nice to return a useful error
message to the caller of the API.
I'd really
Maybe I've just found the answer to my own question - is it something like this:
public Representation getRepresentation(Variant variant) {
snip...
} catch (JSONException e) {
log.error(Error constructing JSON response while returning a user, e);
You should set the HTTP status code to an appropriate value, in the
400 or 500 range, via getResponse().setStatus(). See
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10. For
your example, 401 Bad Request would be appropriate.
You can also return a representation that may return
That is a perfectly good way to do it.
.. Adam
On Sun, Mar 23, 2008 at 7:12 PM, Ian Clarke [EMAIL PROTECTED] wrote:
Maybe I've just found the answer to my own question - is it something like
this:
public Representation getRepresentation(Variant variant) {
snip...
} catch
When is it appropriate to use a query string to pass parameters to a
REST API call?
For example, why is:
http://blah/user/1234
better than:
http://blah/user?id=1234
?
I'm guessing that if I have a GET request which can return a list of a
variable length (such as a search), then a GET
Jerome Louvel wrote:
I've added a new method on Series: getValuesArray(String name):String[].
There is already a getValues(String name):String method so I had to prepend
the 'Array' suffix. Code checked in SVN trunk.
Fab! Thanks for that. I know that many people don't make use of the
11 matches
Mail list logo
