Is it possible to save Interface based Projections?
Can't see anything in the documentation saying you can't, but getting the following error when I try:
org.springframework.data.mapping.MappingException: Constructor parameter names aren't available,...
Upgraded to Spring Boot 2.3 (from 2.2) and app won't startup due to dependency cycle
Any idea why Neo4jOgmEntityInstantiatorConfigurationBean dependant on WebMvcAutoConfiguration$EnableWebMvcConfiguration?
Have used a NodeEntity interface for loading nodes using a custom findBy repository method and this is working fine with Spring Boot 2.1,
Have just tried using Boot 2.2 (and 2.3) and it now fails with:
Caused by: org.springframework.data.mapping.con...
Have enabled auditing (@EnableNeo4jAuditing) and it appears that after a save the node being saved, and all related (mapped) nodes get last modified updated. This occurs regardless of whether the related nodes have been changed.
Is this the expected ...
Appears multi level projections don't work for class based projections
"These DTO types can be used in exactly the same way projection interfaces are used, except that no proxying happens and no nested projections can be applied."
@gerrit_meier Thanks for the reply. Thats what I had assumed but couldn't find it stated in the doco, so thanks for verifying.
Looking at that example dto you posted I see it uses a multi level projection for mayor, citizens and cityEmployees. I've h...
Yes read through the document.
Interface based projections work fine UNTIL I try and persist changes.
Class based projections allow me to persist.
Spring Data Neo4J 5.3.9 being the version defined by Spring Boot dependencies (spring-boot-starter-data-neo4j 2.3.12). The only version specified is Spring Boot.
I refactored the code to remove the userService dependency which fixed it.
If I get a ch...
@gerrit.meier Thanks for the response. Have fixed it by adding custom queries to the repo methods. Previously it must have been seeing the existence of the property based on getter defined in the interface.
Would a better approach (from a Neo4J pers...