I'm not sure :) One can argue that it's up to the implementation how it
stores data.
So if I put a date into a MVM and later on read the resource and get the
value, I expect a date to be returned. So from a documentation pov, a MVM
supports all serializable types - and should ensure that the type
When setting a java.util.Date as the value in the ModifiableValueMap, the
Date object is serialized and saved as the value. This seems like odd
functionality, as java.util.Calendar is supported and the internal datatype
is called 'date'.
I understand that the reason is that internally the JCR
