Hello Ryan,
thanks a lot for reporting this issue. I've entered an issue for this
point (http://restlet.tigris.org/issues/show_bug.cgi?id=312).
Best regards,
Thierry Boileau
The ServletConverter example has the following code:
public void init() throws ServletException {
super.init();
this.converter = new ServletConverter(getServletContext());
This will actually cause serious breakage in a production system.
To reproduce, try hitting your thus-exposed Restlet from
http://localhost... and then try hitting it from your IP address. In
the latter case you will get a blank page. Restart your webapp and
switch it around and you will see it's a "first come first serve" thing.
The reason is that the converter binds to the servlet context of
created when the "init" method is first called (lazily), and will not
listen to requests coming from any other base URL.
I got around this by creating a new servlet converter instance for
each service request. I'm not sure if this is the "right" way,
however -- will this lead to efficiency problems?
--
Ryan Daum
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Senior Developer, Toronto
647.724.5232 x 2073
