Hmm, I did not find a straight forward way to do that based on the sequencing of events that take place for the auto configuration with spring boot.
I ended up having to create a custom bean that got added to the spring container before the JpaProcessEngineAutoConfiguration and JpaProcessEngineAutoConfiguration classes through the use of the @AutoConfigureBefore annotation. This is a bit of a hack.
@Configuration
@AutoConfigureBefore({ JpaProcessEngineAutoConfiguration.class,
JpaProcessEngineAutoConfiguration.JpaConfiguration.class, DataSourceProcessEngineAutoConfiguration.class })
@AutoConfigureAfter(DataSourceAutoConfiguration.class)
public class CustomProcessEngineAutoConfiguration {
It would be nice to see a default strategy approach similar to a lot of the underlying Spring apis that would easily allow devs to hook in a custom strategy.
I might be missing something though. If so, can you point me in the right direction?