RE: Restlet Framework 2.1 RC6 and 2.0.15 released
I've been experimenting with 2.1 for a while with a few big Restlet applications. I want to point out that 2.1-RC6 is the first version of Restlet (including all the 2.0 line!) in which I could use Directory over the internal connector without any response hangs. Hooray, it may be possible to finally remove my dependency on Jetty! (In 2.0, I used Grizzly for a comparable workaround.) I know I should have opened a bug on this in the past, but it's just been so persistent for so many versions, and there was a simple enough workaround. Nevertheless, I would sometimes remove Jetty just to see how the internal connector was behaving... and it looks good. Good job, bug reporters and bug fixers! -Tal -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=3000664
RE: Restlet Framework 2.1 RC6 and 2.0.15 released
Hi Tal, Thanks for reporting your experience! This new NIO internal has taken a long time to get off the ground as it was a massive design and coding effort under the hood. Now, stabilization efforts are starting to pay off... We still have some way to go (especially HTTPS which doesn't work so well in 2.1 RC6). That's our latest major concern to fix before releasing 2.1.0 next month :) BTW, the download link for 2.0.15 that was broken (500 error) has now been fixed after your report. Thanks, Jerome -- http://www.restlet.com http://twitter.com/#!/jlouvel -Message d'origine- De : Tal Liron [mailto:tal.li...@threecrickets.com] Envoyé : vendredi 24 août 2012 10:17 À : discuss@restlet.tigris.org Objet : RE: Restlet Framework 2.1 RC6 and 2.0.15 released I've been experimenting with 2.1 for a while with a few big Restlet applications. I want to point out that 2.1-RC6 is the first version of Restlet (including all the 2.0 line!) in which I could use Directory over the internal connector without any response hangs. Hooray, it may be possible to finally remove my dependency on Jetty! (In 2.0, I used Grizzly for a comparable workaround.) I know I should have opened a bug on this in the past, but it's just been so persistent for so many versions, and there was a simple enough workaround. Nevertheless, I would sometimes remove Jetty just to see how the internal connector was behaving... and it looks good. Good job, bug reporters and bug fixers! -Tal -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=30006 64 -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=3000675
The parent context doesn't have a client dispatcher available. Unable to handle call.
Hello The parent context doesn't have a client dispatcher available. Unable to handle call. Refererence: Version: 2.1RC2, 2.1RC5 2.1RC6 Context: I use Restlet server and client in GAE environment When exception happens: After posting when I read response using Representation it happens. JacksonRepresentationNetworkProductOrder productOrderRep = new JacksonRepresentationNetworkProductOrder(output, NetworkProductOrder.class); productOrder = productOrderRep.getObject(); Exception message org.restlet.engine.util.ChildClientDispatcher parentHandle: The parent context doesn't have a client dispatcher available. Unable to handle call. Conditionally Working: If I comment servlet and servlet-mapping element for restlet in web.xml, it works. ( meaning client works fine, natually no restlet server ) My post in Restlet Discuss is given below http://restlet-discuss.1400322.n2.nabble.com/The-parent-context-doesn-t-have-a-client-dispatcher-available-Unable-to-handle-call-td7578291.html Thanks Sasi Marian -- http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447dsMessageId=3000793
