Re: encoding of URI's

Jerome Louvel wrote: Hi Marc, This is the intended behavior. For query string, you get auto-decoding using a Form. For other situations (path variables), you can manually use Reference.decode(URI) methods. ah cool, patched my sample with that call and things get decoded allright now,

SSL and Wildcard Certifcates

After having put up a service that uses wildcard certificates for SSL, I've found Java's default of rejecting wildcards very broken. Fortunately, you can fix that by setting the HostnameVerifier on the HttpsURLConnection instance. What this means is that, unfortunately, the java.net

Re: 404 from getRepresentation/handleGet?

On 7/26/07, Adam Taft [EMAIL PROTECTED] wrote: You're asking what's the best practice to use when coding your Resource. Exactly! This approach allows the library to do the automatic content negotiation and call getRepresentation(Variant v) with the appropriate Variant. If you short circuit

RE: failing samples in svn-trunk

Hi Marc, Thanks for finding these issues, I've fixed the NPE and the second issue in SVN. For the java.nio.channels.IllegalBlockingModeException one, I would need more details to reproduce it. Which Restlet version, which HTTP client and server connectors? Best regards, Jerome -Message

Re: How to use JDBC Extension?

On 7/25/07, Jerome Louvel [EMAIL PROTECTED] wrote: Hi Avi, The JDBC extension is mostly useful if you want to manipulate your database through XML representations (XML requests and XML responses). For other use cases, such as supporting Resources as Domain Objects, I would recommend more

RE: 404 from getRepresentation/handleGet?

Hi all, I have quickly read over this thread and like to mention that it can be useful to use content negotiation even for DELETE methods. Indeed, a DELETE method can return an entity. In this case you can manually call Resource.getPreferredRepresentation() to set the Response's entity after

Re: 404 from getRepresentation/handleGet?

Geoffrey Wiseman wrote: This approach allows the library to do the automatic content negotiation and call getRepresentation(Variant v) with the appropriate Variant. If you short circuit this and add in your Representation during construction, basically you miss out on the ability to switch

RE: encoding of URI's

Hi Marc, [...] Just a follow up question: for reading the request params I found: - from the query-string request.getResourceRef().getQueryAsForm(); // optional param charset - from the http body request.getEntityAsForm(); (noticing this last one doesn't have an optional charset param

Re: Trouble setting attributes

Sean Landis wrote: The nature of the data is a clientId and a callId. These are going to be used for governance and should be part of every call in our environment. It seemed to me that since it was not application related, that it ought to be hidden. I'd love to hear about alternatives

Re: encoding of URI's

Jerome Louvel wrote: Hi Marc, [...] Just a follow up question: for reading the request params I found: - from the query-string request.getResourceRef().getQueryAsForm(); // optional param charset - from the http body request.getEntityAsForm(); (noticing this last one doesn't have an

Re: Trouble setting attributes

Based on what you wrote Adam, it sounds like you would agree that using hidden parameters in this case doesn't break REST. Now that I've explained what we are trying to accomplish, can you suggest a more RESTful approach? We are very interested in being as RESTful as possible. Sounds like

Re: SSL and Wildcard Certifcates

On 7/27/07, Jerome Louvel [EMAIL PROTECTED] wrote: Hi Alex, Thanks for teaching me new aspects of SSL :) We have a RFE to improve SSL support in Restlet 1.1, I've updated it to propose the addition of a connector parameter. See details here: