MqttConfig.java does not handle both a subscribe and publish under the same topic

[gaby-roland]

Having a publish and subscribe channels under the same topic is allowed, however, it results in compilation errors due to the subscribe topic variables not being created. This is because the loop iterates through the channels, and uses if/elif to create the publish/subscribe topic variables. If both publish and subscribe are defined in the yaml, only the publish variables are created in the Config.java class. This is an easy fix, just change the if/elif to if/if to handle this edge case.

java-spring-template/partials/MqttConfig.java

Line 73 in a1ae805

{% elif channel.hasSubscribe() %}

[github-actions]

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.

[Tenischev]

Hello @gaby-roland
Thank you for the report!
Could you please also provide an example of AsyncAPI file with this configuration? If possible, could you please explain application logic that you expect from application that read and write to the same topic?

[github-actions]

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

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 ❤️