Hi Allard,
we are using the axon-spring-boot-starter with the following (unsuspicious) configuration:
axon:
axonserver:
token: "..."
context: "..."
servers: localhost
ssl-enabled: false
What we did, though, and this could be where we must adopt st: We came up with the concept of “operation modes” (see discussion in https://github.com/AxonFramework/AxonFramework/issues/1256).
So for a system, that only should use the queryGateway, we disabled the JPAAutoConfiguration, Event- and CommundBus, like this:
@EnableAutoConfiguration(exclude = JpaAutoConfiguration.class)
public class QueryOnlyModeConfiguration implements QueryOnlyMode {
@Bean
@Primary
public SagaStore noopSagaStore() {
return NoOperation.SAGA_STORE;
}
@Bean
@Primary
public CommandBus noopCommandBus() {
return NoOperation.COMMAND_BUS;
}
@Bean
@Primary
public EventStore noopEventBusAndStore() {
return NoOperation.EVENT_STORE;
}
}
(where NoOperation… throws UnsupportedOperationExceptions on all functions).
This works, in the sense that we a) can get the query result via queryGateway (and see the service in the axon server overview) and b) do not get tables (eventStore, sagaStore, tokenStore, …) created in our DB. I guess, we missed some internal requirements and should at least provide an inMemory implementation of … what? Any idea? Where does the QueryChannelImpl check if I am registered/subscribed?
Thanks
Jan