Upgraded libs from 2.0M4 to 2.0M5 (JSE edition), now my app is broken

Hello there, I've just updated all Restlet jars used in my project from 2.0M4 to 2.0M5, made small modifs on some resources thanks to the Request/Response refactoring, and some deleted methods like ServerResource.getVariants().put(Method, ListVariant). Anyway, migrated my code to 2.0M5 in less

Re: Upgraded libs from 2.0M4 to 2.0M5 (JSE edition), now my app is broken

Hello Fabian, I think you're right, I've replaced the createRoot method with the createInboundRoot method (createRoot has been deprecated and replaced) and it works. I'm checking why it fails with createRoot. best regards, Thierry Boileau Hello there, I've just updated all Restlet jars used

Re: Upgraded libs from 2.0M4 to 2.0M5 (JSE edition), now my app is broken

Hi, actually the last added service is normally updated with the application's root as next handler. Unfortunately, the setNext method does not take into account the fact that the createRoot method has been deprecated, which leads to a setNext(null) for the last attached service. I've fixed

Re: Upgraded libs from 2.0M4 to 2.0M5 (JSE edition), now my app is broken

Hello Thierry, thanks for fixing this. I've changed createRoot to createInboundRoot and my code is now working fine. I'll review this (if I remember ;-)) at 2.0M6 time. I'll leave createInboundRoot because it's working as expected. De rien. cya. On Tue, Sep 29, 2009 at 11:28 AM, Thierry