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) {
         LOG.info("Read Thing id=" + id);
         ThingItem result = store().get(ThingItem.class, id);
         return result;
      <at> Override
     public ThingItem updateThing(ThingItem Thing) {
         LOG.info("Updating Thing=" + Thing.toString());
         return Thing;
      <at> Override
     public void deleteThing(Long id) {
         LOG.info("Delete Thing id=" + id);
         store().delete(ThingItem.class, id);

(Continue reading)

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 = "http://www.google.com";
>        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?
> ------------------------------------------------------
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3089543

I just want to share that yes it is possible, I have a running proxy in 
(Continue reading)

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:
Koen Maes | 20 Nov 15:18 2014

"segment" router or subrouter


My Restlet application is now mapped in the web.xml to "/app" and "/app/*". I have a whole bunch of routes
setup underneath this base URL in a function called setupApp(router).

Now, I plan to refactor things a bit and I want to change my web.xml so *every* call is intercepted by Restlet
so "/*".

The existing routings like "/app/user/{userId}" must keep on working.

**Now I can manually add the first segment "app" to my existing routings so they keep on working. **

But there must be an easier way to do this. I expect something like this to work :

public synchronized Restlet createInboundRoot() {

  Router router = new Router(this.getContext());

  Router subRouter = new Router(this.getContext());
  router.add("/app/*", subRouter);

  // add new stuff to the router
  router.add("index.html", IndexRouter.class);


// existing code but now with first segment /app added ?
// in the original code, the main router is passed in
public void setupApp(Router subRouter) {

  subRouter.add("/user/{userId}", UserResource.class);
  subRouter.add("/user/{userId}", UserResource.class);


thx for the pointers ...



Jerome Louvel | 19 Nov 00:54 2014

New Restlet web site and framework logo

Hi all,

We just released our brand new Restlet web site this morning, with a new visual identity and consolidating all our products, Restlet Framework, APISpark (GA today) and the Restlet Studio (preview) in one place: http://restlet.com

Here is also the new logo:

Note that some technical resources on the framework haven't been fully migrated yet, but no worry we are actively working on them as I write. Thanks for your patience and do not hesitate to report issue if they are not fixed by the end of this week.

We are also completing version 2.3 of the framework including some great contributions such as support for Swagger 1.2/2.0, RAML 0.8, Jetty 9.2 (client-side and SPDY), firewall with rate-limitation and more.

Stay tuned!
santosh pathak | 10 Nov 21:43 2014

issues with setting Timeouts in Restlet

hi,In one of my project,I am new to restlet. 
I am using 1.1.5 version and using it for consuming a REST web service. 

I tried creating a client and tried setting the socket and connect Timeout in the context

Client client = new
Client(Protocol.HTTPclient.getContext().getParameters().add("readTimeout","some value");
client.getContext().getParameters().add("socketTimeout","some value"));

None of the values that I set in context is recognized by restlet , I still see my thread waiting for response
from back-end for endless time. 

What are the right context paramteres, that are needed for connection timeout and socket timeout?
Appreciate help..


Rob Elsner | 23 Oct 19:41 2014

Feeling stupid - client connection gets closed early when relaying from network

We are trying to relay a FileRepresentation, and downloading directly from the Restlet server works fine. 
I can do a manual cURL/wget and retrieve the whole file correctly.

However, when relaying the input stream through a Servlet it seems like the client socket is being reset.

			Representation rep = myClient.get(MediaType.APPLICATION_OCTET_STREAM);

			response.setHeader("Content-Disposition", "attachement; filename=\"" + fileName + "\"");
			outStream = response.getOutputStream();
			inStream = rep.getStream();
			byte[] buffer = new byte[65535000];
			int read = inStream.read(buffer, 0, 65535);
			while (read != -1)
				outStream.write(buffer, 0, read);
				read = inStream.read(buffer, 0, 65535);

What we end up seeing on the server:

Caused by: java.nio.channels.ClosedChannelException
	at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:135)
	at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:326)
	at org.simpleframework.transport.Appender.write(Appender.java:343)
	at org.simpleframework.transport.Appender.write(Appender.java:322)
	at org.simpleframework.transport.Appender.write(Appender.java:297)

And I'm not sure what's going wrong with our client where the socket connection to the Restlet server is
being prematurely closed before the entire file has been transmitted.

Does anyone have any hints or suggestions?