bugfix:correct wrong property names in seata-spring-boot-starter.

[xingfudeshi]

Ⅰ. Describe what this PR did

Corret wrong property names in seata-spring-boot-starter.

Ⅱ. Does this pull request fix one issue?

fixes #2114

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

I've done integration testing.

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

[codecov-io]

Codecov Report

Merging #2217 into develop will decrease coverage by 0.24%.
The diff coverage is 50%.

@@              Coverage Diff              @@
##             develop    #2217      +/-   ##
=============================================
- Coverage       54.2%   53.95%   -0.25%     
- Complexity      2623     2624       +1     
=============================================
  Files            489      489              
  Lines          15339    15340       +1     
  Branches        1750     1751       +1     
=============================================
- Hits            8314     8277      -37     
- Misses          6241     6282      +41     
+ Partials         784      781       -3

Impacted Files	Coverage Δ	Complexity Δ
.../rm/tcc/remoting/parser/DefaultRemotingParser.java	0% <0%> (ø)	0 <0> (ø)	⬇️
...gure/provider/SpringBootConfigurationProvider.java	32.85% <100%> (ø)	9 <1> (ø)	⬇️
...o/seata/integration/http/AbstractHttpExecutor.java	53.7% <100%> (ø)	10 <0> (ø)	⬇️
.../java/io/seata/spring/util/TCCBeanParserUtils.java	45.23% <66.66%> (+1.33%)	8 <2> (ø)	⬇️
...eata/integration/motan/MotanTransactionFilter.java	57.14% <0%> (-10.72%)	7% <0%> (ø)
...ion/sofa/rpc/TransactionContextProviderFilter.java	50% <0%> (-10%)	7% <0%> (ø)
...obuf/convertor/BranchRegisterRequestConvertor.java	100% <0%> (ø)	3% <0%> (ø)	⬇️
...otobuf/convertor/BranchReportRequestConvertor.java	100% <0%> (ø)	3% <0%> (ø)	⬇️
...obuf/convertor/BranchRollbackRequestConvertor.java	100% <0%> (ø)	3% <0%> (ø)	⬇️
...java/io/seata/tm/api/DefaultGlobalTransaction.java	65.55% <0%> (-7.78%)	19% <0%> (ø)
... and 38 more

[slievrly]

I think you need to modify the SpringBootConfigurationProvider#convertDataId, convert the configuration items - to Camel style configuration. This pr will conflict with #2182 .

[xingfudeshi]

These changes correspond to the structure in file.conf, where each {} is a properties class.

[xingfudeshi]

And the data id conversion is required only if the properties in the properties class are read.

[xingfudeshi]

TestName and test-name are equivalent when reading a configuration item in spring boot.

[slievrly]

Such as there is a seata. client. aaa-bbb properties of configuration items, you create a new ClientPro class reads seata. client prefix projected into aaaBbb attributes in class, this is no problem springboot automatically. However, the configuration used in our program is client.aaa-bbb, which intercepts the getConfig method through spring boot starter. First, the dataId is standardized. If there is no special processing, the requested dataId is changed into "seata.client. aaa-bbb". In this case if aaa-bbb doesn't do the camel formatting to reflect the above property class you can't find the aaa-bbb property, right? The class that exists is aaaBbb.

[xingfudeshi]

Such as there is a seata. client. aaa-bbb properties of configuration items, you create a new ClientPro class reads seata. client prefix projected into aaaBbb attributes in class, this is no problem springboot automatically. However, the configuration used in our program is client.aaa-bbb, which intercepts the getConfig method through spring boot starter. First, the dataId is standardized. If there is no special processing, the requested dataId is changed into "seata.client. aaa-bbb". In this case if aaa-bbb doesn't do the camel formatting to reflect the above property class you can't find the aaa-bbb property, right? The class that exists is aaaBbb.

fixed.

[slievrly]

LGTM

[l81893521]

LGTM