[ https://jira.jboss.org/jira/browse/DNA-188?page=com.atlassian.jira.plugin... ] Randall Hauch commented on DNA-188: ----------------------------------- Needed to add the ability to get the identification properties (e.g., a UUID property) for each child. These properties are required when getting nodes from the original sources so that the merge logic can determine whether child nodes (from different sources) represent the same node or different nodes. These properties are also required in the Federation Connector to obtain the UUID property for each node in the integrated repository cache. The GetChildrenCommand was modified to remove most of the "setChildren(...)" methods and to instead have "addChild(Segment, Property)" methods. The existing connectors were modified to use this new capability. To support storing UUIDs as properties, a UUID property type was added and a new UuidFactory (which extends ValueFactory<UUID>) interface was defined. Each existing factory interface (and implementation) was then modified to add a "create(UUID value)" method. All ValueFactories implementations were modified as well. -- 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

[ https://jira.jboss.org/jira/browse/DNA-188?page=com.atlassian.jira.plugin... ] Randall Hauch commented on DNA-188: ----------------------------------- Added the notion of capabilities to RepositorySource, and added to all RepositorySource implementations. -- 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

[ https://jira.jboss.org/jira/browse/DNA-188?page=com.atlassian.jira.plugin... ] Randall Hauch resolved DNA-188. ------------------------------- Resolution: Done Renamed the StandardMergeStrategy to SimpleMergeStrategy, and fully implemented and tested it to merge multiple contributions. This merge strategy may not be sufficient for many uses, but it works now and does merge properties. Note that while it does not merge any children, it does ensure that any same-name siblings (from all contributions) have the proper indexes. -- 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