Re: Camel-RabbitMQ-STOMP

2019-11-22 Thread Omar Al-Safi
Hi Mahesh,

The error above is related to the initial creation of the Camel route, is
pretty weird though that it can't parse the options although you
correctly spelled them. Which version of Camel do you use?
Also, in regards camel stomp with RabbitMQ, I honestly have no idea if it
is going to work although I don't see why wouldn't work.

Regards,
Omar

On Fri, Nov 22, 2019 at 12:51 PM Mahesh  wrote:

> Hi All,
> I am new to message brokers. I successfully completed a POC using Spring
> Reactor Netty Stomp client (Spring messaging framework) to connect to
> RabbitMQ on port 61613 (port dedicated for STOMP). That was just a POC. Now
> i have to build something concrete to be able to deploy in prod
> environments. I was googling Spring Messaging Vs Spring Integration and
> stumbled upon Apache Camel.
> My question is: Can Apache camel be used to connect to RabbitMQ on port
> 61613.
>
> I read camel documents:
> 1. RabbitMQ component page talks about port 5672 and that is AMQP
> 2. STOMP component page talks about ActiveMQ
>
> I did not see any examples or documentation regarding Camel in conjunction
> with RabbitMQ and STOMP.
>
> I went ahead and tried establishing STOMP connection with RabbitMQ as
> mentioned below:
>
>
> from("stomp:queue:controllerlistener?brokerURL=tcp://localhost:61613=guest=guest").to("stream:out");
>
> I am getting an exception:
>
>  org.apache.camel.FailedToCreateRouteException: Failed to create route
> route1: Route(route1)[[From[stomp:queue:test?brokerURL=tcp://localho...
> because of Failed to resolve endpoint:
>
> stomp://queue:test?brokerURL=tcp%3A%2F%2Flocalhost%3A61613=guest=guest
> due to: Failed to resolve endpoint:
>
> stomp://queue:test?brokerURL=tcp%3A%2F%2Flocalhost%3A61613=guest=guest
> due to: There are 3 parameters that couldn't be set on the endpoint. Check
> the uri if the parameters are spelt correctly and that they are properties
> of the endpoint. Unknown parameters=[{brokerURL=tcp://localhost:61613,
> login=guest, passcode=guest}]
>
> What is the right way to establish STOMP connection with RabbitMQ?
>
> Thanks,
>
> Mahesh
>


Camel-RabbitMQ-STOMP

2019-11-22 Thread Mahesh
Hi All,
I am new to message brokers. I successfully completed a POC using Spring
Reactor Netty Stomp client (Spring messaging framework) to connect to
RabbitMQ on port 61613 (port dedicated for STOMP). That was just a POC. Now
i have to build something concrete to be able to deploy in prod
environments. I was googling Spring Messaging Vs Spring Integration and
stumbled upon Apache Camel.
My question is: Can Apache camel be used to connect to RabbitMQ on port
61613.

I read camel documents:
1. RabbitMQ component page talks about port 5672 and that is AMQP
2. STOMP component page talks about ActiveMQ

I did not see any examples or documentation regarding Camel in conjunction
with RabbitMQ and STOMP.

I went ahead and tried establishing STOMP connection with RabbitMQ as
mentioned below:

from("stomp:queue:controllerlistener?brokerURL=tcp://localhost:61613=guest=guest").to("stream:out");

I am getting an exception:

 org.apache.camel.FailedToCreateRouteException: Failed to create route
route1: Route(route1)[[From[stomp:queue:test?brokerURL=tcp://localho...
because of Failed to resolve endpoint:
stomp://queue:test?brokerURL=tcp%3A%2F%2Flocalhost%3A61613=guest=guest
due to: Failed to resolve endpoint:
stomp://queue:test?brokerURL=tcp%3A%2F%2Flocalhost%3A61613=guest=guest
due to: There are 3 parameters that couldn't be set on the endpoint. Check
the uri if the parameters are spelt correctly and that they are properties
of the endpoint. Unknown parameters=[{brokerURL=tcp://localhost:61613,
login=guest, passcode=guest}]

What is the right way to establish STOMP connection with RabbitMQ?

Thanks,

Mahesh


Re: Camel 3 alternatives for ServletListener component

2019-11-22 Thread Claus Ibsen
Hi

Yeah you can use @WebListener or whatever the servlet container supports.

Or for example use a spring xml file and a spring servlet listener
that bootstrap spring and reads the xml file, where you can have
 to start Camel.
Such as shown in this example
https://github.com/apache/camel/tree/master/examples/camel-example-servlet-tomcat


On Thu, Nov 21, 2019 at 10:41 PM Markus Punnar  wrote:
>
> Hello!
>
> As I understand the ServletListener component which was used to bootstrap
> Camel is deprecated and removed in Camel 3. From the docs I did not find
> what should be done instead when using Camel 3? For Servlet 3.x contains
> the @WebListener annotation-driven configuration can be used. Is this the
> recommended way to go now and drop the web.xml entirely?
>
> The same question also goes for implementing a custom lifecycle. On Camel
> 2.x it was done by
> implementing org.apache.camel.component.servletlistener.CamelContextLifecycle
> which is now removed as well as far as I understand.
>
> If somebody can answer these questions or point me towards the correct
> documentation or examples on how to do this on Camel 3, it would be
> appreciated.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2