We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We have a STOMP server, that is created on some path, for example localhost:8080/watchApi/myStompServer
It is often case when API Gateway approach used in microservice communication.
I have seen the similar ticket #8 , but using non root path was added for STOMP server, not for STOMP client.
I would prefer to connect using the next way:
StompClientConnection stompClientConnection = StompClient.create(vertx).connect(80, "loclahost", "/watchApi/myStompServer").result(); stompClientConnection.subscribe("/foo", ... );
which is very common for websocket.
The text was updated successfully, but these errors were encountered:
@AntonPozdeev it will be very helpful to use Vert.x for communication via stomp subprotocol, not only for raw websocket usecase
Sorry, something went wrong.
Hi. Is this issue resolved? Is there any way to connect to Server with non root path?
No branches or pull requests
Describe the feature
We have a STOMP server, that is created on some path, for example localhost:8080/watchApi/myStompServer
It is often case when API Gateway approach used in microservice communication.
I have seen the similar ticket #8 , but using non root path was added for STOMP server, not for STOMP client.
I would prefer to connect using the next way:
StompClientConnection stompClientConnection = StompClient.create(vertx).connect(80, "loclahost", "/watchApi/myStompServer").result();
stompClientConnection.subscribe("/foo", ... );
which is very common for websocket.
The text was updated successfully, but these errors were encountered: