RE: Session, google app and sip

Hi Matthieu! 1+2) Yes, this is the case. The thread pool can be configured and its parameters vary depending on the HTTP server connector used. For the internal HTTP connector (inside org.restlet.jar), you can find details here:

Re: custom exception message

Hi Sean, I hope you have made the appropriate changes in the configuration file to make use of the status service class which you have created. In your main method you need specify the status service class by calling the application.setStatusService method and pass the class that you have

RE: SSL on Google App Engine

Hi Jerome, thanks you're absolutely right of course. I added this lines to my web.xml and now it demands a certificate when accessing the Rest-services: security-constraint web-resource-collection web-resource-nameHTTPS Rest/web-resource-name

Re: custom exception message

Hi Sean, I think you meant /I called application.setStatusService in my main method and it still does/ *not* /work/. Another thing that you should consider is, *you are not catching* the unhandled exceptions in your resource classes and then wrapping them in ResourceException and throwing it

Re: Problem ignoring local addresses when calling restlet webservices using HtpClientConnector (Ext package)

Hi Guys, Can somebody help with the problem mentioned in the thread? It's urgent as I can't proceed further without resolving this issue. Jerome, Tim I think you might have the workaround for the issue. Thanks Nitin -- View this message in context:

Re: Problem ignoring local addresses when calling restlet webservices using HtpClientConnector (Ext package)

Which Tim do you mean? Not me, I hope -- I don't even understand the question. --tim On Mon, Nov 7, 2011 at 6:40 PM, Nitin Arora aro_ni...@yahoo.com wrote: Hi Guys, Can somebody help with the problem mentioned in the thread? It's urgent as I can't proceed further without resolving this

Re: Problem ignoring local addresses when calling restlet webservices using HtpClientConnector (Ext package)

Hi Tim, I mentioned your name based on the responses that you have already provided in the restlet forum. I can try and the explain the issue again. I've a server running in the LAN which exposes the REST API on port 8006. I've another server which is outside the lan and I consume the REST API

Documentation on Component-based Client reuse

I’ve always had a vague awareness that when an application used a Component, somehow instances of Client would be reused, somehow automatically behind the scenes. Is this still the case with 2.0 and/or 2.1? If so, can anyone point me to some documentation on how this works? Thanks! Avi