Add new seata samples

[xingfudeshi]

Hello Dubbo dev team, I am PPMC from Apache Seata. I have submitted a new Seata example that uses minimal third-party dependencies and can help beginners quickly understand how Seata and Dubbo work together.
Also, later this week, I will submit the PR of the usage documentation for seata to dubbo websites

[wxbty]

Thanks for your pr ，@xingfudeshi， I don't quite understand why the demo needs to be completely replaced. The existing one looks simple enough, can you list some?

[xingfudeshi]

Hi, @wxbty
The seata community received an email from the dubbo community, hoping that we can help update the samples and documents for the upcoming Apache Dubbo 3.3.0. So, I checked the documents and examples of seata that already exist in the dubbo community, and I found some problems. :

1. The document is a bit complicated and contains some repeated information, which is more theoretical.
2. For Dubbo users, they may not be familiar with Seata, so it is necessary that we simplify cases and tutorials to help them quickly experience how Seata and Dubbo work together.

Therefore, I re-wrote a document, and the PR has been submitted here [2], and this sample is matched with that document. This time the document does not rely on any third-party components, and only requires dubbo and seata to complete, I believe It will definitely give users a good experience.

[1]https://lists.apache.org/thread/6853sjp0qxt2rv975fbkhvf4rpo1fsnv
[2]apache/dubbo-website#2906
doc preview:https://deploy-preview-2905--dubbo.netlify.app/zh-cn/overview/mannual/java-sdk/tasks/trasaction/distributed-transaction/
​

[wxbty]

Okay, I've got the background, I will check it later. In addition, if you use dubbo-sample examples, it is recommended that the document add one-click test examples: ./test/run-tests.sh 2-advanced/dubbo-samples-seata. It will start the relevant components and services, start it once, and finally execute the test case

[AlbumenJ]

@slievrly @chickenlj PTAL

[xingfudeshi]

Okay, I've got the background, I will check it later. In addition, if you use dubbo-sample examples, it is recommended that the document add one-click test examples: ./test/run-tests.sh 2-advanced/dubbo-samples-seata. It will start the relevant components and services, start it once, and finally execute the test case

Ok.I'll do that.

[wxbty]

@xingfudeshi Please refer to the original example to restore the two files case-configuration.yml and case-versions.conf. The example of dubbo-sample not only allows users to manually execute unit tests, but also is the source of automatic integration testing for dubbo main repository workflow. Automatic testing requires One-click testing, this is the role of case-configuration.yml. And case-versions.conf can help us test the dependencies of the specified version matrix

[xingfudeshi]

@xingfudeshi Please refer to the original example to restore the two files case-configuration.yml and case-versions.conf. The example of dubbo-sample not only allows users to manually execute unit tests, but also is the source of automatic integration testing for dubbo main repository workflow. Automatic testing requires One-click testing, this is the role of case-configuration.yml. And case-versions.conf can help us test the dependencies of the specified version matrix

Done.

[wxbty]

[root@VM-16-12-centos dubbo-samples]# ./test/run-tests.sh 2-advanced/dubbo-samples-seata/

[wxbty]

What about changing to java8 version? Java17 seems to have a problem with the old seata-sample, and the test is ignored during execution.

[xingfudeshi]

What about changing to java8 version? Java17 seems to have a problem with the old seata-sample, and the test is ignored during execution.

Ok.I'll take a look on it.

[xingfudeshi]

I have been trying for a long time but still cannot succeed. Please help me check where the problem is
It seems to be a network issue in the Docker environment. I'm not sure if it's because I'm using Multicast. Please take a look at my code.

dubbo:
    application:
        logger: slf4j
        name: ${spring.application.name}
        qos-enable: false
    registry:
        address: multicast://224.5.6.7:1234
    protocol:
        port: 20881
        name: dubbo

I don't want to introduce any extra middleware to increase the time cost of user experience data, so I use Multicast as the registry.

[xingfudeshi]

[xingfudeshi]

I can run these samples through a regular spring boot application without any problem

[xingfudeshi]

I've figured it out, the previous issue was due to some mistakes.Now the test has passed.

[wxbty]

On my server, it also passed the test and there seems to be no problem. @AlbumenJ PTAL again

[wxbty]

LGTM

[AlbumenJ]

@xingfudeshi PTAL