Router swallowing exceptions

I unfortunately accidentally discovered that if a "Resource" is not instantiable (e.g., the class is abstract, constructor is protected, etc.), the router-which is unable to complete its work-does "nothing" and doesn't log anything either It would be most appreciated if it would log a (probably SE

RE: Restlet 1.1: Rationale behind deprecation of Variant#setModificationDate

Hi Lars, I agree about refactoring handleGet() and added a note about that in the RFE. Best regards, Jerome Louvel -- Restlet ~ Founder and Lead developer ~ http://www.restlet.org Noelios Technologies ~ Co-founder ~ http://www.noelios.com -Message d'origine- De : Lars Heuer [mailto:[E

Re: Restlet 1.1: Rationale behind deprecation of Variant#setModificationDate

Hi Jerome, [...] > I think there is room for optimization but this would lead to some > significant refactoring. Let's have a look at this for Restlet 2.0: > "Optimize conditional handling" > http://restlet.tigris.org/issues/show_bug.cgi?id=633 Thanks, for the time being I'll handle that use cas

RE: Restlet 1.1: Rationale behind deprecation of Variant#setModificationDate

Hi Lars, You are correct, the variants were only used for content negotiation hence the potential confusion. I think there is room for optimization but this would lead to some significant refactoring. Let's have a look at this for Restlet 2.0: "Optimize conditional handling" http://restlet.ti

Re: serving static files from servlet WAR with Directory class: index.html not served automatically

Hello Luis, we have reconsidered the question. The WAR client connector supports the content negotiation feature. The fix is available in the svn repository and in the last snapshot. Best regards, Thierry Boileau -- Restlet ~ Core developer ~ http://www.restlet.org Noe