[
https://issues.apache.org/jira/browse/SMX4-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990605#comment-12990605
]
Gert Vanthienen commented on SMX4-753:
--------------------------------------
It does work fine using the {{activemq:}} URI prefix, using
{{failover:(tcp://localhost:61616)}} as the connection url. Wondering if we
shouldn't do something in ServiceMix to make this work using the vm: transport
instead (both for performance and to ensure things keep working when people
change the transport connection parameters) ...
> Improve out-of-the-box integration between Camel and ActiveMQ
> -------------------------------------------------------------
>
> Key: SMX4-753
> URL: https://issues.apache.org/jira/browse/SMX4-753
> Project: ServiceMix 4
> Issue Type: Improvement
> Affects Versions: 4.2.0
> Reporter: Gert Vanthienen
> Assignee: Gert Vanthienen
> Fix For: 4.3.0
>
>
> While creating the quickstart guide last night, I found myself needing to
> install the camel-activemq feature and having to add a component definition
> to be able to use the 'amq' component. We should make it as easy as possible
> for people to use ActiveMQ and Camel together in ServiceMix. In my mind, the
> XML file below should just work in a new ServiceMix installation.
> {code:xml}
> <blueprint
> xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="
> http://www.osgi.org/xmlns/blueprint/v1.0.0
> http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd";>
> <camelContext xmlns="http://camel.apache.org/schema/blueprint";>
> <route>
> <from uri="amq://events"/>
> <to uri="log:events"/>
> </route>
> </camelContext>
> </blueprint>
> {code}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
