Fix keyset pagination with hierarchical idclass

[JBodkin-Amphora]

I've noted a few issues with keyset pagination when using hierarchical idclasses that I believe was introduced when Jakarta Persistence changed the greaterThan/lessThan methods on the criteriabuilder to take a Comparable. I've written some code to extract the attribute paths so that the underlying values can be extracted instead of the entity.

Whilst writing tests for the code, I found that the isNotNull/isNull predicates are being applied the wrong way around. This is covered by the tests.

I've noted that the Eclipse Link tests are now failing, I'm not sure if the technology supports the same hierarchical classes as I'm a Hibernate user. If it doesn't, is there a way to prevent the new repositories/entities being used for those tests?

[JBodkin-Amphora]

Eclipse Link tests are now passing after changes to the entities. Also changed the lookup to loop through the attributes instead of trying to look up by type, as Eclipse Link converts the primitive type to the wrapper type inside the metamodel

[mp911de]

Thanks a lot. Which version of Spring Data JPA is affected for you? (So that we can correctly apply backports).

[JBodkin-Amphora]

I've noted the issue starting when I migrated to Spring Boot v4, which uses the 4.0.x branch in this project.