Timon Back

Thank you @GreenRover for the reference link. Specifying a complete schema for xml is probably a bit overkill for us, but we will discuss. (Based on a java class, we...

Sure, here it is: ```json { "asyncapi": "3.0.0", "info": { "title": "Springwolf example project - Kafka", "version": "1.0.0", "description": "Springwolf example project to demonstrate springwolfs abilities, including **markdown** support for...

Thanks for this elaborate explanation. Now, I understand that an exchange with a routingKey is a feature to hide the underlying queue name - or adjust it dynamically. Basically you...

Thanks for the PR @pdalfarr I guess we need to into the asyncapi docs how amqp is mapped to channels, particular routing keys. In case you find time to check,...

Thanks for the contact. I get the feeling that we need to deeply look into the amqp plugin implementation and how exchanges, routing keys and queues are mapped to asyncapi...

Relates to https://github.com/asyncapi/bindings/pull/259

Hi @ctasada, great idea, however the timing is unfortunate as we just released 1.0.0, which allowed us to easily discuss and including breaking changes. --- We discussed more in detail...

Sounds great, thanks for the clarification @ctasada. We do have an own package namespace for each maven artifact, so the new annotation would contain the package name `-binding` and the...

Hi @ctasada , springwolf uses swagger to get the property names. Even though I use kotlin myself, adding support for one 'external' annotations opens the door to add support for...

Awesome, Springwolf does support the `ModelConverter` mechanism. Just create a bean in the spring context (example: `MonetaryAmountConverter` within the add-ons package) The class in the linked GH comment has quite...