Spring Data JPA @Lock Annotation #35891
Labels
Comments
|
/cc @geoand (spring) |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 13, 2023
|
I added a note in #35899 but I will keep this issue open as it definitely makes sense as a feature request |
geoand
added a commit
that referenced
this issue
Sep 13, 2023
Add note about unsupported @lock in Spring Data JPA
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 19, 2023
Relates to: quarkusio#35891 (cherry picked from commit 4c15e55)
aloubyansky
pushed a commit
to aloubyansky/quarkus
that referenced
this issue
Oct 25, 2023
Relates to: quarkusio#35891 (cherry picked from commit 4c15e55)
holly-cummins
pushed a commit
to holly-cummins/quarkus
that referenced
this issue
Feb 8, 2024
gsmet
added
kind/enhancement
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The
org.springframework.data.jpa.repository.Lockannotation isn't included withquarkus-spring-data-jpa. It isn't listed under What Is Currently Unsupported on the Quarkus Spring Data JPA Extension page so filing it as a bug instead of a feature request. There are obvious workarounds but with their own drawbacks, supporting the annotation would be strongly preferred for our use cases. For example, sharing a library that uses Spring Data JPA between Quarkus and non-Quarkus applications.Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -aorverNo response
Output of
java -versionNo response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --versionorgradlew --version)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: