Troubleshooting¶

Healthchecks¶

Problem: The beadledom-health module has a dependency on com.github.spullara.mustache.java:compiler:0.9.0. Some older versions of com.github.spullara.mustache.java:compiler do not have support for Java 8 which beadledom health needs. Not having Java 8 support would result in Optional fields not being unwrapped properly.
Suggested solution: Add an explicit dependency on version 0.9.0 of the com.github.spullara.mustache.java:compiler dependency

Problem: What this usually telling you is that you have a scala version mismatch (Scala classes from 2.10 and 2.11 or 2.11 and 2.12 etc.). The best way we have found to resolve these inconsistencies is to do mvn dependency:tree -Dincludes:scala-library:: and search the output for anything containing the unwanted version of Scala. For instance scalatest_2.10 if you were using Scala 2.11.

Problem: Beadledom clients are automatically generated from API resources annotated with JAX-RS and Swagger annotations. API definitions from clients used in a service is getting merged with the service definition.
Suggested solution: Make your service module a private module, and expose only your server resources. In another module install ResteasyModule and bootstrap all the configurations needed for resteasy. In your ResteasyContextListener class install your service module and ResteasyBootstrapModule.
Alternative solution: Have client owners provide an alternative means of consuming their client that does not directly expose the JAX-RS resource interfaces through Guice. The wrapper client should be named like SomeClient and have accessor methods to the individual JAX-RS resources.

Problem: Guice does not support using multibinder or optional bindings for the same type across multiple PrivateModules or between a PrivateModule and AbstractModule.
Solution: Make sure any usage of multibinders or optional bindings, including in your installed dependencies, are not used across different types of Guice modules.