AsyncAPI spec v3 support in Java Spring template

[jonaslagoni]

Reason/Context

This Issue is used to track changes needed to support AsyncAPI v3. As a code owner, please edit this list of TODO tasks in order to properly track the progress 🙂 Once this issue is closed it means that v3 is now fully supported in this library.

Remaining tasks:

• [ ] Update template to use parser v2, this is already supported by the generator by changing the apiVersion

[github-actions[bot]]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart:

[Tenischev]

I start slowly gather here tasks:

• [ ] update template to use parser-js v3. It doesn't make much sense to migrate from v1 to v2 when v2 is outdated. The problem is in significant parser API change
• [ ] support reply operation, follow to asyncapi/spec#981
• [ ] probably most of all calls to channels() has to be changed to operations() with rewrite of underling code, because for program it's more important which operations should be made instead of which channels are defined. It may be sense to use channels() in Configuration class.
• [ ] use channel.address() instead of channelName
• [ ] no more hasPublish or hasSubscribe methods
• [ ] operation now should work only like oneOf is several possible messages are listed (clarification of Parser API is required here)
• [ ] any parameters of channel now could be only string type (clarification of Parser API is required here)

[johnament]

Are there any plans to address this?

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity :sleeping:

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience :heart: