• Stephane Nicoll's avatar
    Fix order of JMS auto configuration · 630c1456
    Stephane Nicoll authored
    Add additional @AutoConfigureAfter elements to ActiveMQAutoConfiguration
    and HornetQAutoConfiguration to ensure that they are configured after
    JndiConnectionFactoryAutoConfiguration.
    
    The possible sources for a JMS ConnectionFactory are:
    
    1. JNDI
    2. HornetQ (embedded broker or an external broker)
    3. ActiveMQ (embedded broker or an external broker)
    
    The last two auto configurations must run after JTA auto-configuration
    has completed as it may register additional beans that are necessary to
    enable XA.
    
    Previously, the HornetQ embedded broker would start regardless of the
    presence of a ConnectionFactory as a ConditionalOnMissingBean was
    missing. Furthermore, there was no order condition for the JNDI
    auto-configuration so it may just run after one of the broker has been
    found.
    
    JNDI takes now precedence to be consistent with the regular DataSource
    auto configuration.
    
    Fixes gh-1821
    630c1456
Name
Last commit
Last update
docs Loading commit data...
eclipse Loading commit data...
spring-boot Loading commit data...
spring-boot-actuator Loading commit data...
spring-boot-autoconfigure Loading commit data...
spring-boot-cli Loading commit data...
spring-boot-dependencies Loading commit data...
spring-boot-docs Loading commit data...
spring-boot-full-build Loading commit data...
spring-boot-integration-tests Loading commit data...
spring-boot-parent Loading commit data...
spring-boot-samples Loading commit data...
spring-boot-starters Loading commit data...
spring-boot-tools Loading commit data...
spring-boot-versions Loading commit data...
.gitignore Loading commit data...
.settings-template.xml Loading commit data...
.travis.yml Loading commit data...
CONTRIBUTING.adoc Loading commit data...
README.adoc Loading commit data...
pom.xml Loading commit data...