Fix duplicate bean exceptions after spring-boot 3.2 update 04/143104/1
authorFiete Ostkamp <fiete.ostkamp@telekom.de>
Tue, 3 Feb 2026 09:50:03 +0000 (10:50 +0100)
committerFiete Ostkamp <fiete.ostkamp@telekom.de>
Tue, 3 Feb 2026 09:50:03 +0000 (10:50 +0100)
commitc2434b9be6c8befbaa964ecfbade22b4ae98ef32
tree7864ddded800fd55ec0fb2bd1e999986cb705d6b
parent8cf145991dac94acb78c697b35399c5062f710c6
Fix duplicate bean exceptions after spring-boot 3.2 update

- spring-boot 3.2 seems to be stricter as to how beans may be declared
- to avoid DuplicateBeanExceptions, @Component and @Service annotations
  are removed from some classes in favor of solely relying on their
  @Bean declarations in @Configuration classes

Issue-ID: AAI-4223
Change-Id: I4bb53680bc86f4ff34a6c32d9273c69b34f5ba1d
Signed-off-by: Fiete Ostkamp <fiete.ostkamp@telekom.de>
aai-core/src/main/java/org/onap/aai/kafka/DeltaProducer.java
aai-core/src/main/java/org/onap/aai/kafka/DeltaProducerService.java
aai-core/src/main/java/org/onap/aai/kafka/NotificationProducer.java
aai-core/src/main/java/org/onap/aai/kafka/NotificationProducerService.java
aai-schema-ingest/src/main/java/org/onap/aai/config/ConfigConfiguration.java
aai-schema-ingest/src/main/java/org/onap/aai/setup/SchemaConfigVersions.java