Hi, ANd it must not be forgotten that the Sling POST Servlet was designed with first class support for HTML Forms in mind. If you consider such a form, you could pre-fill it with the current values and the user could clear the fields assuming to remove/clear the properties. So the Sling POST Servlet just removes the property.
And even though the doc may contradict the implementation, the implementation has been around for more than two years. We cannot just change the implementation without risking breaking existing applications. In this special case we should therefore fix the doc and referring to the problem. Regards Felix Am 13.08.2012 um 13:15 schrieb Carsten Ziegeler: > 2012/8/13 Bertrand Delacretaz <bdelacre...@apache.org>: >> On Mon, Aug 13, 2012 at 11:47 AM, Carsten Ziegeler <cziege...@apache.org> >> wrote: >>> ...after fixing these I run into failing integration tests, e.g. >>> SlingDefaultValuesTest#testDefaultBehaviour posts a new property with >>> an empty value and checks if the property does not exists afterwards.... >> >> IIRC (but that was a long time ago) that's by design. Would we have >> another way of removing a property via a POST than setting it empty >> anyways? >> > See > http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html > > which mentions that @IgnoreBlanks should be used instead > > Reading https://issues.apache.org/jira/browse/SLING-1412 where this > was introduced, it suggests that the current behaviour was not how > these things have been handled before the fix. > > Carsten > > > -- > Carsten Ziegeler > cziege...@apache.org
