diff options
| author |   Jim Hahn <jrh3@att.com> | 2020-02-20 09:40:14 -0500 |
|---|---|---|
| committer | Jim Hahn <jrh3@att.com> | 2020-02-20 16:29:08 -0500 |
| commit | 467247c7970f9ae83464d78929ed970bbf03c593 (patch) | |
| tree | 54b78e6505b664c3a61e532bf6f7c276307d6591 /models-interactions/model-actors/actor.so/src/test/resources | |
| parent | f6da7772d9dc01ce4ddd21a55b0f1c5fb7ad814f (diff) | |
More actor clean-up
Currently, Operator classes refer to Operation classes, and
vice versa, creating a dependency cycle. In addition, there is
a slight problem in that if an operator is reconfigured, any
running operation may get inconsistent configuration data.
Modified the code to create Config objects that are passed to
the operation, instead of passing the Operator to the operations.
This solved both issues.
Replaceed makeOperator() with constructors.
Added parameter type to HttpActors.
Modified guard to get "ONAP" properties from its configuration,
as a default.
Changed setUp() to setUpBasic(), so "throws Exception" could be
removed, thus resolving a sonar issue.
Issue-ID: POLICY-1625
Signed-off-by: Jim Hahn <jrh3@att.com>
Change-Id: I21eb8798acfbc636ff1bd8741b21c7278365b6e4
Diffstat (limited to 'models-interactions/model-actors/actor.so/src/test/resources')
0 files changed, 0 insertions, 0 deletions