IvanLatysh wrote:
Julian Reschke wrote:
I strongly disagree. Being absent, and having an empty string value
are completely different things. Font instance, you can't have a
"null" attribute value in XML.
XML attribute isn't type strict as JCR is.
So parameter.setValue(valueFactory.createValue((Double)null)) should
result a parameter of type 'Double' with null value.
OK, let's just agree that we disagree here.
...
You can do that as well, can't you?
Yes I can do that. And as I sad: API is not consistent.
Spec promote usage of "p.setValue((Value)null)" as the way to remove the
property when it should say to use "p.remove();" instead.
...
I totally agree that teaching people to use p.remove() would be preferable.
I believe it is a community process so committee will discuss it.
And again it is funny to hear that it is a major change when XPath just
has been dropped.
Be reasonable, if you brake the spec, at least fix the obvious bugs.
Anyway 2.0 won't be compatible with 1.0
...
I personally think that 2.0 *should* be as compatible as possible (and
yes, that means that people should be ably to rely on XPath).
Best regards, Julian
