[ https://issues.jboss.org/browse/RTGOV-154?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-154: ---------------------------------- Refactored services (e.g. CacheManager) used by event processor to be available as a common component (RTGOV-214), to enable the active collection predicate to also be able to use it. Add a context parameter supplied to the predicates (used to filter derived active collections) to enable additional active collections and services to be used by the predicate. Current thoughts on solution are: a) have a second active collection (backed by an infinispan cache) to represent the list of components with known issues (i.e. not to be displayed) b) have a derived collection from the current Situations active collection, that will use the new active collection from (a) to filter out the situations that are related to known issues - as the result of the derived collection may change, based on the (a) active collection, we need a way to refresh the derived collection list. This could be achieved a couple of ways: (i) use active notifications from the (a) collection to update the list, but this would require some additional logic to be provided to understand the active notifications and apply the changes (ii) use active notifications to prompt a re-evaluation of the complete derived collection - may be ok in this case, although could generate alot of work if there any many changes to collection (a) (iii) enable the derived collection to be configured as not storing actual results (i.e. just use it as a proxy to generate notifications), and when the list is requested the parent collection is fully evaluated against the predicate - this should be ok if the complete list is only requested periodically. c) update gadget to use the derived Situations collection rather than the full list d) provide a REST service to enable components to be added and removed from the known issues list - possibly also a JMX action To support (b), we also need to pre-configure the derived collection as part of the top level collection's ActiveCollectionSource, and also mark the derived collection as permanent (i.e. it shouldn't be removed when no clients). Currently option (b) (iii) is most likely to be implemented. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira