Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

seata使用例子可以随之更新吗? #648

Closed
ListenQ opened this issue Mar 18, 2024 · 6 comments · Fixed by apache/incubator-seata-website#852
Closed

seata使用例子可以随之更新吗? #648

ListenQ opened this issue Mar 18, 2024 · 6 comments · Fixed by apache/incubator-seata-website#852

Comments

@ListenQ
Copy link

ListenQ commented Mar 18, 2024

采用seata + springboot + dubbo + mybatis + nacos 的例子,可以更新一下吗?
目前是2019年的老旧版本,随着发布更新一起升级调整下例子就好

期望
seata version:2.0.0
springboot version:2.7.x 及以上
dubbo version:3.1.0 +

@ptyin
Copy link
Member

ptyin commented Mar 18, 2024

We have recently refactored the sample repository by #647.

You can check it here to see if that satisfies your requirements.

@ListenQ
Copy link
Author

ListenQ commented Mar 18, 2024

Okay, thanks.

@ListenQ
Copy link
Author

ListenQ commented Mar 18, 2024

@ptyin
Copy link
Member

ptyin commented Mar 18, 2024

Sure. I will fix that.

Run this file.

@ListenQ
Copy link
Author

ListenQ commented Mar 19, 2024

  1. TC(seata server端)设计及原理可以详细出文档说说吗?
    启动 seata server ,开启mysql log 查看如下图,会一直频繁的刷是什么?
    image

  2. TC 管理界面一直显示信息是为哈?什么原因?
    image
    image

程序console日志如下图,一直重复刷
image

@ptyin
Copy link
Member

ptyin commented Mar 19, 2024

For implementation, you can

  • refer to dev docs for AT implementation details.
  • check blog to search for relevant resources.

I will close this issue. For any unexpected behaviour of Seata, please open a new issue in the main repository and supplement related error logs and version information.

@ptyin ptyin closed this as completed Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants