Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
As the simulator now resides in policy-models, the code for it is
no longer needed in apex-pdp. Deleted it.
Issue-ID: POLICY-2676
Change-Id: I8ae6c8d860a47e5e7ba0509c99e4e2676109de25
Signed-off-by: Jim Hahn <jrh3@att.com>
|
|
Added logging to handle file io boolean returns
Added security related settings to xml factories and builders
Issue-ID: POLICY-2654
Change-Id: Ibc0a01f978bfc446e1dc1f8ad952d1305a7b7178
Signed-off-by: ToineSiebelink <toine.siebelink@est.tech>
|
|
Change-Id: I0da222e592e6e29f0afca4a1515d8f126fe91cbb
Issue-ID: POLICY-2623
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
|
|
This change is basically a rollback of https://gerrit.onap.org/r/c/policy/apex-pdp/+/104230, with minor refactoring.
The problem that 104230 tried to address was supposed to be caused by https://jira.onap.org/browse/POLICY-2463.
With this rollback, apex-pdp increases performance and reduces memory usage.
Issue-ID: POLICY-2572
Signed-off-by: huaxing <huaxing.jin@est.tech>
Change-Id: I3a52d0ead0c1e530d218f9e3aba8b3eb5558abaf
|
|
Signed-off-by: Henry.Sun <henry.a.sun@est.tech>
Change-Id: Ieceb3e129620ced23552027e71fd09a2bd91acbe
Issue-ID: POLICY-2649
|
|
|
|
We should use the managed version of jackson from policy-parent rather
than a specific apex-pdp version.
Also upgrade the version of Avro, avro 1.9.2 uses a newer somewhat more
secure version of Jackson.
Issue-ID: POLICY-1508
Change-Id: If32218816ae76cf3cf6ddc8980e3a37e7e2ffd19
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
Issue-ID: POLICY-2387
Change-Id: I6d9222cfe8841a4a4532d95dbc6f8b3f3d15ac87
Signed-off-by: RossC <ross.carter@est.tech>
|
|
Issue-ID: POLICY-2188
Change-Id: I56bbf3aa3bd9e1ef433cc93ad2be0c54d141a2a5
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
|
|
Change-Id: I0c15bb6bddb00f5d1fa00ea48e570bc7c270c43d
Issue-ID: POLICY-2627
Signed-off-by: a.sreekumar <ajith.sreekumar@bell.ca>
|
|
Issue-ID: POLICY-2630
Signed-off-by: huaxing <huaxing.jin@est.tech>
Change-Id: I6475f9272c1a770836af537c13b23e486b66ac3e
|
|
|
|
Issue-ID: POLICY-2457
Signed-off-by: aditya.puthuparambil <aditya.puthuparambil@est.tech>
Change-Id: Id47155d172f2b6386c94470dd5068ee09d2a8238
|
|
Issue-ID: POLICY-2319
Change-Id: I0699b2d2791e07df89b7a1e9c78320ced3c14f26
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-2514
Change-Id: I764cfe41ed8cf8ffebd4ff076d0b76b79d61e142
Signed-off-by: RossC <ross.carter@est.tech>
|
|
Issue-ID: POLICY-2514
Change-Id: I5b130b052150eb0e51759c751b83ab9d6f199759
Signed-off-by: RossC <ross.carter@est.tech>
|
|
Issue-ID: POLICY-2514
Change-Id: I6dbdc5057a944792372ebcd02fe30f97fe7b6686
Signed-off-by: RossC <ross.carter@est.tech>
|
|
Issue-ID: POLICY-2514
Change-Id: If247d2ea6d7aabe5c82776ddf46ddf623247cc13
Signed-off-by: RossC <ross.carter@est.tech>
|
|
|
|
Issue-ID: POLICY-2514
Change-Id: I76b58cd69dcba6010867a583edb1b844eeec20d4
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
In the Web Socket unit test, sometimes the server does not start quickly
enough and is not available when the wek socket client connects. This
review changes the unit test to wait for up to 2 seconds for the web
socket server to come up.
Issue-ID: POLICY-2571
Change-Id: I0c970783f368d691d07683bad0cdc28b681e5334
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
If the port specified in the allocateAddress() is occupied, the method
returns the next highest available port. The unit test is changed to
reflect this behaviour.
Issue-ID: POLICY-1916
Change-Id: I02f63476d5f8f3ef2b2363afb3e23de04264e810
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
Issue-ID: POLICY-1916
Change-Id: Ie7cafa16ce12ca542a4e76307caddb36b7753990
Signed-off-by: RossC <ross.carter@est.tech>
|
|
Issue-ID: POLICY-1916
Change-Id: Ie3d1c33648e7996ac063bbaac6ea11f3df03564b
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Issue-ID: POLICY-1916
Change-Id: I4bd93d72f234e1ce572b11bcb0621078480e061b
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
Glassfish security fix in parent, also fixes in common/models
Issue-ID: POLICY-2510
Change-Id: Id5186d4e2610a56db6ef66be62b4cc5177018c68
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
|
|
Change-Id: Ic668ab20498bdc41edc78f52c7ce9d89a1385f19
Issue-ID: POLICY-2378
Signed-off-by: a.sreekumar <ajith.sreekumar@est.tech>
|
|
Issue-ID: POLICY-2378
Change-Id: I0d3d2733083b50dc4b0f5e8126e7014d4ef97a4d
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-1913
Signed-off-by: huaxing <huaxing.jin@est.tech>
Change-Id: Id1a9a6b6f7a9c8c74dd69bd0d30af05162a92cd1
|
|
Issue-ID: POLICY-2378
Change-Id: I7b966eca01f8baf0be3461b33efb8faaf12eb29c
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
|
|
Issue-ID: POLICY-2378
Change-Id: I3d4ef6b6b8f61c0af23676189c9bf6eec529e3f3
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-1913
Signed-off-by: aditya.puthuparambil <aditya.puthuparambil@est.tech>
Change-Id: Ie6dccc50ad63c5fdca1e79d7985aec2455041b56
|
|
Fix for naming policy and yaml string conversion.
Issue-ID: POLICY-2486
Change-Id: I1fc63ab7fdde63c5555d0bae784aee1309f7f8c3
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-2378
Change-Id: I219f1ba6c816166c98346df47a68d21b9736b6b5
Signed-off-by: Pamela Dragosh <pdragosh@research.att.com>
|
|
Issue-ID: POLICY-2446
Signed-off-by: huaxing <huaxing.jin@est.tech>
Change-Id: I1bc45367884ec78436a97256ac4286ab79c8a6b7
|
|
The Web Socket server is marked as started before the start process has
complted. This change fixes that issue.
Issue-ID: POLICY-1470
Change-Id: I5b5ef5832893d884a6551b0516df91cb71d6c622
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
When consumers and producers are paired as in the case of the REST
Rquestor, both sides must come up and be wired together in the
initiation phase of apex-pdp before the consumers and producers start
handling envents.
In the ApexActivator class, the consumers were started immediately after
they were initialized meaning that a consumer could return events to a
producer that had not started yet.
This change fixes the ApexActivator so that it waits until all consumers
and producers are initialized before starting event handling.
It also fixes the timings on RestRequestor tests and tidies up the unit
tests.
Issue-ID: POLICY-2469
Change-Id: Ib66d9531bf21f2a879ab33795aded4f48e7bfbc6
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
|
|
Issue-ID: POLICY-2467
Change-Id: Iea562574f466775f4dd443fc4ef9ecaa6ba610fd
Signed-off-by: Ram Krishna Verma <ram_krishna.verma@bell.ca>
|
|
All the Kafka components need something near 10 seconds to come up
completely. This review tweaks the timing to allow the test Kafka server
to come up and to allow the consumers to connect to it.
Issue-ID: POLICY-2106
Change-Id: I6dd8ace0848bdc2549e658ef8908b4d85d5ea789
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
|
|
|
|
Issue-ID: POLICY-2106
Change-Id: I7bd44f8dfe349d73a4c8c4f978a30b455c45b2c7
Signed-off-by: liamfallon <liam.fallon@est.tech>
|
|
Issue-ID: POLICY-2445
Signed-off-by: huaxing <huaxing.jin@est.tech>
Change-Id: I7fda1961e95b1f18da6c0e22c7799195fc511443
|
|
Issue-ID: POLICY-1122
Signed-off-by: aditya.puthuparambil <aditya.puthuparambil@est.tech>
Change-Id: I552b58f39325982f1e26e59b352dfbe70cf35e7c
|