[dna-issues] [JBoss JIRA] Updated: (DNA-303) The workspace NamespaceRegistry implementation should be shared

Randall Hauch (JIRA) jira-events at lists.jboss.org
Tue Mar 17 00:55:22 EDT 2009


     [ https://jira.jboss.org/jira/browse/DNA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Randall Hauch updated DNA-303:
------------------------------

    Fix Version/s: 0.5
                       (was: 0.4)


Changing the fix version to 0.5, since this is not critical for 0.4 functionality and is more of an optimization for larger numbers of Session instances to the same workspace.  However, we should keep these changes in mind, should any modifications be required to these components in 0.4.

> The workspace NamespaceRegistry implementation should be shared
> ---------------------------------------------------------------
>
>                 Key: DNA-303
>                 URL: https://jira.jboss.org/jira/browse/DNA-303
>             Project: DNA
>          Issue Type: Sub-task
>          Components: API, JCR
>    Affects Versions: 0.3
>            Reporter: Randall Hauch
>             Fix For: 0.5
>
>
> The JcrWorkspace class currently uses the GraphNamespaceRegistry, which implements DNA's NamespaceRegistry implementation on top of namespace mappings stored in a graph.  While this works for a single ExecutionContext, having a shared implementation for multiple JcrWorkspace objects means that the update methods need to be done with the ExecutionContext of the user making the changes.  This would require changing the design a fair amount.
> The NamespaceRegistry implementation would also need to be thread-safe.

-- 
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

        



More information about the dna-issues mailing list