com]
Envoyé : vendredi 15 juillet 2011 10:41
À : discuss@restlet.tigris.org
Objet : Re: Problem passing Context with Spring extension
Hello Paul and Daniele,
I've opened an issue for that
(http://restlet.tigris.org/issues/show_bug.cgi?id=1288).
The current trunk provides a fix for that, since
Hello Paul and Daniele,
I've opened an issue for that (
http://restlet.tigris.org/issues/show_bug.cgi?id=1288).
The current trunk provides a fix for that, since there is no need to provide
a context when attaching an application. This behaviour is actually a
reproduction of when happens when attac
Have a look at how I create the child context here:
https://github.com/apius/apius-core/blob/master/projects/identity/src/identity-context-common.xml
Do this and you should be able to pass the child context into the Application
constructor without an error.
Paul Morris
On Jul 14, 2011, at 4:12
I am having the same error but I've no reason to believe is related to
a classpath issue. I'm using Restlet 2.0.8
I fall into this problem trying to add HTTP client protocol to my
applicaiton to allow a new client resource to contact a third web
service from inside my application context.
Here's
I think I had some classpath problems or perhaps even a mixture of different
release version jars. I deleted all jars from WEB-INF/lib and replaced the
restlet and other dependent jars with those packaged in the 2.0.8 release and
everything started behaving as expected. (Shaking my head).
-
I'm getting the error below. Using as a model the example in the Restlet in
Action book for Spring integration. The book indicates that the example is the
correct way to create a child context for passing to the application but
nevertheless the error persists. Attaching my bean container xml.
J
6 matches
Mail list logo
