Any plan to support WebSocket Annotations for generating AsyncAPI doc ?

[ceoche-kereval]

Hi,

From my understanding, quarkus-asyncapi only support Microprofile-messaging annotations.

Is there any plan to support WebSocket Annotations from jakarta.websocket-api (@ServerEndpoint, @OnMessage...) for generating AsyncAPI doc ?

Thank you.

[indiealexh]

This is also my preferred use case.

[ChMThiel]

We don't use Websockets, so thats not planned on my side.
But feel free to participate. If you want to implement this and provide a PR, you're welcome 👍

[indiealexh]

We don't use Websockets, so thats not planned on my side. But feel free to participate. If you want to implement this and provide a PR, you're welcome 👍

I'll see if I can make time for this, it would be really handy. Only issue I see is that the Websocket stuff is little open ended as it doesn't have a specific subprotocol or communication method, so scaning and documenting models will be hard. @ceoche-kereval do you have a specific sub protocol you use? I use a variation on JsonRPC 2.0 where both server and client can send requests, responses and notifications.

If I pick up the quarkiverse json-rpc library that might be a good place to start with async-api support for websockets. Not sure what other sub-protocols are popular these days.