-
Notifications
You must be signed in to change notification settings - Fork 1.5k
NoClassDefFoundError TypedParameterValue when using eclipselink #2857
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
Comments
gregturn
added a commit
that referenced
this issue
Mar 14, 2023
This should also be candidate for backporting to |
gregturn
added a commit
that referenced
this issue
Mar 14, 2023
The Hibernate-specific version can then leverage TypedParameterValue. Resolves #2857.
gregturn
added a commit
that referenced
this issue
Mar 14, 2023
The Hibernate-specific version can then leverage TypedParameterValue. Resolves #2857.
gregturn
added a commit
that referenced
this issue
Mar 14, 2023
The Hibernate-specific version can then leverage TypedParameterValue. Resolves #2857.
gregturn
added a commit
that referenced
this issue
Mar 14, 2023
The Hibernate-specific version can then leverage TypedParameterValue. Resolves #2857.
gregturn
added a commit
that referenced
this issue
Mar 14, 2023
The Hibernate-specific version can then leverage TypedParameterValue. Resolves #2857.
gregturn
added a commit
that referenced
this issue
Mar 14, 2023
This allows the Hibernate variant (HibernateJpaParametersParameterAccessor) to potentially unwrap TypedParameterValue. Resolves #2857.
gregturn
added a commit
that referenced
this issue
Mar 14, 2023
This allows the Hibernate variant (HibernateJpaParametersParameterAccessor) to potentially unwrap TypedParameterValue. Resolves #2857.
klajdipaja
pushed a commit
to klajdipaja/spring-data-jpa
that referenced
this issue
Mar 24, 2023
This allows the Hibernate variant (HibernateJpaParametersParameterAccessor) to potentially unwrap TypedParameterValue. Closes spring-projects#2857 Original pull request spring-projects#2859
klajdipaja
pushed a commit
to klajdipaja/spring-data-jpa
that referenced
this issue
Mar 24, 2023
Renamed to unwrapDate to align with the changes from spring-projects#2861. Minor JavaDoc adjustments See spring-projects#2857 Original pull request spring-projects#2859
klajdipaja
pushed a commit
to klajdipaja/spring-data-jpa
that referenced
this issue
Mar 24, 2023
Removed instanceof assert. See spring-projects#2857 Original pull request spring-projects#2859
klajdipaja
pushed a commit
to klajdipaja/spring-data-jpa
that referenced
this issue
Mar 24, 2023
Reduce method visibility. Improve method naming. Avoid using var in production code. See spring-projects#2857 Original pull request spring-projects#2859
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
we followed this guide (https://www.baeldung.com/spring-eclipselink) to use eclipselink instead of hibernate.
So we have following exclusion in the pom file.
Upgrading spring-boot form 2.7.7 to 2.7.8 i get the following error in one of our tests.
i guess the reason is this older issue #2544
which makes use of a hibernate dependency.
Removing the exclusion for
hibernate-core
makes the code run.But i am unsure about side effects. Is it just excluded to safe some space in the artifact or does it enable some maybe unwanted spring magic by default.
The text was updated successfully, but these errors were encountered: