d2bc2530cc
Migrating to use ApplicationContextRunner or ImportAutoConfiguration with SpringApp.run, instead of SpringApplicationBuilder, because builder does not handle AutoConfiguration properly SimpleTaskAutoConfiguration now has an annotation AutoConfigureBefore the BatchTaskAutoConfig so that it is processed prior. THis is so that that BatchTaskAutoConfig can create the appropriate beans SimpleTaskAutoConfiguration has new annotations so that it is AutoConfigured after BindingServiceConfiguration and after SimpleTaskAutoConfiguration. This is so that it does not attempt to start emitting messages before stream is ready and it can create the appropriate beans after SimpleTaskAutoConfiguration has run. Renamed SimpleTaskConfiguration to SimpleTaskAutoConfiguration. Task version updated to 2.1.0 Added missing headers Updated documentation. Deprecated EnableTask Added ability to disable Task autoconfiguration. Removed @EnableTask from tests Resolves #439 Resolves #440 Resolves #448 Resolves #466
= Multiple DataSources Sample Task This is a Spring Boot application that utilizes two DataSources and explicitly configures which one to be used for the Spring Cloud Task repository. == Requirements: * Java 8 or Above == Classes: * `MultipleDataSourcesApplication` - the Spring Boot Main Application. * `SampleCommandLineRunner` - the `CommandLineRunner` implementation for this task. It outputs the number of `DataSource` beans found in the context (should be 2). * `DataSourceConfiguration` - Configures two `DataSource` beans. * `CustomTaskConfigurer` - Uses a Spring `@Qualifier` to specify the correct `DataSource` to use. == Build: [source,shell,indent=2] ---- $ mvn clean package ---- == Run: [source,shell,indent=2] ---- $ java -jar target/multiple-datasources-2.0.0.RC1.jar ----