server/services.
On Fri, Sep 26, 2014 at 3:33 PM, Audumbar Pujari audumbarpuj...@gmail.com
wrote:
Scenario :
-
I have implemented simple restlet server.
-
One client(RestClient / wget) or more than one client sending
GET/POST requests to server at same time. (eg: wget
Scenario :
-
I have implemented simple restlet server.
-
One client(RestClient / wget) or more than one client sending GET/POST
requests to server at same time. (eg: wget http://mymachine.com:8182)
Expected Behavior :
- Server needs to handle all requests concurrently
at 3:33 PM, Audumbar Pujari audumbarpuj...@gmail.com
wrote:
Scenario :
-
I have implemented simple restlet server.
-
One client(RestClient / wget) or more than one client sending GET/POST
requests to server at same time. (eg: wget http://mymachine.com:8182)
Expected
Hi,
I'm trying to upload an image to my Restlet server.
The server keep returning Unsupported media type (415).
Some details:
My request:
POST myURL HTTP/1.1
Host: localhost:8008
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101
Firefox/19.0
Accept: */*
Accept-Language: he
Found the problem :)
I changed the signature of the annotated method in
my server resource to
@Post
public void setLogo(Representation toSet)
was initially:
@Post
public void setLogo(byte[] toSet)
Is there anyway to use concrete types in the declaration or I need to manually
convert the data
Hello Noam,
I'm currently using the net client connector for customer in production
environment. Using the HttpClient extension is fine also.
Best regards,
Thierry Boileau
Thanks for your reply Jerome!
It is working fine on SunOS with the org.restlet.ext.net connector!
I will also test
Thanks for your reply Jerome!
It is working fine on SunOS with the org.restlet.ext.net connector!
I will also test with the httpclient connector. Is this connector recommended
for production?
Thanks again!
--
if this helps!
Jerome
-Message d'origine-
De : Noam Krendel [mailto:nkren...@yahoo.com]
Envoyé : lundi 15 octobre 2012 20:48
À : discuss@restlet.tigris.org
Objet : Restlet client hanging when connecting to Restlet server (SunOS)
I am using Restlet 2.1.0 with the xstream and jettison extensions
I am using Restlet 2.1.0 with the xstream and jettison extensions. In my JUnit
test I create a simple server:
@BeforeClass
public static void setUpBeforeClass() throws Exception {
server = new Server(Protocol.HTTP, SERVER_PORT, TestServerResource.class);
Context ctx = new
Hello Jon,
from what I notice, this is due to the fact that the entity is not
consumed. I've just reproduced it using this code:
ClientResource cr = new
ClientResource(http://www.example.com;);
for (int i = 0; i 20; i++) {
System.out.println(i);
cr.get();
Thierry,
I have come up with a fix that solves the issue for us... but I don't know if
it is the best/right solution. It doesn't seem to be the right way to handle
it.
I'm using the 2.0.11 source.
In HttpMethodCall.sendRequest(Request) I noticed that after:
this.httpResponse =
Hello Jon,
tanks for reporting this problem, I've entered an issue for that point :
https://github.com/restlet/restlet-framework-java/issues/630
Best regards,
Thierry Boileau
I'm seeing similar behavior (leaked connections), but in a different case.
In our case we get leaked connections if
I should clarify. We are using org.restlet.ext.httpclient.
In our log file, when the request is for a valid resource URI, we see log
messages that indicate the connection is being returned to the pool.
15:18:31.193 [qtp1028854205-70 - /order] DEBUG
o.a.h.i.c.t.ThreadSafeClientConnManager -
Thanks Thierry. If you suggest where to look I'm happy to see if I can fix it.
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2994322
I'm seeing similar behavior (leaked connections), but in a different case.
In our case we get leaked connections if the request throws an exception.
We noticed this in Restlet 2.0.11, and I just tried 2.0.14 and I see the same
problem.
String uri =
if anyone has any insight I'm all ears.
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/OPTIONS-and-TRACE-not-being-caught-by-Restlet-Server-tp7578142p7578150.html
Sent from the Restlet Discuss mailing list archive at Nabble.com
://restlet-discuss.1400322.n2.nabble.com/OPTIONS-and-TRACE-not-being-caught-by-Restlet-Server-tp7578142p7578151.html
Sent from the Restlet Discuss mailing list archive at Nabble.com.
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId
My server stops serving after some connections and I would like to increase the
number of threads.
try
{
Server server = new Server(Protocol.HTTP, m_iPort,
ContentProvider.class);
server.start();
}
catch (Exception e)
{
e.printStackTrace();
}
This line below would return a null
Hello Liem,
you can set it as follow : server.setContext(new Context());
Generally, such connector is used inside a Component, which automatically
adjust the connector's context.
Best regards,
Thierry Boileau
My server stops serving after some connections and I would like to increase
the
Hi,
I am trying to send a POST request to my restlet service.
I am getting the POST data and performing some time consuming operations which
takes about 1 minute.
In the mean time, either the request is timing out or the restlet server is
sending a response back to the client but the server
Yes - that works! Many thanks.
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2888171
Thanks for the response. I thought it would be something that I was not
releasing. Constructive comment: The examples don't release the resource.
I'll try your solution next week when I'm back at work.
- Jim
--
I am using Restlet to implement a web service. The client (also uses Restlet)
makes many consecutive calls to the server, but after a small number of calls
complete successfully, further calls hang the server, which shows the message:
INFO: Stop accepting new connections and transactions.
Jim,
You forget releasing the resource! Try add clientResource.release(), like
this:
Response response = clientResource.getResponse();
*clientResource.release();*
Status status = response.getStatus();
return status: + status + message: +
: mercredi 23 mars 2011 18:56
À : discuss
Cc : ROSTAING TAYARD Philippe
Objet : Re: Restlet Server, GWT, restlet client
Hello Philippe,
the main problem is that the GWT *extension* for the server side (jse, jee, gae
edition), is able to serialize an objet sent to a GWT client, and deserialize
an object
to think to simplify this.
Best regards,
Thierry Boileau
Hi All,
I'm totally newbie, and this is what I want to do with restlet :
- have a restlet server serving a GWT application
- have a restlet client accessing this server
Instead of making a long discussion, I enclosed
My problem ended up being Grizzly (version 1.9.21).
Switching to Jetty made the problem disappear, at least for the past 24
hours. Will keep you posted.
I don't know if the issue is Grizzly itself or the Restlet connector,
but this is a production system I can't play around with and test.
I get these errors frequently in my restlet server log.
I'm running restlet 2.0-RC04 as a standalone process.
I consume the web services with Apache HTTP client 3.1.
It seems to be related with serving relatively large pages (it seems to
get more frequent).
At the HTTP client side, sometimes
I just tried using nginx as a reverse proxy. It doesn't seem to make any
difference, data is still being lost.
--
View this message in context:
http://restlet-discuss.1400322.n2.nabble.com/Data-loss-between-HTTP-client-and-restlet-server-errors-writing-to-non-blocking-channel-tp5720451p5721844
Hello Patrick,
when used inside a Component, a ClientResource will use the client connectors
registered by the Component, exactly as hosted applications share the server
connectors registered by the component [1] and [2].
Thus, you simply need to add the following line of code:
Hi
I tried some more by using standard URLConnection inside the same block like...
-
URL yahoo = new URL(http://www.yahoo.com;);
URLConnection yc = yahoo.openConnection();
BufferedReader in = new BufferedReader(
I hope I'm not spamming the list. I tried post once, but the message doesn't
seem to show up.
I'm using restlet 2.0rc4 on BSD, and run into some interesting problem. I'm
trying to make http request using restlet client from inside restlet server
code (inside ServerResource @post method
Hi,
I'm using restlet 2.0rc4 on BSD, and run into some interesting problem. I'm
trying to make http request using restlet client from inside restlet server
code (inside ServerResource @post method).
Code snippet is as following:
InetAddress yahoohost
-Message d'origine-
De : webp...@tigris.org [mailto:webp...@tigris.org]
Envoyé : vendredi 29 octobre 2010 15:54
À : discuss@restlet.tigris.org
Objet : RE: Restlet client code does not work in Restlet Server
(ServerResource) service.
Hi
I tried some more by using standard URLConnection
Hi Jerome,
I didn't see any response, only your name as author of response post. :-)
Anyway, should I add any issue to your bug tracking in this case?
--Patrick
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2677196
Hello,
I have put together an application based on the RESTlet First Resource sample
code. The server component runs within Tomcat. All works fine (I can send data
to the RESTlet server and it receives it.
However, I would like to change the port it is listening on (it is currently
listening
Hello,
unless you instantiate your own component (using a restlet.xml file, or
specifying a org.restlet.component parameter in the web.xml file), the
component listens on the port defined by the servlet container. In this case,
this should be transparent.
Best regards,
Thierry Boileau
: CAS authentication in Restlet server
Hi Jerome,
Thanks for the pointer, it was very useful. I think I'm starting to see
the picture now. I'm a bit confused about the various places where a
Verifier is referenced. I've seen such references in Context,
ChallengeAuthenticator and Realm. I assume
Hello,
I know it is quite iconoclast, but I would like to know your feeling about
the following idea, ie having a client (for instance gwt app) with a restlet
server inside...
The idea behind is the following ; many different clients access a server
through restlets, and some REST actions may need
I was thinking the same about web sockets. We have several applications
that use Restlet in GWT to talk to a server, and I have been trying to think
about good ways to port these for offline/local use to use HTML5 database
APIs. This might be a road in the future. I agree, a bit iconoclastic,
Rhett Sutphin wrote:
Hi Arjohn,
On Dec 2, 2009, at 12:34 PM, Arjohn Kampman wrote:
Hi Rhett, others,
Thanks for your suggestion. Since I'm fairly new to the subject, I
hope
you (and others) can help me a bit to get things clear.
If I understand you correctly, you are suggesting to
Hi Jerome,
Thanks for the pointer, it was very useful. I think I'm starting to see
the picture now. I'm a bit confused about the various places where a
Verifier is referenced. I've seen such references in Context,
ChallengeAuthenticator and Realm. I assume that the context's verifier
serves as a
Hi Rhett, others,
Thanks for your suggestion. Since I'm fairly new to the subject, I hope
you (and others) can help me a bit to get things clear.
If I understand you correctly, you are suggesting to use a CAS proxy
ticket as an authentication token. However, such a token can only be
sent once to
Hi Arjohn,
On Dec 2, 2009, at 12:34 PM, Arjohn Kampman wrote:
Hi Rhett, others,
Thanks for your suggestion. Since I'm fairly new to the subject, I
hope
you (and others) can help me a bit to get things clear.
If I understand you correctly, you are suggesting to use a CAS proxy
ticket as
Hi Jerome, others,
I have just started working on this. If I get it up-and-running, I can
probably donate the code to the restlet project if you like.
I'm currently looking at the org.restlet.security API, but I'm seeing a
lot of terms/concepts that are new to me. Do you have a bit of
@restlet.tigris.org
Objet : Re: CAS authentication in Restlet server
Hi Arjohn,
On Nov 10, 2009, at 5:31 AM, Arjohn Kampman wrote:
Hi Rhett,
Many thanks for these pointers and your suggestions. The code looks
nice
and clean.
Thanks.
The license for this code looks very BSD-like
Hi Rhett,
Many thanks for these pointers and your suggestions. The code looks nice
and clean. The license for this code looks very BSD-like, is that
correct?
I noticed that this code is based on acegi. Is this easier/better than
using the CAS client code directly?
Arjohn
Rhett Sutphin wrote:
Hi Arjohn,
On Nov 7, 2009, at 4:31 AM, Arjohn Kampman wrote:
I'm planning to integrate CAS (proxy) authentication in my Restlet-
based
server. Has anyone worked on this before? Any suggestions on how to
best
implement this?
I have done this for my Restlet-based API. I can point you to
Hi all,
I'm planning to integrate CAS (proxy) authentication in my Restlet-based
server. Has anyone worked on this before? Any suggestions on how to best
implement this?
CAS: http://www.jasig.org/cas
Regards,
Arjohn
--
Arjohn Kampman, Senior Software Engineer
Aduna - Semantic Power
setting up a test harness for my restlet server; using junit inside
Eclipse. I am using restlet to generate the client side messages and view
the responses.
It doesn't seem possible to generate bad HTTP headers with the restlet
client. Whenever I try to create headers that are part
Hi,
I am setting up a test harness for my restlet server; using junit inside
Eclipse. I am using restlet to generate the client side messages and view the
responses.
It doesn't seem possible to generate bad HTTP headers with the restlet client.
Whenever I try to create headers that are part
Technologies ~ Co-founder ~ http://www.noelios.com
-Message d'origine-
De : Ashish Sharma [mailto:ashish.shar...@hp.com]
Envoyé : mercredi 23 septembre 2009 11:58
À : discuss@restlet.tigris.org; Bruno Harbulot
Objet : RE: Re: Integrating Apache and Restlet server like Apache and Tomcat
Bruno,
I
Bruno,
Can you post a simple code sample for reference.
As I am a newbie.
Thanks in advance!!
Ashish
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2398769
Hi Ashish,
As Rémi said, mod_proxy might be better for what you need. In addition,
mod_jk seems to have been deprecated in favour of mod_proxy_ajp (both
use AJP). There is more about this on the Jetty wiki:
http://docs.codehaus.org/display/JETTY/Configuring+AJP13+Using+mod_jk
The only case
Bruno,
I am able to run restlet over jetty as advised by you, but I am not clear how
can it fulfill my original requirement.
Please explain!!!
thanks in advance
Ashish
Hi Ashish,
Ashish Sharma wrote:
Hello,
I have my Apache http server running on localhost:80 and restlet server
Hello,
I have my Apache http server running on localhost:80 and restlet server on
localhost:8182, but I want to configure above combination just like Apache http
server and Apache tomcat servlet container can be configured with mod_jk
library.
Is it possible?
Do I have to modify code
Hello,
I have my Apache http server running on localhost:80 and restlet server on
localhost:8182, but I want to configure above combination just like Apache http
server and Apache tomcat servlet container can be configured with mod_jk
library.
Is it possible?
Do I have to modify code
Hi Ashish,
Ashish Sharma wrote:
Hello,
I have my Apache http server running on localhost:80 and restlet server on
localhost:8182, but I want to configure above combination just like Apache
http server and Apache tomcat servlet container can be configured with mod_jk
library
Hello,
Not sure I understood the question.
You'd better user mod_proxy and ProxyPass instead of mod_jk.
Rémi
On Tue, Sep 22, 2009 at 14:40, Ashish Sharma ashish.shar...@hp.com wrote:
Hello,
I have my Apache http server running on localhost:80 and restlet server on
localhost:8182, but I
I just realized I am using an old version of Tomcat (4.1) and the
servlet spec for that version of Tomcat does not have support the
'getLocalAddr' method. Darn it.
Stephan Koops wrote:
Hi Matt,
looks like that the JARs are from different Restlet versions.
best regards
Stephan
Hi Matt,
looks like that the JARs are from different Restlet versions.
best regards
Stephan
--
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=2359005
d'origine-
De : news [mailto:n...@ger.gmane.org] De la part de Leshek
Envoye : jeudi 15 janvier 2009 00:21
A : discuss@restlet.tigris.org
Objet : Re: Command line to STOP Restlet server
When you stop the parent Component, it stops all the child connectors.
Sounds like a simple, nice, soft stop
Fiedorowicz
Envoye : mercredi 14 janvier 2009 06:35
A : discuss@restlet.tigris.org
Objet : Re: Command line to STOP Restlet server
All good, helpful hints, but... by Restlet designed (the best practice?) way
to stop Restlet internal HTTP server?
Leshek
Ps. I have re-registered with tigris, thank
When you stop the parent Component, it stops all the child connectors.
Sounds like a simple, nice, soft stop for me, but...
What I am thinking is to respond to URI request like PUT .../shutdown
(limit to localhost request and run through authentication guard as all
the other requests).
I want to have stop and exit restlet server command line interface.
The start is simple (java -jar myRest.jar).
I know from within I can do getContext().getApplication().stop()
I could to it in response to http request .../STOP, but... I want to keep
control on the server only.
So I am looking
I want to have stop and exit restlet server command line interface.
The start is simple (java -jar myRest.jar).
I know from within I can do getContext().getApplication().stop()
I could to it in response to http request .../STOP, but... I want to keep
control on the server only.
So I am looking
Take a look at Java Service Wrapper:
http://wrapper.tanukisoftware.org/
It covers all sorts of possibilities.
--tim
On Mon, Jan 12, 2009 at 12:29 PM, Leshek lesh...@hotmail.com wrote:
I want to have stop and exit restlet server command line interface.
The start is simple (java -jar
Leshek wrote:
I know from within I can do getContext().getApplication().stop()
I could to it in response to http request .../STOP, but... I want to keep
control on the server only.
Apart from the Service Wrapper already pointed out, you could always restrict
access to such a resource. Either
All good, helpful hints, but... by Restlet designed (the best practice?) way
to stop Restlet internal HTTP server?
Leshek
Ps. I have re-registered with tigris, thank you Jerome!
--
Hi,
its nice hearing that in 1.1M4 we are going to have facilities to deploy war
project in restlet server. It will be really nice if we can have some running
example of how to deploy and run war.
I tried with restlet server, but filed to deploy war in restlet server. So,
right at this moment I
@restlet.tigris.org
Objet : Re: restlet server
Hi,
its nice hearing that in 1.1M4 we are going to have
facilities to deploy war
project in restlet server. It will be really nice if we can
have some running
example of how to deploy and run war.
I tried with restlet server, but filed to deploy
Hi,
Is there any way to point restlet server to a full web app? I mean the web app
is having directory structure as a regular web app with WEB-INF, META-INF.
web.xml.
I want restlet server to use that web.xml. I mean, is it possible use restlet
server to work exactly like it will work if i
Actually, i am using Echo2 framework. I want to deploy or run my developed Echo2
in restlet server. but have no clue how to do that.
please, any help?
-Message d'origine-
De : Rob Heittman [mailto:[EMAIL PROTECTED]
Envoyé : lundi 17 mars 2008 14:23
À : discuss@restlet.tigris.org
Objet : Re: restlet server
The Restlet framework can run inside a J2EE container quite
nicely, by using the ServerServlet instead of a standalone
:[EMAIL PROTECTED] De la part de Aaron Crow
Envoyé : lundi 10 mars 2008 23:58
À : discuss@restlet.tigris.org
Objet : Re: Shut down a Restlet server using kill?
Hi Jerome and All,
A related question: Is there a programmatic way to tell the
Restlet engine
to do a clean shutdown, and if so
20:28
À : discuss@restlet.tigris.org
Objet : Shut down a Restlet server using kill?
Is it ok to shut down a Restlet server using Unix kill? What
does Restlet do
in this case? And does anyone have any good advice on what
the application
code might do to handle this event properly?
On Sat, Mar 8, 2008 at 2:25 PM, Steve Loughran [EMAIL PROTECTED] wrote:
[...]
We in SmartFrog, http://smartfrog.org/ are assing support for Restlet
deployments as manageable components, but I don't consider the stuff
stable yet. I've finally got all my tests with S3 working, with
On Sat, Mar 8, 2008 at 2:29 PM, Steve Loughran [EMAIL PROTECTED] wrote:
[...]
you're server should start returning something other than 200 from its
happy page, and the HTTP-aware front end load balancer (which polls
these pages) will stop routing traffic to it. That makes it implicit
that
,
Jerome
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Aaron Crow
Envoyé : jeudi 6 mars 2008 20:28
À : discuss@restlet.tigris.org
Objet : Shut down a Restlet server using kill?
Is it ok to shut down a Restlet server using Unix kill? What
does Restlet do
You should just down a Restlet server like any other java application,
either with QUIT on unix or Control-Break on Windows.
That will allow the jvm to gracefully shutdown by running finalizers and
shutdown hooks.
Sincerely,
Kevin Conaway
On Thu, Mar 6, 2008 at 2:28 PM, Aaron Crow [EMAIL
On Thu, Mar 6, 2008 at 11:28 AM, Aaron Crow [EMAIL PROTECTED] wrote:
Is it ok to shut down a Restlet server using Unix kill?
Depends on your application's specifics.
For example, the oldest Restlet-based production code that I have is
an authentication gateway that I would just kill outright
a Restlet server using Unix kill?
Depends on your application's specifics.
For example, the oldest Restlet-based production code that I have is
an authentication gateway that I would just kill outright.
What does Restlet do in this case?
Unless something has been changed in the v1.1+ world
@restlet.tigris.org
Objet : Shut down a Restlet server using kill?
Is it ok to shut down a Restlet server using Unix kill? What
does Restlet do
in this case? And does anyone have any good advice on what
the application
code might do to handle this event properly?
On Fri, Mar 7, 2008 at 4:45 PM, Aaron Crow [EMAIL PROTECTED] wrote:
Hi John,
Howdy!
So as far as server app code dealing with a forced shutdown, may I ask what
you recommend for situations where there's some task running that really
should be allowed to complete? For example, would you
Is it ok to shut down a Restlet server using Unix kill? What does Restlet do
in this case? And does anyone have any good advice on what the application
code might do to handle this event properly?
You might want to look at the code for the existing connectors to see
what's involved.
Hope this helps,
John
On 8/8/06, Winters, Chris [EMAIL PROTECTED] wrote:
Say I wanted to have a restlet server run alongside another process that
accepted messages over something besides HTTP. In my head's
John D. Mitchell wrote:
You might want to look at the code for the existing connectors to see
what's involved.
That's the plan -- I'm not averse to plugging through this myself, but I
wanted to make sure there wasn't any fundamental problem before getting
into it. Lazy answer, I know ;-)
87 matches
Mail list logo
