Unable to find converter for java.util.UUID

Chirayu Desai <chirayu <at> purpledocs.com>
2015-03-16 11:30:43 GMT

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();
sessionAttributes.setAlive(true);
sessionAttributes.setFQUserName(userAtDomain);
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 :
f3d2edda-443c-454d-856a-fb4e7ed9c535*
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/" +

Restelt Client Internal Connector Error (1002)

Chirayu Desai <chirayu <at> purpledocs.com>
2015-03-10 20:04:16 GMT

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(ClientResource.java:1663)
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: http://restlet-discuss.1400322.n2.nabble.com/Restelt-Client-Internal-Connector-Error-1002-tp7579347.html
Sent from the Restlet Discuss mailing list archive at Nabble.com.
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3104395

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

Xybrek <xybrek <at> gmail.com>
2015-01-15 12:27:50 GMT

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?
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3094294

HTTP/1.1 422 Unprocessable Entity - Error

Xybrek <xybrek <at> gmail.com>
2015-01-13 20:42:24 GMT

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?):
<dependency>
<groupId>org.restlet.gae</groupId>
<artifactId>org.restlet.ext.jackson</artifactId>
<version>2.2.0</version>
</dependency>
<dependency>
<groupId>org.restlet.gae</groupId>
<artifactId>org.restlet.ext.json</artifactId>
<version>2.2.1</version>
</dependency>
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?
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3094172

Re: Redirect whole browser traffic to restlet proxy

Xybrek <xybrek <at> gmail.com>
2015-01-03 19:41:49 GMT

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
heroku that runs Restlet proxy and redirects all traffic to a given URL
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=3093682

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.)

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.

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.

Restlet Framework 2.3 RC1 and 2.2.3 released

Jerome Louvel <jlouvel <at> restlet.com>
2014-11-29 07:52:58 GMT

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,