Well, I just tried calling System.exit(0) and nothing happens: the
process doesn't exit. FYI: I'm using the Simple HTTP server. There
are a bunch of threads stuck in wait().
How can I shutdown the server and cause the process to exit?
- Paul
On Jan 9, 2008, at 11:43 PM, Paul J. Lucas
Hi again,
This is a known issue with Simple that they need to fix... I don't remember
a workaround for this connector.
If this is very important, you can still switch to the Jetty connector, or
use our internal server added in 1.1 M1.
Best regards,
Jerome
2008/1/10, Paul J. Lucas [EMAIL
Well, if you want to post-process a request in error, you need to
distinguish that case from the case where you don't want to post-
process in error.
Another problem is that the current doHandle() calls next.handle()
and that doesn't return a boolean to indicate whether to do post-
Jerome,
What's the advantage of Filter.handle being final?
- R
Bug the Simple developers. I am absolutely astonished that they don't
provide a clean way to shut down their server.
On Jan 10, 2008 2:59 AM, Paul J. Lucas [EMAIL PROTECTED] wrote:
Well, I just tried calling System.exit(0) and nothing happens: the
process doesn't exit. FYI: I'm using the
Hi Sven,
Is there any best-practise on how to model resources, which consist of
other resources as well? I read the book of RichardsonRuby recently and
wondered how I could map their idea of fully connected resources to a
hibernate-domain-model.
It depends what you mean by resource
Hi all,
On Wednesday 09 January 2008 23:33:55 Jerome Louvel wrote:
Thanks Davide.
Here are some comments I initially made to you, so we can publicly
discuss them:
1) Some complimentary features that would be great to add are :
- start/stop listeners in any protocol (mainly HTTP/HTTPS for
Hi Paul,
Well, if you want to post-process a request in error, you need to
distinguish that case from the case where you don't want to post-
process in error.
Another problem is that the current doHandle() calls next.handle()
and that doesn't return a boolean to indicate whether to do post-
This has been done several times in their mailing list already. Apparently
it requires some internal redesign
I saw the posts a month or so ago when I was writing the connectors for the
test cases and I couldn't figure out why the Simple connector kept getting
address in use SocketExceptions.
The Restlet project sort of gives the message (by the example of
restlet.orgetc.) that Simple is the best thing to run Restlet servers
on top of, when
-- at least in my opinion -- in fact it's really not. The Simple project
seems kind of unresponsive to Restlet's needs. So maybe it's time for a
I switched to using Jetty and I had the same problem -- the process
didn't terminate. So I figured out that it was my fault by creating a
deadlock. I removed that and now the process terminates when calling
System.exit(0). So then I went and tried Simple again and it too now
terminates.
Hi all,
I'm happy to announce a new initiative aiming to implement the JSR-311
specification (JAX-RS API) on top of the Restlet API.
This project was proposed and will be led by Stephan Koops in the context of
his Master thesis that is now officially registered. His thesis ends in July
2007 and
Is there a way to do a POST with an Expect: header in Restlet? To use
Expect you construct your POST except you leave off the body and stick in an
Expect: 100-continue. If the server is happy to receive your POST he
returns status 100 and the client sends the normal POST with content. This
can
Thanks Jon, I forgot to increment this counter.
The end of the thesis is indeed in July 2008 :-)
Best regards,
Jerome
-Message d'origine-
De : Jonathan Hall [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 10 janvier 2008 20:20
À : discuss@restlet.tigris.org
Objet : Re: JSR-311
Hi all,
I have added reusing of BindingFactories to the JibxRepresentation,
which works reliably and quite fast. I would really advice you to give
JIBX a chance instead of JAXB.
@Jerome: Hope you got my signed JCA. Feel free to incorporate the code.
The usage is simple:
private Project
By the way, in the doHandle() method, if there isn't a next Restlet,
the method sets the response to CLIENT_ERROR_NOT_FOUND. Shouldn't
that be SERVER_ERROR_INTERNAL because the programmer goofed by not
setting a next Restlet?
- Paul
Thanks for the thoughtful reply, John. It was very helpful. One
follow-up question:
John D. Mitchell wrote:
One way to do this is to use different representations for the
different types of clients. I.e., support the usual (x)html for the
human web interface and a pure xml (or the current
Hi All,
another restshell snapshot:
http://dfa.is-a-geek.org:9000/it/slackware/dfa/restshell/1.0.3/restshell-1.0.3-exe.jar
Best Regards,
-- Davide Angelocola
18 matches
Mail list logo
