[
https://jira.jboss.org/jira/browse/DNA-466?page=com.atlassian.jira.plugin...
]
Randall Hauch commented on DNA-466:
-----------------------------------
One benefit of the current connectors that don't support UUIDs is that they don't
support updates, meaning the client has no need to use Session.save(). So until this
issue is resolved completely, two workarounds for configurations that use these connectors
are:
1) do not call Session.save(), Session.refresh(), Node.save(), or Node.refresh(); or
2) do not retain Node references after any of these methods
Obviously these are not ideal, and thus this issue will remain open.
JCR requires connectors to expose UUID as identifier property
-------------------------------------------------------------
Key: DNA-466
URL:
https://jira.jboss.org/jira/browse/DNA-466
Project: DNA
Issue Type: Bug
Components: JCR
Affects Versions: 0.5
Reporter: Randall Hauch
Assignee: Randall Hauch
Priority: Blocker
Fix For: 0.6
The JCR implementation currently expects connectors to return a UUID as the identifier
property. This is obviously incorrect, as it goes against several of the connectors
we've already implemented. In particular, the SessionCache is expecting to find the
UUID, and submits requests to the source with only the UUID (not the path).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira