Add support of WebSocket protocol

[Tenischev]

Reason/Context

WebSocket is one of the chose when we need establish connection between backend server and (usually web) client.
Spring-WebSocket is relatively popular library among users (353 usages + 937 usages according to maven).
At the moment template support only mqtt, amqp and kafka protocols.

Description

Provide support for WebSocket (wss) protocol using spring-websocket and\or spring-integration-websocket.
Implementation should be aware of STOPM limitations and\or have SockJS fallback.

• Create dedicate Publisher and Config in partials.
• Update PublisherService, Config, MessageHandlerService and CommandLinePublisher template files.
• Create Java tests, update 02_removeNotRelevantParts.js to avoid presence of wss tests in other protocol generation.
• Create npm snapshot tests with providing corresponding mock API.

Docs and guides:

• https://docs.spring.io/spring-integration/docs/6.1.5/reference/html/web-sockets.html#web-sockets
• https://docs.spring.io/spring-framework/reference/web/websocket/server.html
• https://spring.io/guides/gs/messaging-stomp-websocket/
• https://www.baeldung.com/websockets-spring

[aeworxet]

Bounty Issue's service comment

Text labels: bounty/2024-Q1, level/advanced, bounty/coding, bounty/dropped, bounty/eol
End Of Life after: 2024-05-31 23:59:59 UTC-12:00

[Tenischev]

I would like to work on this issue

[aeworxet]

@asyncapi/bounty_team

[aeworxet]

Bounty Issue's Timeline

Complexity Level	Assignment date (by GitHub)	Start date (by BP rules)	End date (by BP rules)	Draft PR submission	Final PR submission	Final PR merge
Advanced	2023-12-20	2024-01-01	2024-02-23	2024-01-19	2024-02-09	2024-02-23

Please note that the dates given represent deadlines, not specific dates, so if the goal is reached sooner, it's better.

[Jagrutiti]

Can I take this up? I am in good in Java and Spring.

[Jagrutiti]

Can I take this up? I am in good in Java and Spring.

I was actually looking for Docs issue. But came across something I understand.

[aeworxet]

@Jagrutiti Please take a look at the top of the page, it says this issue already has an assignee.

[Jagrutiti]

The issue does not have an active PR linked.

This assignee could be inactive. At least that's what I assumed. My bad.

[aeworxet]

Assignees only for regular GitHub issues have the luxury of being inactive. The AsyncAPI Bounty Program Participants are responsible.
Also, it is not the time for PR yet, according to the Bounty Issue's Timeline.
Keep an eye on:

• GH Discussion for Bounty Issues submission during the first and second full (seven-day) calendar weeks of the last month of the current calendar quarter (2023-03-04 ~ 2023-03-17 is the closest), to be able to make an early decision on the Bounty Issue's choice,
• the #17_bounty channel in Slack till the end of that month (2023-03-18 ~ 2023-03-31 is the closest) to catch an up-for-grabs Bounty Issue and submit your candidature in its comments.

[aeworxet]

@Tenischev, please provide an update to the PR.

[aeworxet]

@Tenischev, please provide an update to the PR.