Skip to content

Fix persistence config and POM dependency issues

Daniel Gerhardt requested to merge fix-persistence-dependency-issues into 2-implement-as-reactive-pattern

This MR fixes:

  • the persistence configuration for R2DBC
  • the Maven dependency configuration

I haven't tested if the backend is working correctly but at least it starts up w/o exceptions and R2DBC related log entries look good:

2020-05-15 23:08:48.140  INFO 7651 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode!
2020-05-15 23:08:48.140  INFO 7651 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data R2DBC repositories in DEFAULT mode.
2020-05-15 23:08:48.189  INFO 7651 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 46ms. Found 5 R2DBC repository interfaces.

I removed the r2dbcDatabaseClient bean definition because I expect Spring's auto configuration magic to do its thing (but I'm not sure if it really does it is fine).

Furthermore, the JPA is not reactive and does not work with R2DBC. Entities used some JPA annotations which had to be migrated to Spring Data annotations.

Spring Data R2DBC does not yet support composite keys. Entities which used composite keys need to be refactored.

Related: #2 (closed)
See: https://github.com/spring-projects/spring-data-r2dbc/issues/158

Edited by Daniel Gerhardt

Merge request reports