Hi I dont think this is implemented/supported. Its intended to be a local server when using consumer (from).
Not sure what it would take to support this (and if possible). As there are some other ramifications. Also it seems a bit abusive use-case you are doing. Instead look at the stomp component. https://camel.apache.org/components/latest/stomp-component.html On Tue, Jan 12, 2021 at 10:19 AM CASAUX Nicolas <nicolas.cas...@soprasteria.com> wrote: > > Hello again :) > > Could someone confirm that it is not possible to receive message from a > remote websocket server with this "camel-vertx-websocket" component ? Or > pointing out what I'm doing wrong ? > As far as I understand, currently it seems only possible to send message to a > remote server. > > Thanks! > > Nicolas > > > > De : CASAUX Nicolas > Envoyé : mercredi 16 décembre 2020 21:45 > À : users@camel.apache.org > Objet : camel-vertx-websocket > > Hello ! > > I'm currenty trying to use camel-vertx-websocket component to connect to a > remote ActiveMQ through a "Stomp over Websocket" connection. > Since version 3.7.0 of Camel released today, I can successfully set the > subprotocol in URI like this, and it works: > > .to("vertxWebsocket://remoteActiveMQHost:61614/?clientSubProtocols=v12.stomp")) > > My issue is I can't figure out how I'm supposed to receive the message which > are sent by the ActiveMQ to my client. > Indeed, when I try to start another route with: > > from("vertx-websocket://remoteActiveMQHost:61614/?clientSubProtocols=v12.stomp > ") > > Vertx seems to try to start local server (and fails). > I tried to setup a VertxWebsocketEndpoint, with a specific > VertxWebsocketConfiguration, but it always ends up by Vertx trying to start a > server. > > How could I write a route in such way I could receive messages from a remote > Websocket endpoint ? > > Thanks in advance! > > Nicolas -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
