Moduliths Events JPA module not working properly when used with Spring Boot DevTools

Parameter 0 of constructor in org.moduliths.events.jpa.JpaEventPublicationConfiguration required a bean of type ‘org.moduliths.events.jpa.JpaEventPublicationRepository’ that could not be found.

Spring Boot Version 2.4.4, Also tried downgrading to 2.3.10 with no luck.

The following issue solution did not help either: Upgrading to 1.1.0-RC2 solved the issue.

_Originally posted by @igler in https://github.com/odrotbohm/moduliths/issues/166#issuecomment-818947681_

Getting this with all versions of the library when starting my application. Any assistance would be greatly appreciated @odrotbohm

[odrotbohm]

I’ve fixed the issue with DevTools. If you’re not using automatic schema creation with Hibernate, you’d have to take care of the schema creation for the publication table yourself. I guess you can mimic what Hibernate is doing, enable SQL logging in a sample project and just copy the output into a Flyway script or the like for now. I’d like to focus this ticket on the DevTools aspect and mark this resolved. We of course need to improve on the schema creation but that’s likely much more effort as we have to provide this for multiple databases etc., which warrants a new ticket.

Regarding the actual interaction with the database, I’d have to again ask for a reproducing example as “nothing is ever being persisted” can’t really be investigated without one and we have tests and samples (one linked to above), that actually show the interaction happening and the log working.

[odrotbohm]

Let’s tackle this, one by one: if you use @EnableJpaRepositories explicitly, you completely disable Boot’s auto-configuration for JPA and Spring Data JPA repositories. That means that repositories and entities are only picked up from packages you define. Can you try adding org.moduliths.events.jpa to the list of packages you declare explicitly?

Regarding the “non-public interface is not defined by the given loader” I’ll have to investigate. Is DevTools in play here by accident? I’ve experienced the classloader arrangement causing a few issues here and there.