feat: interceptor filter pattern for serialization/deserialization common cases such as Message and KStream

[SheheryarAamir]

Implement the interceptor filter pattern. Each type has its own class (message, kstream, ...). This allows users to specify their own or (de)activate them. And it opens up the extension point via bean injection and ordering

Relates to #433

[netlify]

✅ Deploy Preview for springwolf-ui canceled.

Name	Link
🔨 Latest commit	89f963f
🔍 Latest deploy log	https://app.netlify.com/sites/springwolf-ui/deploys/6560cf30dde282000821383f

[timonback]

Hi @SheheryarAamir
@sam0r040 and I started on it by converting the SpringPayloadExtractor in core to a spring bean.

The idea is that List-Extractor, Message- (and KStream- in cloud-stream) would implement the newly introduced interface.
The SpringPayloadExtract finds them via dependency injection (List).

This might be a bit more tricky than expected.
Next steps would be:

• Create a class for the KStream- & Message- each and implement the interface
• Adapt the SpringPayloadExtract (if needed)

Right now, we are unsure about the best solution.

We can also imagine a single class that does handle all GenericTypes in one. And similar to resilience4j.ignoreException, a user can set the types which should be extracted via configuration:

springwolf:
    ...:
        payloadExtractor:
            types:
                - org.springframework.web.client.HttpServerErrorException
                - java.io.IOException

[SheheryarAamir]

thank you @timonback. I have one question, how to extract payload type in we are using custom interface instead of spring message for example MyMessage<String> ?

[timonback]

Hi, sorry I forgot to update and good question.

I am not sure if the current state is the final idea before the release. I imagine that the map of classes that can be extracted can be passed via properties configuration by the user.
The map is likely also missing some entries. Function, Consumer and Supplier comes to mind. Are you missing some entries?

[SheheryarAamir]

No, I dont think of any more entries other than already mentioned. But giving an option to user to put values in map solve most of the problem.
I also like the fasterxml implementation of deserialisers . You can have a look in class SimpleDeserializers of jackson-databind:2.15.2 library