SpringBoot Multiple AutoConfiguration exclusions defined at startup

Question

I work on a corporate Spring Boot extension that autoconfigures its own RabbitMQ clients. This extension (a starter) replaces the Spring Boot RabbitAutoConfiguration.

I know there are many ways to disable the RabbitAutoConfiguration :

• in each Application (main) class with @EnableAutoConfiguration(exclude = RabbitAutoConfiguration.class) or @SpringBootApplication(exclude = RabbitAutoConfiguration.class)
• in the application.properties or yml file (externalized or within the jar), with spring.autoconfigure.exclude=org.springframework.boot.autoconfigure.amqp.RabbitAutoConfiguration

I wonder if there is a way that the presence of my new starter disables the Spring Boot RabbitAutoConfiguration.

I tried some dirty things, such as putting an application.properties with the exclude property in the corporate starter module, but as Spring Boot only reads one in the classpath, it can be easily overriden by one used in a client application. I do not want to impose some restrictions.

I do not like the idea of each application adding the same exclusion one way or the other (properties or annotation).

Any ideas ?

EDIT

I need to configure several RabbitMQ ConnectionFactory and RestTemplate within the same application.

Answer 1

If you want to truly replace the standard RabbitAutoConfiguration by yours, you just need to add @AutoconfigureBefore(RabbitAutoConfiguration.class) on your own auto-configuration to teach Spring Boot to process yours before the standard one.

If it is a replacement, yours will register beans that the standard auto-configuration will detect and it will back-off the same way as if you would have defined them manually.

Having said that, why are you doing this? I'd rather complement the existing auto-configuration rather than replacing the standard one. Is there a problem with the standard one? If so, we'd love to hear about it and adapt the code so that you don't have to fully replace it.