feature: failureHandler implement can be read from the container

[ph3636]

Ⅰ. Describe what this PR did

FailureHandler implement can be read from the container

Ⅱ. Does this pull request fix one issue?

#2353

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (develop@1d468c4). Click here to learn what that means.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##             develop    #2370   +/-   ##
==========================================
  Coverage           ?   51.81%           
  Complexity         ?     2699           
==========================================
  Files              ?      517           
  Lines              ?    16761           
  Branches           ?     2028           
==========================================
  Hits               ?     8685           
  Misses             ?     7267           
  Partials           ?      809

Impacted Files	Coverage Δ	Complexity Δ
...ommon/src/main/java/io/seata/common/Constants.java	50% <ø> (ø)	1 <0> (?)
...ing/boot/autoconfigure/SeataAutoConfiguration.java	0% <0%> (ø)	0 <0> (?)
...ta/spring/annotation/GlobalTransactionScanner.java	52.12% <100%> (ø)	17 <1> (?)

[zjinlei]

LGTM

[slievrly]

Why not load it from the globalTransactionScanner in starter ?

[ph3636]

Why not load it from the globalTransactionScanner in starter ?

You mean it's more appropriate?
【
@bean
@dependsOn({BEAN_NAME_SPRING_APPLICATION_CONTEXT_PROVIDER})
@ConditionalOnMissingBean(GlobalTransactionScanner.class)
public GlobalTransactionScanner globalTransactionScanner(SeataProperties seataProperties) {
if (LOGGER.isInfoEnabled()) {
LOGGER.info("Automatically configure Seata");
}
FailureHandler customFailureHandler = null;
try {
customFailureHandler = ObjectHolder.INSTANCE.getObject(ApplicationContext.class).getBean(FailureHandler.class);
} catch (NoSuchBeanDefinitionException ignore) {
}
return new GlobalTransactionScanner(seataProperties.getApplicationId(), seataProperties.getTxServiceGroup(), customFailureHandler);
}
】

I think my approach is at the bottom of the way, no matter which way he chooses, it can ensure loading.

[slievrly]

LGTM