Re: RestletServlet: [Restlet] ServerServlet couldn't find the target class

I solved the problem. The line com.adxsearch.core.server.service.rule.FirstStepsApplication was in the web.xml file. After I changed it, it worked in the new location. -- View this message in context: http://restlet-discuss.1400322.n2.nabble.com/RestletServlet-Restlet-ServerServlet-couldn-t-find-

RE: SSL Client, HttpURLConnection, 2.0-RC2, keep-alive not working

Hi Thierry! I still want to use the HttpURLConnection in my application. Version: 2.0.3 Module: org.restlet.ext.net I can not make the keep-alive working. This a big problem, since the performance is massive derading espacially using HTTPS. Below is my testcode. The plain HttpURLConnection is

Re: Child URI's

Nice write up! But one problem I see in this is that it's a bit like IDL and the like in SOAP and other RPC protocols. You end up having to share some kind of interface descriptor (or load/interpret it at runtime) between the server and the client. REST requires a well-documented URI space, as

Re: Child URI's

I'm interested in hearing other answers to this, too, but the first thing that occurs to me about your example is that the recipient of this representation would probably find an absolute URI more useful than a relative one. So at the very least you'd want something like this: String userProje

RestletServlet: [Restlet] ServerServlet couldn't find the target class

I'm trying to use the Java EE Hello World example: http://wiki.restlet.org/docs_2.0/13-restlet/275-restlet/312-restlet.html http://wiki.restlet.org/docs_2.0/13-restlet/275-restlet/312-restlet.html It worked the first time but when I rename the entry class I get the error below. I have a Java EE a

RE: Re: JAX RS + Tomcat (Servlet Container)

Hi Stephan, for now we are trying the following solution: We created an HttpServletRequestWrapper which overrides the method #getInputStream. In this method we read the parameters from request#getParameterMap and return it into an ByteArrayInputStream. We will let you know if it works. Best r

RE: Redirector fails with chunked encoding

Problem solved by using (embedded) Jetty instead of the internal server at the end of the chain. There is something wrong with the handling of chunked encoding by the internal server. The effect of the Redirector and client implementation changes was to change the sizes of the chunks. Mark --

Child URI's

I've a User object with a name and a List of Project objects. When I represent with, for example, a JsonRepresentation, I do jr.put("lastName", user.getLastName()); jr.put("projects", "user/"+user.getId()+"/projects"); return jr; The 'projects" uri construction seems a little naive.