[dna-issues] [JBoss JIRA] Resolved: (DNA-282) Federation connector improperly handles root-level node with one projection of a non-root node from a single source

Randall Hauch (JIRA) jira-events at lists.jboss.org
Wed Apr 29 08:58:49 EDT 2009


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

Randall Hauch resolved DNA-282.
-------------------------------

    Resolution: Done


Corrected the connector to properly handle root-level nodes in this particular case.  The problem was in how the UUIDs were being handled.  Fixed a couple of other minor issues as well.  

Found another issue while getting the Getting Started repository examples running (see DNA-387).

> Federation connector improperly handles root-level node with one projection of a non-root node from a single source
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: DNA-282
>                 URL: https://jira.jboss.org/jira/browse/DNA-282
>             Project: DNA
>          Issue Type: Bug
>          Components: Connectors
>            Reporter: Randall Hauch
>            Assignee: Randall Hauch
>            Priority: Blocker
>             Fix For: 0.4
>
>
> The federation connector currently has a problem when configured to project a non-root node from a single source into the root node of the federated repository.  The cache always has a root node with a specific UUID, and the single source's non-root node has a different UUID, so when the federation connector attempts to project that non-root node from the source into the root node of the federated repository, the cache is unable to store the node with the UUID from the source.
> This problem arose when working on DNA-281 - the test cases were changed to use the InMemory connector rather than the SimpleRepositorySource connector (used for testing only).  The simple implementation didn't maintain UUIDs, whereas the in-memory implementation does.  (This is one of the problems with using a "mock" or non-production implementation in tests.)
> So, although the code compiles, several of the federation connector's tests fail, and the problem also affects several of the JCR unit tests and the Getting Started repository example.  Therefore, after these are fixed, the corresponding projects need to be added back into the POM file.

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