Andrej,
I am hitting the same restriction. Were you able to connect stomp endpoint
to use websocket or is there another workaround that I am not reading in
this comment thread?
Thanks,
Michael
Hitting this:
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to
resolve endpoint:
Ahh, i missed that. In your OP you mention you want to connect Camel to
ActiveMQ which is behind a firewall. For that the http transport should
work fine.
If you're sending messages from a browser directly to the broker, STOMP
over WebSockets should be work.
If you're getting a BindAddressExcepti
Because i want to deliver messages to the queue from a webbrowser. The
broker will be behind a firewall, only able to use ports 80 and 443.
The camel route should also connect to the same broker over the same port
to consume messages from the same queue.
+-+ +
Why don't you use the http transport? Don't need WS for this...
http://activemq.apache.org/http-and-https-transports-reference.html
On Sun, Oct 13, 2013 at 7:52 AM, ako wrote:
> Hi,
>
> I want to create a camel route which consumes messages from an ActiveMQ
> topic. There's a firewall between
Can get it to work.
1st attempt:
/* init broker */
...
BrokerService brokerSvc = new BrokerService();
brokerSvc.setBrokerName("brkr1");
brokerSvc.addConnector("ws://localhost:61613?trace=true");
...
/* route configuration */
from("stomp:top
Hi
I think the protocol in camel-stomp should be defined as tcp.
http://camel.apache.org/stomp
On Sun, Oct 13, 2013 at 4:52 PM, ako wrote:
> Hi,
>
> I want to create a camel route which consumes messages from an ActiveMQ
> topic. There's a firewall between the camel code and the ActiveMQ broke
