Hello Ben,
that's very surprising. I personnally work on a GWT project for a customer.
We handle quite big objects and the GWT serialisation/deserialisation is not
a problem.
In order to see what happens, did you try with a classic HTTP client, such
as curl, or a clientResource (from the jse
Hello Steve,
welcome on the restlet list!
From what I see in the dependencies, the jackson extension relies on the
release 1.4.3 of the Jackson library. These jars are delivered by the Restlet
edition.
But, you point a good question, we certainly need to support the last release
of Jackson.
Hello Steve,
I've made some tests with the 1.7.1 release of Jackson library in conjunction
with the current trunk of the Restlet framework and it works well for me. I
notice also that in both current trunk and 2.0 branch of Restlet, this line of
code (pointed by the exception message)
Hello, thank's for the quick answer !
I tried with IE, FF and Chrome. The result is the same.
I profiled the client with the Chrome plugin Speed Tracer : I thought there was
no ambiguity. But I had a doubt because chrome is working strangely on my pc.
I then created a simple restlet client in
Hello Ben,
How many objects are listed in the Operations structure? Could you perhaps
send a sample test case?
Best regards,
Thierry Boileau
Hello, thank's for the quick answer !
I tried with IE, FF and Chrome. The result is the same.
I profiled the client with the Chrome plugin Speed Tracer
We are having the same problem.
Did anyone do this? Is there an example that can be looked at?
Cheers!
Nirav
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Threads-never-close-for-ClientResource-tp5164847p5944757.html
Sent from the Restlet Discuss mailing list
I don't have the solution on-hand, but I had to supply connections to each
client resource and manually close those connections.
Thanks,
- TK
... and they stirred up the Nazirites who had completed their days and they
cried aloud to Heaven, saying, What shall we do with these? Where shall we
Hi,
I am using Restlet 1.1m3 release in my application.My application is deployed
on tomcat server. Currently it is deployed on IPV6 linux machine and running
fine. but now i need to bring up my application in IPV6 environment, but iam
getting follwoing error message in tomcat
Hello,
I am trying to create a RESTful application Server.
I am going to use the RestLet framework.
As i am designing the URL's i have some questions.
This app server is going to be the backend for an iPhone app.
The app will require authentication
So here is where i get a little confused with
hi all,
I am interested in your thoughts on implementing mongodb inside a standard
jse restlet app. My current implementation uses a context attribute to
store the reference to the mongo connection pool but was interested in any
other ideas.
my implementation uses restlets 2.0.4 and is slated
I have been developing regularly using Restlet (via Prudence for
JavaScript) and MongoDB for a while, and strongly recommend it.
Check out the MongoVision project as an example. The server-side code is
ridiculously simple:
http://code.google.com/p/mongo-vision/
(For web development, the
11 matches
Mail list logo