Hi,
it seems that currently JCR2SPI assumes that the NoteIds returned for
referenceable nodes actually do contain the UUID of that Node -- if the
SPI implementation returns an absolute path based NodeID instead,
JCR2SPI's Node.getUUID() implementation fails.
Proposals:
Either
1) Decide that this is how things are supposed to work, and just
document it. Drawback: there may be repositories that have referencable
nodes but path-based lookup still is more efficient (however, in that
case the implementation could build a custom NodeId that contains both).
or
2) Change JCR2SPI to that it does not make that assumption, but instead
retrieves the value of the jcr:uuid property.
Additional thought: before making a decision on this we may want to look
at what new requirements JSR283 brings to the table.
BR, Julian
- SPI requirement for NoteIds of referenceable Nodes Julian Reschke
-