2.1.2 not working on Windows XP

[petemadsen]

Restlet 2.1.2 (e.g. HelloServer and HelloClient) is not running Windows XP. My real app is working with no problems on 7 and Vista, but not on XP.

The server starts, the ports are listening. The clients seems to connect but nothing happens, it simply hangs.

If I close the server, the clients shows errors.

2.1.1 is running like a charm.

[jlouvel]

Are you using the default HTTP server in org.restlet.jar? If so you can work around the issue but adding the Simple or Jetty extension in the classpath.

[petemadsen]

Yes, the default. I ll stick to 2.1.1 for now but will try simple/jetty extension.

[petemadsen]

Finally found some time to give it a try. Yes, using the Simple extention in the classpath works on XP.

[thboileau]

The current internal connector is not fully stabilized yet, we prefer tell you to use either the Simple of Jetty extensions which are fully approved for production.
We will close this issue.

[lxy4java]

now i use the restlet 2.1.4, i meet the same question ,how can i get the Simple or Jetty extensions
i can't find it in the lib

[jlouvel]

You need to download the Java SE edition of Restlet.

[lxy4java]

i download the java EE

google find the Simple extensions (org.restlet.ext.simple 2.1.4)

and i got this
java.lang.NoClassDefFoundError: org/simpleframework/http/core/Container

[lxy4java]

thanks
i got it

[Zzirconium]

Thanks for this thread, it solves the problem I had (using Simple HTTP Server). Jérôme, Thierry, don't you think this piece of information should appear in http://restlet.org as a prerequisite, or a side note to the "First Server" entry in the user guide ? Amazing job all anyway !

[jlouvel]

@Zzirconium Thanks for your feed-back.

Have you tried RF 2.1.7? The default HTTP server shouldn't have this issue anymore, thus not requiring usage of the extension connectors (Jetty or Simple)?

It would be great if you could let us know.

[Zzirconium]

Since I was running under 2.1.6, my first reaction yesterday was to try with the newer version. And I still had the same trouble : server starts, and when attempting to connect using a browser, nothing happens although some connection exists since the browser keeps waiting for an answer. I will give a new try next week for I might have made a mistake swatching jar file, and i'll confirm