RE: b19 - Resource
-Original Message- From: Lars Heuer [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 18, 2006 7:49 AM To: discuss@restlet.tigris.org Subject: b19 - Resource Hi Jerome, For me it is not obvious why a Resource now must be constructed with a Logger instance. Can you explain this change a bit? And because the Logger may be initialized lazily in the getLogger method: Why does the Resource not provide a default constructor? Ditto for me -- I'm not sure what the 'wrappedResource' is either, but I haven't investigated much into that. Just getting into updating my internal Restlet app to the new version -- lots of compile errors! Chris
b19 Wrapper (was: Re: b19 - Resource)
Hi Jerome, I've readded the default constructor to Resource (in SVN). I need a way to [...] Merci :) The need for wrapper when further to many other classes as it's the mechanism used to separate the API classes from the implementation classes. So, we need the wrapper classes for the Restlet / Noelios engine? If they are needed for the latter, why don't we remove them from org.restlet and put them into the noelios.impl package? It was becoming too cumbersome to maintain all those wrappers (and create new ones), Javadocs duplication and making sure no method wrapper code was missing. I was writing this while your e-mail popped up: I wonder if we need the 'decoratable' behaviour in the mentioned classes. If we don't like to have a few more classes (the Wrapper* classes), we should remove the 'decoratable' feature from the Resource, Restlet, Request... . While I am using the decorated classes a lot in my Restlet projects, I think that modern IDEs like Eclipse provide enough support to write a class that delegates methods calls to a 'wrapped' class. IMO this approach is much cleaner than the getWrapped* calls in every method. Other thoughts? Best regards, Lars -- http://www.semagia.com
Powered by Restlet
Hi all, Sometimes ago, Lars suggested that I provide an affiliation button to put on web sites using Restlets. I thought it was a good idea and created thisbutton: This is also documented on the new Wiki. There is also a table that you can edit tolink your product or web site: http://wiki.java.net/bin/view/Javawsxml/Restlet Thanks,Jerome
RE: b19 Wrapper (was: Re: b19 - Resource)
Hi Lars, So, we need the wrapper classes for the Restlet / Noelios engine? If they are needed for the latter, why don't we remove them from org.restlet and put them into the noelios.impl package? I indeed have a need for those wrappers in the NRE and I thought it would also benefit to developers. [...] I wonder if we need the 'decoratable' behaviour in the mentioned classes. If we don't like to have a few more classes (the Wrapper* classes), we should remove the 'decoratable' feature from the Resource, Restlet, Request... . While I am using the decorated classes a lot in my Restlet projects, I think that modern IDEs like Eclipse provide enough support to write a class that delegates methods calls to a 'wrapped' class. IMO this approach is much cleaner than the getWrapped* calls in every method. Your remarks make sense... Let's simplify things as you proposed: removing the wrapper constructors and using hidden wrappers for the implementation where necessary. Thanks, Jerome
