I'm getting this same error using the second mechanism described here:
http://wiki.restlet.org/docs_2.0/13-restlet/28-restlet/70-restlet/195-restlet.html
In my original configuration I did not have any Component bean, just the
Application one. I've added it to attacch new protocols to the context
Hi Jim,
It's actually quite important to separate the various settings you pass
to the Component (and the connectors) from those you pass to the
Application itself. This way, you prevent leakage of sensitive
information (such as private keys for SSL connectors) to the Application.
One easy way
Gents,
I am using the latest on 1.1 branch and am getting a whole lot of
SEVERE errors. while running my test cases but they seem to be benign.
SEVERE: For security reasons, don't pass the component context to
child Restlets anymore. Use the Context#createChildContext() method
instead.class
3 matches
Mail list logo