[ 
https://issues.apache.org/jira/browse/SMX4-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gert Vanthienen updated SMX4-753:
---------------------------------

    Fix Version/s:     (was: 4.4.0)
                   4.5.0

Currently, we already support the {{amq://}} URLs out-of-the-box, but we still 
need to work on leveraging the connection pool instead of using the ActiveMQ 
default connection factory
                
> 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
>             Fix For: 4.5.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.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to