Chirayu Desai | 16 Mar 12:30 2015

Unable to find converter for java.util.UUID

I am working on a client server application. I was using Restlet 2.0.3. Due
to a heavy load task my client was getting timed-out. I searched on the
forum and found that switching over to Restlet 2.2 would help. So I did
that. I upgraded my Restlet to 2.2.1. But now my code has stopped working at
precisely this method.

*public synchronized UUID generateUniqueSessionId(String userAtDomain)
        UUID newSessionId = UUID.randomUUID();
        SessionAttributes sessionAttributes = new SessionAttributes();
        loggedInUsers.put(newSessionId, sessionAttributes);
        return newSessionId;
So I am returning the UUID at last. This code is on the server and invoked
during login. Following is the error that I am getting from the logs.

*16 Mar 2015 11:23:18 WARN - Unable to find a converter for this object :

And this object referred in the log belongs to java.util.UUID

The code on the client side which invokes the server looks like this.

*public UUID authenticateUser(String username, String passwd) {

        try {
            String url =
RESTLetWebSvcsFactory.getFactoryInstance().getServer_URL() + "login/" +
(Continue reading)

Chirayu Desai | 10 Mar 21:04 2015

Restelt Client Internal Connector Error (1002)

I am using a restlet 2.1 client sever based architecture, my client times out
within 1 minute after sending the request. and I get the following exception
Internal Connector Error (1002) - The calling thread timed out while waiting
for a response to unblock it.
	at org.restlet.resource.ClientResource$1.invoke(
	at com.sun.proxy.$Proxy17.getTaskList(Unknown Source)....

My code is as below :

import org.restlet.resource.ClientResource;

*ClientResource cr = new ClientResource(uri);
MyResource resource= cr.wrap(MyResource .class);
				updateStatus = resource.updateData(Parameter);*

how should I configure my client resource to avoid timeout ?

View this message in context:
Sent from the Restlet Discuss mailing list archive at


Xybrek | 8 Feb 07:49 2015

Restlet cannot process query parameter on ROOT path

I have this code:

 <at> Override
public Restlet createInboundRoot() {

     Router router = new Router(getContext());

     Redirector forward = new Redirector(getContext(), SOME_URL,

     router.attach("/" + "{id}", forward);
     router.attach("/rest/", RootServerResource.class);

     MyFilter myFilter = new MyFilter(getContext());

     return myFilter;

The problem with this code is that Restlet cannot seem to process query 
parameter on ROOT path:


Filter does not trigger.

However, when through the /rest/ part


(Continue reading)

Jerome Louvel | 3 Feb 16:30 2015

Restlet Framework 2.3.1 released

Hi all,

We have just pushed the first maintenance version on the "stable" branch.
Here are the bug fixed:
- Reintroduced registration by default of the internal HTTP server connectors in JEE edition. - FormDataSet not properly serializing text/plain files. Issue #1006. Reported by johnjaylward. - Fixed fileupload extension for GAE and JEE editions. - Fixed potential NPE. Issue #1004. Reported by Philippe Perrault. - Reference scheme reverts to http when using https. Issue #998. Reported by Stephen C. Pope. - Fixed bug that prevented client code to properly consume error responses #1004 and #1018. Reported by Philippe Perrault and spraguep.
Xybrek | 15 Jan 13:27 2015

Is there any concrete example on how to use Restlet File Upload extension with Google App Engine?

Is there any concrete example on how to use Restlet File Upload 
extension with Google App Engine?

There are lots of example for Restlet File Upload but not for the GAE 
edition of Restlet? Is there any complete Upload example to do file 
upload with Restlet?


Xybrek | 14 Jan 01:45 2015

CRUD Operation for Calling ServerResouce with ClientProxy

I have this ServerResource that is called by a ClientProxy:

public class GaeThingServerResource extends SelfInjectingServerResource
         implements ThingResource {
     private static final Logger LOG
             = Logger.getLogger(GaeThingServerResource.class.getName());
      <at> Override
     public ThingItem createThing(ThingItem Thing) {
         return Thing;
      <at> Override
     public ThingItem readThing(Long id) {"Read Thing id=" + id);
         ThingItem result = store().get(ThingItem.class, id);
         return result;
      <at> Override
     public ThingItem updateThing(ThingItem Thing) {"Updating Thing=" + Thing.toString());
         return Thing;
      <at> Override
     public void deleteThing(Long id) {"Delete Thing id=" + id);
         store().delete(ThingItem.class, id);

This is called by:

public interface ThingResourceProxy extends ClientProxy {
      <at> Get
     public void readThing(Long id, Result<ThingItem> callback);
      <at> Delete
     public void deleteThing(Long id, Result<Void> callback);
      <at> Post
     public void createThing(ThingItem thing, Result<ThingItem> callback);
      <at> Put
     public void updateThing(ThingItem thing, Result<ThingItem> callback);
      <at> Get
     public void list(Result<ThingResultItem> callback);

With this code:

                 ThingResourceProxy thingResource = 

thingResource.getClientResource().setReference("/rest/thing/" + id);
                 thingResource.readThing(id, new Result<ThingItem>() {

However readThing method the Long id is always null, when is called, 
what could be the problem?


Xybrek | 13 Jan 21:42 2015

HTTP/1.1 422 Unprocessable Entity - Error

How to fix when GWT ClientProxy resource gets this "HTTP/1.1 422 
Unprocessable Entity" error?

Is it fine to have these two dependency in the project (or just one?):


If this is not the issue what could be the problem that GWT ClientProxy 
is getting this error? The Actual method in the ServerResource doesn't 
seem to get invoked at all, since the LOG would not show. So Where is 
this "HTTP/1.1 422 Unprocessable Entity" being caught if not on the 
actual ServerResource, how to deal with this?


Xybrek | 3 Jan 20:41 2015

Re: Redirect whole browser traffic to restlet proxy

On Tuesday, 07 October, 2014 08:12 PM, Jovan Jovanovic wrote:
> Hi everybody,
> after a lot of tries to build a proxy server I found it really easy using Restlet. Although I have an obvious
issue after setting all the traffic from Chrome to go through my proxy, I get redirection loop (as also the
routed URL is trying to go through proxy). Here is the code that I am using:
>   public static void main(String[] args) throws Exception {
>      Component component = new Component();
>      component.getClients().add(Protocol.HTTP);
>      component.getServers().add(Protocol.HTTP, 8111);
>      Application application = new RestletProxy();   component.getDefaultHost().attachDefault(application);
>          component.start();
>      }
>       <at> Override
>      public Restlet createInboundRoot() {
>        Router router = new Router(getContext());
>        String target = "";
>        Redirector redirector = new  Redirector(getContext(), target);
>        router.attachDefault(redirector);
>        return router;
>      }
> So I am just trying to redirect every single request to google. Is it possible using restlet?
> ------------------------------------------------------

I just want to share that yes it is possible, I have a running proxy in 
heroku that runs Restlet proxy and redirects all traffic to a given URL


Tim Peierls | 19 Dec 20:34 2014

Trouble going from 2.2 to 2.3

The default connectors for various editions have changed between 2.2 and 2.3 (actually between 2.3-RC1 and 2.3.0). JEE edition no longer registers HTTP or HTTPS server helpers; JSE still does.

Assuming this was intentional and not an oversight, the change causes problems for me. For several versions now I've been able to maintain one build that works both as a standalone deployment and when embedded in a WAR for deployment in a production server running Tomcat. I've used the JEE edition because of the dependency on org.restlet.ext.servlet.ServerServlet.

(Why use Tomcat at all? There are better connectors for production purposes. Short answer is that it plays well with AWS Elastic Beanstalk.)

With this latest change, however, the standalone deployment no longer works. I get message: No available server connector supports the required protocols: 'HTTP' Please add the jar of a matching connector to your classpath.

It's because no HttpServerHelper has been registered in these lines for JEE (the "jee" token was added to the #ifndef list only a few days ago). I'd be happy to add the jar of a matching connector if there was one that the JEE edition supported, but the obvious candidates, Jetty and Simple, don't seem to be available for that edition.

I'd be happy to switch to the JSE edition, but then I wouldn't be able to compile against org.restlet.ext.servlet.

There's an existing issue which is vaguely related:

I'm not filing my own issue yet, because I don't see it as a bug, but I'd like advice on what to do here. I'd prefer not to have to make separate builds -- it was a really nice property that I could run the same code and libraries either standalone or deployed as a WAR.

Jerome Louvel | 18 Dec 22:49 2014

Restlet Framework 2.3.0 released!

Hi all,

Check out the details about the new version here!

We also updated the technical documentation on the web site with better styling, a navigation bar in the user guide and more. The Javadocs area will get the update soon as well.


Jerome Louvel | 29 Nov 08:52 2014

Restlet Framework 2.3 RC1 and 2.2.3 released

Hi all,

We have just released version 2.3 RC1 that will soon become our new "stable" version, as well a 2.2.3 that includes several bug fixes including a critical security fix for Directory. Please test and send any feed-back, 2.3.0 is planned for next week!

Recent changes in the 2.3 branch include:
  • support for SPDY via the Jetty 9.2 extension, 
  • automatic serialization of Java exceptions as HTTP error responses on both client-side and server-side via the <at> Status annotation, StatusService and ConverterService,
  • an enhanced APISpark extension including an API introspector for Restlet API/JAX-RS API/Jackson annotations as well as a firewall service with rate limitation (integration with APISpark is optional),
  • compatibility with GWT 2.7,
  • Jackson extension now configured to produce more compact JSON by ignoring null values by default,
  • update HTTP client connectors timeout default value to prevent connections to stay around forever if not consumed,
  • Swagger 1.2 & 2.0, RAML 0.8  support added and improved via dedicated extensions
Changes log for 2.3:

To download those version: