Re-introduce Spring XML based configuration 21/56721/1
authorMichael Arrastia <MArrasti@amdocs.com>
Wed, 18 Jul 2018 10:46:16 +0000 (11:46 +0100)
committerMichael Arrastia <MArrasti@amdocs.com>
Wed, 18 Jul 2018 10:46:16 +0000 (11:46 +0100)
commit04006990b05ec12a1b493848d41b5f0c7eee800f
tree3759978df6e98d296fa78736c8ebe4dd541368ac
parentf3ebf3538abbf63d8455d42f259f61dfdbf6ad30
Re-introduce Spring XML based configuration

This is to retain existing Spring XML based configuration in the
microservice and continue to support switching message bus
implementations through the existing beans XML file resource.

The Java based configuration, though feasible, introduced complexity.
We are going to take the pragmatic approach of handling topic password
de-obfuscation centrally in the event-client.

Change-Id: I1c0ed92cdc155a5d848f94dafedb6c69af88b681
Issue-ID: AAI-1388
Signed-off-by: Michael Arrastia <MArrasti@amdocs.com>
src/main/java/org/onap/aai/spike/EventConsumerConfiguration.java [deleted file]
src/main/java/org/onap/aai/spike/EventPublisherConfiguration.java [deleted file]
src/main/java/org/onap/aai/spike/SpikeApplication.java
src/main/java/org/onap/aai/spike/service/SpikeService.java