Note that there are some explanatory texts on larger screens.

plurals
  1. POActiveMQ setup of tcp socket using mina
    primarykey
    data
    text
    <p>I am trying to setup a simple demo of activemq and mina. I edited the camelContext in the activemq.xml file to include two mina tcp sockets, two queues and routes as such: </p> <p>listenerA -> qA -> listenerB<br> listenerB -> qB -> listenerA </p> <p>The intent is to have two way pass through between two telnet sessions. Later, I will add more fancy features such as filtering, routing to a topic and my own codec on each listener. </p> <p>Here is my camelcontext: </p> <pre><code> &lt;!-- You can use a &lt;package&gt; element for each root package to search for Java routes --&gt; &lt;package&gt;com.myco.codec&lt;/package&gt; &lt;endpoint id="listener_A" uri="mina:tcp://localhost:42000?textline=true"/&gt; &lt;endpoint id="listener_B" uri="mina:tcp://localhost:42001?textline=true"/&gt; &lt;!-- You can use Spring XML syntax to define the routes here using the &lt;route&gt; element --&gt; &lt;route&gt; &lt;from ref="listener_A"/&gt; &lt;to uri="activemq:qA"/&gt; &lt;/route&gt; &lt;route&gt; &lt;from uri="activemq:qB"/&gt; &lt;to ref="listener_A"/&gt; &lt;/route&gt; &lt;route&gt; &lt;from ref="listener_B"/&gt; &lt;to uri="activemq:qB"/&gt; &lt;/route&gt; &lt;route&gt; &lt;from uri="activemq:qA"/&gt; &lt;to ref="listener_B"/&gt; &lt;/route&gt; &lt;/camelContext&gt; </code></pre> <p>When I start activemq I get an exception: </p> <p>org.apache.camel.NoSuchEndpointException: No endpoint could be found for: mina:tcp://localhost:42000?textline=true </p> <p>Do I explicitly need to add a mina bean? If so where and how?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload