-
Notifications
You must be signed in to change notification settings - Fork 1.5k
ClassNotFound Exception for org.hibernate.jpa.TypedParameterValue in QueryParameterSetter when using Eclipselink JPA Provider #2902
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
Labels
Milestone
Comments
@gregturn The workaround should be reverted now. Lines 90 to 102 in d64cfd1
|
gregturn
added a commit
that referenced
this issue
Apr 28, 2023
Hibernate resolved hibernate/hibernate-orm#5438, allowing us to no longer implement special handling. Resolves #2902.
@quaff I tried removing that block, but it wasn't enough. Check out the linked PR for a proposed solution (feedback welcome). |
schauder
pushed a commit
that referenced
this issue
May 2, 2023
Hibernate resolved hibernate/hibernate-orm#5438, allowing us to no longer implement special handling. Closes #2902 Original pull request #2933
That's fixed by 9dbd41e |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Hi,
after upgrading spring-data-jpa to 2.7.10 (from 2.7.6) I encountered a new Runtime Error when calling a Stored-Procedure.
Class org.springframework.data.jpa.repository.query.QueryParameterSetter has a hard dependency on org.hibernate.jpa.TypedParameterValue and throws a ClassNotFound Exception
Stacktrace:
This issue appears when calling a repository method backed by a stored procedure.
Example:
As far as I can tell, this issue was introduced with d64cfd1, a fix for a hibernate related issue.
The text was updated successfully, but these errors were encountered: