passay | Password policy enforcement for Java

By excluding spring-boot-starter-web you did exclude all its dependencies, which are necessary to run a Spring Boot project in a servlet environment. Most notably you did exclude spring-web, which contains most of the classes you find in the error messages.

As its name suggests spring-boot-starter-web isn't centered around Tomcat, only its dependency spring-boot-starter-tomcat is. So you should exclude the latter artifact and include spring-boot-starter-undertow to pull the necessary Undertow dependencies into the project:

I figured it out:

Ok so, for me what worked was a rebuild of the project in Intellij.

Boot 2.3 uses spring-kafka 2.5 by default (and kafka-clients 2.5.0); since you have overridden its prescribed spring-kafka version to 2.6.5, you must override all of the kafka dependencies to match

kafka-clients 2.6.1, kafka-streams 2.6.1 (if you are using them).

If you are using the embedded Kafka broker in tests, there are a bunch of other jars you need. See https://docs.spring.io/spring-kafka/docs/current/reference/html/#update-deps

2.6.x is used by Boot 2.4 and will bring in all the right versions.

Confluent 5.4 uses Kafka 2.4.

You should use the version of confluent that matches Spring Boot's prescribed versions of spring-kafka, kafka-clients.

If you use Boot 2.4.x, use confluent 6.0.

https://docs.confluent.io/platform/current/installation/versions-interoperability.html

As the error suggests, you are annotating (referencing) a non-persistent type within anohter JPA Entity.

The EarthquakeEntity should be the mapped type instead of EarthquakeDto:

I suspect your problem lies with @DBRef. I never used it but based on the documentation, your query will also retrieve Customers from a different collection, the same goes for Menu (i.e. +2 queries for each MenuChoice, not sure how SpringJPA handles it but since MongoDB is NO-SQL I suspect these queries are distinct).

More details at MongoDB - is DBREF necessary?

The reason why the query works so fast in Compass is that these additional queries are not performed whereas SpringJPA also performs the additional queries so you have a complete POJO.

When it comes to improvements you have the following options:

1. Use foreign keys for Menu and Customer and retrieve them as required.
2. Move Customer and Menu into the same collection thus no referencing required.
3. If you wish to use references then MongoDB is a bad fit, consider using relational DBs like Postgre, MySQL, MSSQL, OracleSQL.

In case of 'jar' packaging, by default JAR Plugin looks for 'src/main/resources' directory for the resources and bundled them along with code build (if not configured for custom resource directory etc).

But 'pom' packaging doesn't work this way so application.properties is not included in build if it is not specified with some annotation etc.

Either you can create one more module which can be child to parent pom and parent to rest of modules to share one application.properties across whole project or you can use maven-remote-resources-plugin to use a remote resource bundle

related answers

maven doc

Given the lack of logging output, you may have a problem with some logging related dependencies. For example, a dependency on commons-logging:commons-logging can cause problems and should be excluded in favour of org.springframework:spring-jcl. org.slf4j:jcl-over-slf4j should be treated similarly.

You can learn if you have either of these dependencies on the classpath using Gradle's dependencyInsight task: