Hi, On 7/20/07, IvanLatysh <[EMAIL PROTECTED]> wrote:
I agree with Alexandru, and will add my use-case where we are greatly suffer from such behavior.
The use case you describe is about allowing null values in the first place, and not about setProperty(null) acting as remove(). The JCR content model is pretty clear in that it doesn't allow null values, and quite frankly I think that it's a very good thing. You can use a non-mandatory or a multi-valued property if you need to handle cases where a property can be absent, or present but with no values. BR, Jukka Zitting
