hi michael
Ok, makes sense. We need then
- Have a respective value entity on the oak-api. There is already the
CoreValue class which should somehow fit/be fitted into the picture.
- Update all places in the API where Scalar is used currently with the
new value representation.
rather do it now that later, when its used all over the place.
- Still come up with a encoding into JSON. However since this is not
exposed through the oak-api we are more flexible here.
yes, we will in any case need to have an encoding into JSON.
Could you come up with a draft for such a class/interface?
i can give it a try next week. today i wanted to look at
the editor stuff again.
That would allow me to take the role of the API critic for once ;-)
lol :) we should do that more often anyway, should't we?
regards
angela
Michael
kind regards
angela
Implementation wise, would that
en/decoding happen inside oak-jcr or oak-core?
Michael
[1]
http://svn.apache.org/viewvc/jackrabbit/sandbox/jackrabbit-mk/jackrabbit-spi2microkernel/src/main/java/org/apache/jackrabbit/spi2microkernel/Values.java?view=markup
