RE: UnsupportedOperationException in DomRepresentation constructor

Hi Mikis, It might help indeed to know which Java SE version you are using and if any specific XML parser is manually configured. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -Message

RE: Re: Good or Bad - MediaType Condition APPLICATION_WWW_FORM

Hi Rick, It really depends on the capabilities of your clients. If they are simple Web browsers, application/x-www-form-urlencoded might be more natural, if they are AJAX applications, JSON or XML might be easier to send and process on the server-side. You could also support both formats if

RE: HttpClient Alternatives

Hi Rob, I agree Rob we should consider direct HttpCore usage. I have added a comment in the related RFE. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org/ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com/

RE: Setting WWW-Authenticate Header with a 401 Response

Hi there, Yes it is possible. Authentication schemes can be dynamically plugged in the engine. But what is wrong with HTTP Basic in your case? Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com

Client HTTP request with proxy

Hi all, I'm looking for a possibility to easily use proxy support for Client HTTP calls with Restlet. The normal approach using System.setProperty(http.proxyHost,proxy); System.setProperty(http.proxyPort,8080); does not work. I already searched this discussion board and came

No CallContext given until now when using client.post() inside a jax-rs method

An exception is thrown when using client.post() inside a jax-rs method Source code: http://pastebin.ca/1420694 without the call, the jax-rs method works fine. when launching the client.post() method from a main no exception is thrown. Stacktrace Using grizzly connector:

Can a filter read entity non-destructively?

To teach myself Restlet, I am trying to port the example bookmarking application from chapter 7 of Richardson and Ruby's RESTful Web Services. In their example, they put before filters on their objects to check if the user whose information is being requested matches the user whose credentials

Re: Weird exception using Spring integration

Hi Stephane, This error means that the entity has already been read by the time your resource starts executing. This might happen in a filter, for example. AFAIK, the SpringBeanRouter (and its various helpers) do not touch the entity. Rhett On May 13, 2009, at 9:17 AM, Stephane Nicoll