Allow separate stacks registration through services operation
authorEduardo Ramos Testillano (eramedu) <eduardo.ramos.testillano@ericsson.com>
Fri, 15 May 2020 15:06:16 +0000 (17:06 +0200)
committerEduardo Ramos Testillano (eramedu) <eduardo.ramos.testillano@ericsson.com>
Fri, 15 May 2020 15:13:47 +0000 (17:13 +0200)
commit3753f8bd8025131cc0b62da8942daefc376c1c46
treeff0dbe48ce89011a166eaf41744744befc8da2f4
parentceba287089c374f877a3045aece2f0d0bf653d84
Allow separate stacks registration through services operation

Until now, stacks could not be delta-loaded. All the stacks might be
loaded in a unique single xml file (or xml representation through
rest api). This was due to counterscope initialization restriction:
once a counter was registered (due to event received), you could not
initialize more counter scopes.

We removed this restriction (now commented on initializeCountersScope).
New scopes() method to know current registered ones in order to put
the correct start point at services load procedure.

The services "node" nodes always could be loaded separately, so, no
impact on functional behaviour for this.

Fixed: https://redmine.teslayout.com/issues/48
example/diameter/launcher/Launcher.cpp
include/anna/core/oam/Module.hpp
source/core/oam/CounterScope.cpp
source/core/oam/Module.cpp