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
