[ 
https://issues.apache.org/jira/browse/SM-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944620#comment-13944620
 ] 

Gert Vanthienen commented on SM-2269:
-------------------------------------

I already updated the quickstart guide so at least that guide just works for 
people who start using the project.
We should however still try to fix the issue here, I think, and make using 
ActiveMQ and Camel together as easy as possible.

> ActiveMQ quick start doesn't work due to the missing activemq component
> -----------------------------------------------------------------------
>
>                 Key: SM-2269
>                 URL: https://issues.apache.org/jira/browse/SM-2269
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 5.0.0
>            Reporter: Krzysztof Sobkowiak
>            Priority: Minor
>             Fix For: 5.0.1
>
>
> The activemq sample described in quick start 
> (http://servicemix.apache.org/docs/5.0.x/quickstart/activemq.html) doesn't 
> work with ServiceMix 5.0.0. It looks like the activemq component is not 
> registered. Adding following snippet to both routes solves the problem
> {code}
> <reference id="connectionFactory" interface="javax.jms.ConnectionFactory" />
> <bean id="activemq" 
> class="org.apache.activemq.camel.component.ActiveMQComponent">
>         <property name="brokerURL" value="tcp://localhost:61616"/>
>       <property name="userName" value="smx"/>
>       <property name="password" value="smx"/>
> </bean>
> {code}
> As described by user reporting this problem, the quick start works with 
> ServiceMix 4.5.3 without additional registering of the activemq component.
> As described by the user, the camle-jms component must be also installed 
> manually (in opposite to 4.5.3)
> We should solve these issues or update the quick start.
> Cfr. 
> http://servicemix.396122.n5.nabble.com/ANNOUNCE-Apache-ServiceMix-5-0-0-released-td5719674.html
>  for more information



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to