jamesnetherton commented on issue #4557:
URL: https://github.com/apache/camel-quarkus/issues/4557#issuecomment-1426029204
> That form is documented here
Yes. For the WS consumer (`from(...)`) where specifying the `host:port`
makes little sense on Quarkus.
For the WS producer (`to(..)`) you could either be connecting to the local
Quarkus HTTP server or some externally hosted WebSocket. Hence `host:port/path`
makes sense in that scenario.
I'm not advocating folks hard code the host / port either. Camel can resolve
Quarkus config properties like:
```
.to("vertx-websocket:localhost:{{quarkus.http.port}}");
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
