Federated repository is not properly handling/merging paths above where a source is being projected --------------------------------------------------------------------------------------------------- Key: DNA-225 URL: https://jira.jboss.org/jira/browse/DNA-225 Project: DNA Issue Type: Bug Components: Examples, Federation Affects Versions: 0.2 Reporter: Randall Hauch Assignee: Randall Hauch Priority: Critical When a source is federated, the configuration must specify how that source is to be projected into the federated repository. For example, the root of a "Cars" repository might be projected into the federated repository at "/Vehicles". Thus, the "Vehicles" node in the federated repository must exist because of the federated source. If multiple sources are projected into overlapping (or matching) paths, then the federated connector is not properly merging them. Using the above example, consider another "Airplanes" repository that is also projected into the federated repository at "/Vehicles". There should only be one "Vehicles" node, but the federated connector is at present creating one "Vehicles" node for each projection. This is incorrect, and the "Vehicles" nodes must be merged (since they only exist to get to where the nodes being projected from the sources). This problem exists in the "repository" example ("docs/examples/gettingstarted/repositories") of the Getting Started document. -- 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