summaryrefslogtreecommitdiffstats
path: root/src/main/java/org/onap/dcae/commonFunction/DmaapPublishers.java
AgeCommit message (Collapse)AuthorFilesLines
2018-07-02Prepare codebase for dynamic DMaaP configurationPawelSzalapski1-91/+0
From now on, there is only one single place where we can create whole app core concerning sending events and it has a single entry point, based on DMaaP configuration. It can be used to rebuild part of app that is responsible for sending events dynamically. Changes are in scope for the dynamic DMaaP config feature. + bumped up code coverage a bit Change-Id: Iecc8c4e534ae9b781f47e3616409271ba83169c8 Signed-off-by: PawelSzalapski <pawel.szalapski@nokia.com> Issue-ID: DCAEGEN2-517
2018-06-24Remove dead code from VESCollectorPawelSzalapski1-11/+6
Many things there are unused or have inproper modifiers, spelling etc. I run static analysis tool (Intellij code inspect) and clear those things up. It will be easier to maintain now. No actual behavior changes were done. Issue-ID: DCAEGEN2-526 Signed-off-by: PawelSzalapski <pawel.szalapski@nokia.com> Change-Id: I1a4ad0c896bd32165cba654344ffc5245648c615
2018-04-12Optimize and refactor EventPublisher class in VESPiotr Jaszczyk1-0/+96
* Remove need for having sendEvent synchronized by means of using Guava LoadingCache. The only thing that made it synchronized was the creation of new entries in the map but the synchronization was made on each incoming event. * Split the class to smaller classes which conform to SRP. This makes us able to... * ... write unit tests for affected classes * TODO: upgrade to Java8 so lambdas will simplify the code even more Change-Id: I14cf4cfab0570ce5aecc9a5e5dc9f541c499f9d7 Issue-ID: DCAEGEN2-440 Signed-off-by: Piotr Jaszczyk <piotr.jaszczyk@nokia.com>