[ http://jira.jboss.com/jira/browse/DNA-115?page=comments#action_12416861 ] Randall Hauch commented on DNA-115: ----------------------------------- My latest thought is that the federation engine needs to maintain a single integrated repository (with persistent storage) that contains the merged information, unique identifiers (w/r/t the federated graph), and "provenance information" (basically, a record of from which source all of the property values and children came). This can be accomplished in the federation engine by using any RepositorySource (that supports updates and transactions?) and storing on each node the merged properties, merged child references, federated UUID, source-specific properties (e.g., source UUIDs, source paths, etc.), a merge plan that defines the mapping of the source information into the merged/federated node (including cache policy information), and the shortest TTL of the individual source TTL values. The latter enables the engine to quickly determine if the federated node contains any expired information; if not, it can continue using it. If something has expired, then the merge plan must be obtained and processed to determine which subset of the information is expired. These federation-specific properties (e.g., federated UUID, shortest TTL, merge plan, cache information, contributing sources, etc.) can be stored as normal properties using a specific federation namespace. These federation-specific properties would normally be excluded from the public view, but could be accessed via specific commands (e.g., "GetFederationDetailsForNodeCommand"). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/DNA-115?page=comments#action_12419539 ] Randall Hauch commented on DNA-115: ----------------------------------- Added more tests for FederationService, including tests for those methods that read the configuration repository. To allow the configuration of a FederatedRepository to be updated in a concurrent environment, the configuration-related information (regions, default cache policy) was pulled into a separate FederatedRepositoryConfig object. A FederatedRepository's configuration can therefore be replaced wholesale. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/DNA-115?page=com.atlassian.jira.plugin... ] Randall Hauch commented on DNA-115: ----------------------------------- Moved the federating functionality into a separate connector and out of 'dna-repository'. This cleans up the 'dna-repository' project and also makes it easier to assemble and (re)use the federation capability in different parts of the system. -- 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-115?page=com.atlassian.jira.plugin... ] Randall Hauch commented on DNA-115: ----------------------------------- Added some exception handling in FederatedRepositorySource to better explain a ClastCastException when looking up objects out of JNDI. -- 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-115?page=com.atlassian.jira.plugin... ] Randall Hauch resolved DNA-115. ------------------------------- Resolution: Done Closing this issue, as the minimum functionality is there to do federation. More work will need to be done on additional merge strategies, but that requires a review and changes to better handle node identification (when getting children, for example). This work will all be tracked with other issues. -- 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