I'm evaluating restlet and I like what I see, especially the 2.0 version.

If I understand ServerResource.setEx‚Äčisting(false) correctly, the restlet 
infrastructure should send back a 404 when I call setExisting(false) on a 
request (called within the doInit method)

Reproducable with 2.0m3 by navigating to /firstResource/items/333 on a server 
restart. Server is returning 500 because the example is throwing an exception 
in toXml() (because item is null), but that is only the symptom -- I would 
think it should never get there because the example is calling 
setExisting(false) in doInit.



Reply via email to