"Fixed" the bug by adding a default-handler master default-handler-as-fix
authorKai Moritz <kai@juplo.de>
Mon, 6 Jun 2022 16:49:21 +0000 (18:49 +0200)
committerKai Moritz <kai@juplo.de>
Mon, 6 Jun 2022 16:49:21 +0000 (18:49 +0200)
commitaa59bc37304588ef413dead0a0dd4a653b4a139e
tree9bcf79412840ddb7a6cd042f919fb4a7a996d6ca
parent4a47513393bbe1aaaf8c9674ad978de5da2a9d7d
"Fixed" the bug by adding a default-handler

* The default-handler is _NOT_ necessary, if the handler-methods only
  consume the message itself.
* This looks like a bug in the automatic configuration:
  * Without the addtional parameter of type `ConsumerRecordMetaData`, the
    automatically created resolvers are able to consume the payload.
  * After the addition of the `consumerRecordMetaData`-parameter, the
    automatically created resolvers are empty and fail to resolve the
    payload.
  * After the addition of the default-handler, the required resolvers
    are availabe again.
src/main/java/de/juplo/kafka/MultiMessageConsumer.java