; from endpoint class.
>
>
> below is the log message :
>
> *[New I/O worker #19] WsEndpoint INFO
> received message --> my external WebSocket *
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-We
webscoket but not working if we use
Netty or any other technology. .
Any help on this would be greatly appreciated!
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-WebSocket-WsEndpoint-not-forwarding-messages-tp5760996p5761344.html
Sent from the Camel - Users mailing list
427.n5.nabble.com/Camel-WebSocket-WsEndpoint-not-forwarding-messages-tp5760996p5761345.html
Sent from the Camel - Users mailing list archive at Nabble.com.
messages to my route //myEndPoint .
>
> But same configuration is working fine if external WebSocket also uses the
> Camel WebSocket component which is weird. *Does this mean camel websocket
> AHC-WS component only works if external Websockets developed using Camel
> Components*?
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-WebSocket-WsEndpoint-not-forwarding-messages-tp5760996.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
myEndPoint .
But same configuration is working fine if external WebSocket also uses the
Camel WebSocket component which is weird. *Does this mean camel websocket
AHC-WS component only works if external Websockets developed using Camel
Components*?
--
View this message in context:
http://c
