Service classes from other modules

Quarkus CXF inspects your service implementations at build time through the Quarkus class index, also known as Jandex. So the whole class hierarchy of a service implementation must be in that index: the implementation class, its superclasses, and the interfaces it implements.

The class index always contains the classes of your application. Those are all the classes of the module that is configured with quarkus-maven-plugin, or with the io.quarkus Gradle plugin. Quarkus indexes them automatically.

Quarkus does not index the classes of other modules automatically, even when they belong to the same multi-module project. Quarkus treats such a module as a dependency. A dependency is in the index when, for example, it contains a Jandex index (META-INF/jandex.idx) or a beans.xml descriptor, or when you register it with quarkus.index-dependency properties. See Bean Discovery in the Quarkus CDI reference for the full list, and Working with multi-module projects for Maven.

When a service implementation in your application implements a service interface from a dependency without an index, for example a separate API module, and does not set the endpointInterface attribute of @WebService, the build fails with a message such as the following: