Open njr-11 opened 7 months ago
See EclipseLink Issue : 2195
FYI @njr-11 @Riva-Tholoor-Philip
I was unable to recreate. I also un-commented and ran the original test and it works from Jakarta Data as well. Perhaps this bug was fixed in one of the beta versions of EclipseLink we have upgraded too?
My recreation attempt: https://github.com/KyleAure/open-liberty/commit/1483d53229d4e8898066114fb2ff1b9b014bc2bf
I was unable to recreate. I also un-commented and ran the original test and it works from Jakarta Data as well. Perhaps this bug was fixed in one of the beta versions of EclipseLink we have upgraded too?
Oh, I didn't realize it worked via Jakarta Data now, too. Then yes, EclipseLink must have fixed it already. I just tried it locally as well and given that worked, and I requested a build to confirm that its working there as well. I set up the PR to automatically close this issue.
When I attempted to re-enable this under #29200 I discovered that it's an intermittent issue that appears to happen when the test testEmbeddedId
, which uses the same entity, runs first.
Thanks @njr-11
Reopening issue. The PR accidentally automatically closed this, it is still an issue that needs to be resolved.
remove release:24.0.0.9 label (this OLGH is incorrectly in the fix pack metadata)
Describe the bug
The JPQL query
SELECT o FROM Account o WHERE (o.accountId=?1)
fails when supplied with anAccountId
that is an embeddable id for the entity.EclipseLink converts this to SQL:
SELECT BALANCE, BANKNAME, CHECKING, OWNER, ACCOUNTNUM, ROUTINGNUM FROM WLPAccount WHERE ((ACCOUNTNUM = ?) AND (ROUTINGNUM = ?))
which looks fine, but it gets an error processing the result:NullPointerException: Cannot read field "index" because "key" is null
.Steps to Reproduce
Uncomment these lines of code and run the test:
https://github.com/OpenLiberty/open-liberty/blob/8fdfcb7f06624d098f4170de68f1bb926e90ae8b/dev/io.openliberty.data.internal_fat_jpa/test-applications/DataJPATestApp/src/test/jakarta/data/jpa/web/DataJPATestServlet.java#L2048-L2053
Expected behavior
JPQL query should succeed and return the data.
Diagnostic information:
Additional context
Add any other context about the problem here.