hello again,
On Wednesday 03 December 2008 06:46:39 pm Raif S. Naffah wrote:
hello Mark,
On Wednesday 03 December 2008 09:50:38 am Mark Derricutt wrote:
We used to get LOTS of JVM crashes with Restlet under JDK 6 update 10,
the solution (aka work around) was to add:
hi there,
i've already attached a patch to that issue to handle init-param elements
both in the component and the attach elements.
cheers;
rsn
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=978798
On line 501 in version 1.1.1 of org.restlet.resource.Resource.handleGet(),
there's logic that sets the response status to 404 if the representation is
null and the response status is 200-299. That logic doesn't seem to account
for status 204, which by definition should not contain a message
Profitez de notre offre de prévente sur le plus important fichier BtoB de
France.
Exportez sur votre PC, les coordonnées complètes de 600 000 entreprises avec
leur adresse email
Tarif exceptionnel de 349 euros au lieu de 499 euros.
L'outil ideal pour votre prospection par e-mail, par fax, par
Hello together,
currently I´m fighting with restlet to connect our database resources
via url to the web. I want to run the service in the tomcat container.
Without tomcat I can use the apache httpclient to connect to a url. In
tomcat the same code does not work anymore. I don´t know what
A better solution than overriding handleGet is probably returning
Representation.createEmpty() instead of null for 204 responses.
That works fine, though it does seem like null should be an appropriate
response too.
--
Hello Thilo,
it seems you are mixing the httpclient extension of Restlet 1.1 and the
api of Restlet 1.0...
Could you check that you get the right java archives?
Best regards,
Thierry Boileau
--
Restlet ~ Core developer ~ http://www.restlet.org
Noelios Technologies ~ Co-founder ~
At this point in the tutorial:
http://www.restlet.org/documentation/1.0/firstResource#part07
where it says:
This client application must be run as a standalone Java application using a
couple of JARs:
* org.restlet.jar
* com.noelios.restlet.jar
*
Hi all,
A few days ago, Tigris.org completed a major upgrade on their open source
hosting platform, where the Restlet project partly lives.
As a result, some settings where changed in the mailing lists, potentially
affecting some of you. I have just done some adjustments
to the configuration
Hi Raif,
Thanks for the updates. I'm glad you found a solution!
The conclusion, there is an integration issue between Tomcat 6.0, JDK 6 and
Restlet 1.1... We need to have a look as it might be a
common scenario.
Do you have some reproducible code (ideally a WAR with source would be perfect)
Hi Ryan,
This sounds like a bug to me. I have made the following change in SVN branch
1.1 and trunk:
if ((getResponse().getStatus() == null)
|| (getResponse().getStatus().isSuccess()
!Status.SUCCESS_NO_CONTENT
That works great.
Thanks for the fast response!
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=979124
hello Jerome,
On Thursday 04 December 2008 05:23:13 am Jerome Louvel wrote:
Hi Raif,
Thanks for the updates. I'm glad you found a solution!
The conclusion, there is an integration issue between Tomcat 6.0, JDK 6
and Restlet 1.1... We need to have a look as it might be a common
scenario.
13 matches
Mail list logo