[ http://issues.apache.org/jira/browse/JCR-657?page=all ]
Thomas Mueller updated JCR-657:
-------------------------------
Attachment: NodeReferencesChanges.txt
This patch contains a new class NodeReferencesChanges, and the relevant changes
in the core components. The persistent manager is not yet changed. This patch
does not yet remove the limitation on the number of references per node, but is
a first step in this direction. The next steps are to change the NodeReferences
class to be disk buffered if the list is too big. Also, the persistent manager
interface and implementations should be changed to directly support
NodeReferencesChanges or a similar 'delta' mechanism.
> Node references limitations
> ---------------------------
>
> Key: JCR-657
> URL: http://issues.apache.org/jira/browse/JCR-657
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Reporter: Thomas Mueller
> Attachments: NodeReferencesChanges.txt
>
>
> In Jackrabbit, there is currently a limitation on how many references
> (properties referencing to this node) a node can have. The reason is that
> node references are kept in an in-memory list when getting the references,
> and also when adding/deleting a reference.
> Proposed solution: Instead of reading/updating/storing the list of references
> whenever there is a change, use a new class NodeReferencesChanges to keep
> track of changes where possible.
--
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
