Good afternoon.
It was not intended but it forced us to call a restful web service within a
restful web service. For example RWS1 in projectA deployed on server1 is
calling RWS2 in projectB deployed on server2. I just wanted to find what could
be disadvantes/cons by doing this.
Thanks
Venkat
Doh! I think I found the answer thread:
http://restlet-discuss.1400322.n2.nabble.com/automated-conversion-from-java-object-to-json-td3584962.html
Sorry for adding noise to the discussion board...
--
Hi Martin,
I've just fixed this regression in SVN trunk.
Note that it's better to use the c...@restlet.tigris.org mailing list to
discuss such issues (or enter defect reports in Tigris.org tracket).
Best regards,
Jerome
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.org
Noelios
I'm not clear from the question if you're asking about the number of task
threads as Tim has explained, or the number of http listener threads, for that
use:
Server httpServer = new Server(Protocol.HTTP, port);
serviceComponent.getServers().add(httpServer);
Hi Andrei,
Thanks for creating the bug report. Here it is:
http://restlet.tigris.org/issues/show_bug.cgi?id=1285
This looks like a serious one to fix !
Best regards,
Jerome
--
Restlet ~ Founder and Technical Lead ~ http://www.restlet.org/
http://www.restlet.org
Noelios Technologies
Oh ... that's probably what the original question was asking about. I just
jumped reflexively on the phrase thread pool. Sorry...
--tim
On Thu, Jul 28, 2011 at 8:40 AM, Matt Kennedy stinkym...@gmail.com wrote:
I'm not clear from the question if you're asking about the number of task
threads
Once again you've been an enormous help.
By removing the Context from the Application constructor, I've moved from
having errors that I don't understand to having errors that I expected. I
consider this a step in the right direction
(Not sure what the Context is supposed to be doing
7 matches
Mail list logo