Eduard Witteveen <[EMAIL PROTECTED]> wrote:
> Michiel Meeuwissen wrote:
> [...]
>
> >nullable fields:
> >- getValue() returns null if value set to null or unset.
> >- get<Type>Value() never returns null, but the 'empty' value of the correct
> >
> >
> I think it should return also null here, or a setValue(-1) should give
> the field the value of null(if nullabla).
>
> The following code may not affect the value of the node. As long as that
> is garanteed, you have my support
> node.setValue("a", node.getIntValue("a"))
> node.setValue("b", node.getStringValue("b"))
I think we only should perhaps garantee that node.getValue("a", node.getValue("a"))
should not affect the code.
And even that, with the advent of plugins on get- and set- of bridge cannot
is not certain.
> The behavior (if a getIntValue() returns null of -1) could be configured
> in the config file.
It is impossible, because getIntValue does not return an Integer but an
'int' so never can return null. Therefore I suggested to let that be valid
for all get<Type>Values.
Michiel
--
Michiel Meeuwissen
Mediacentrum 140 H'sum
+31 (0)35 6772979
nl_NL eo_XX en_US
mihxil'
[] ()
