Resolve NodeId/UUID ambiguity
-----------------------------
Key: JCR-113
URL: http://issues.apache.org/jira/browse/JCR-113
Project: Jackrabbit
Type: Improvement
Environment: jackrabbit r164198
Reporter: Tobias Strasser
Assigned to: Stefan Guggisberg
Priority: Minor
Currently the NodeId and internal UUID strings are randomly used throughout
jackrabbit.
NodeIDs are created from UUID strings and vice versa very often. i suggest to
make the ItemId/NodeId/PropertyId extendable for other applications (e.g.
clients that want to make use of jackrabbits code base, but need additional
information in the NodeIds).
i suggest:
- turn ItemId, NodeId, PropertyId into interfaces
- replace all *.getUUID() methods to getId() methods (also parentUUID)
- consider to remove NodeId.getUUID() and rather place it to some sort
of uuid manager. this indicates that a getUUID() operation could be
expensive.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
