[EMAIL PROTECTED] wrote: > > Can someone explain the design decision to not allow > NodeProperty's to allow null for their property value? > > In place of a literal null, the value 'new String()' is > substituted. Clearly there is a distinction between a > zero-length string and null, so why the assumption that > null = zero-length string? > > I believe there are scenarios where you'd want a property > to exist in a revision descriptor and for its value to be > null. > > Any thoughts? >
A couple of major reasons come immediately to mind: - Slide is designed primarily to be accessed through webdav. Since webdav is essentially a textual protocol, there's no sensible way (and certainly no standard way) to distinguish between an empty string and a null string. So you wouldn't be able to set OR retrieve this null value through the main (webdav) interface. - The slide<->store interface isn't designed to do this. The stores aren't expected to be able to store null properties. Michael -- To unsubscribe, e-mail: <mailto:slide-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:slide-dev-help@;jakarta.apache.org>
