[jira] Updated: (JCR-657) Node references limitations

["Jukka Zitting (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCR-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-657:
------------------------------

    Status: Patch Available  (was: Open)

> Node references limitations
> ---------------------------
>
>                 Key: JCR-657
>                 URL: https://issues.apache.org/jira/browse/JCR-657
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-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.
-
You can reply to this email to add a comment to the issue online.