Have an application that declares an MDB to handle incoming messages from a Kafka Topic. The related feature is not by default enabled - not all instances of the application will connect to the Kafka Topic. Rather than have perpetual errors in the logs it would be good to provide an ActivationConfigProperty that skipped enabling any workers:
Have an application that declares an MDB to handle incoming messages from a Kafka Topic. The related feature is not by default enabled - not all instances of the application will connect to the Kafka Topic. Rather than have perpetual errors in the logs it would be good to provide an
ActivationConfigProperty
that skipped enabling any workers:The variable replacement is handled by the container (Wildfly specific, but presumably this is relevant in general).
Would a PR along these lines be welcome?