[dna-issues] [JBoss JIRA] Commented: (DNA-451) RepositoryService should dynamically keep its RepositorySource instances in sync with changes to the configuration repository

[ https://jira.jboss.org/jira/browse/DNA-451?page=com.atlassian.jira.plugin... ] Randall Hauch commented on DNA-451: ----------------------------------- The RepositoryLibrary and RepositoryService classes were changed so that the RepositoryService now behaves as an Observer for changes to the content in the configuration source. If the configuration content changes, RepositoryService attempts to update the RepositorySource instance(s) that correspond to the changed content. Of course any removed content for a repository source causes the corresponding RepositorySource object to be removed. RepositoryService does not own the RepositorySource for the configuration, so it cannot register as a listener on its own. Instead, RepositoryService is now an Observer, it must be registered appropriately to receive the events; this is usually done by the code that owns the configuration RepositorySource. In the case of DnaEngine, this was done by using a (new) ObservationBus class (which allows multiple observers on the bus, but the bus is itself an observer so that we have the multiplexing behavior) registered to receive events from the configuration RepositorySource, and to register RepositoryService as an observer on the bus. -- 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