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>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/main/java/org/onap/aai/spike/SpikeApplication.java b/src/main/java/org/onap/aai/spike/SpikeApplication.java
index 33760de..da9a433 100644
--- a/src/main/java/org/onap/aai/spike/SpikeApplication.java
+++ b/src/main/java/org/onap/aai/spike/SpikeApplication.java
@@ -25,13 +25,13 @@ import org.eclipse.jetty.util.security.Password;
 import org.springframework.boot.autoconfigure.SpringBootApplication;
 import org.springframework.boot.builder.SpringApplicationBuilder;
 import org.springframework.boot.web.servlet.support.SpringBootServletInitializer;
-import org.springframework.context.annotation.Import;
+import org.springframework.context.annotation.ImportResource;
 
 /**
  * Spike service Spring Boot Application
  */
 @SpringBootApplication
-@Import({ EventConsumerConfiguration.class, EventPublisherConfiguration.class })
+@ImportResource({"file:${SERVICE_BEANS}/*.xml"})
 public class SpikeApplication extends SpringBootServletInitializer {
 
     public static void main(String[] args) {