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

WebSockets Next: follow the rule of Quarkus REST for Transactional annotation #44495

Closed
mkouba opened this issue Nov 14, 2024 · 0 comments · Fixed by #44498
Closed

WebSockets Next: follow the rule of Quarkus REST for Transactional annotation #44495

mkouba opened this issue Nov 14, 2024 · 0 comments · Fixed by #44498
Labels
Milestone

Comments

@mkouba
Copy link
Contributor

mkouba commented Nov 14, 2024

Description

It seems that Quarkus REST has a specific rule for @Transactional: "If a method or class is annotated with jakarta.transaction.Transactional then it will also be treated as a blocking method. This is because JTA is a blocking technology, and is generally used with other blocking technology such as Hibernate and JDBC.".

Implementation ideas

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant