brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BROOKLYN-49) Catalogue should be persisted and used when rebinding
Date Fri, 19 Sep 2014 14:55:34 GMT


ASF GitHub Bot commented on BROOKLYN-49:

Github user aledsage commented on a diff in the pull request:
    --- Diff: core/src/main/java/brooklyn/catalog/internal/ ---
    @@ -53,11 +54,12 @@
         List<CatalogDo> childrenCatalogs = new ArrayList<CatalogDo>();
         CatalogClasspathDo classpath;
         Map<String, CatalogItemDo<?,?>> cache;
    +    Map<String, CatalogItemDo<?,?>> registeredTypeNameCache;
    --- End diff --
    Is the original `cache` key'ed by id? I'd probably prefer names like `cacheById` and `cacheByRegisteredTypeName`.
No strong feelings.
    I'd also make these `private` so we can better reason about what is maintaining the cache.

> Catalogue should be persisted and used when rebinding
> -----------------------------------------------------
>                 Key: BROOKLYN-49
>                 URL:
>             Project: Brooklyn
>          Issue Type: Improvement
>            Reporter: Sam Corbett
>            Assignee: Sam Corbett
> Proposal:
> The catalogue, consisting of application templates, entities, policies and 'configuration'
(whose purpose is unknown to me and is unused in general), will be persisted to a `catalog`
directory alongside enrichers, entities, locations, nodes, plane and policies. Location definitions
(that are conceptually linked but are unrelated in code) will be stored too.
> Modes of operation:
> * If persistence if disabled load the default catalogue;
> * If persistence is enabled but there is no persisted catalogue (i.e. the server is running
for the first time) then load the default catalogue;
> * Otherwise load the persisted catalogue. Do _not_ load the default catalogue. 

This message was sent by Atlassian JIRA

View raw message