There really shouldn't be any reason to use the activemq-camel dependency.
Here's an example pom.xml that I've used to build a web-app with a Camel
context:

<?xml version='1.0'?>
<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
   <modelVersion>4.0.0</modelVersion>

   <artifactId>camelwar</artifactId>
   <packaging>war</packaging>
   <name>ActiveMQ Artemis Camel WAR Example</name>

   <dependencies>
      <dependency>
         <groupId>org.springframework</groupId>
         <artifactId>spring-web</artifactId>
         <version>${spring.version}</version>
      </dependency>
      <dependency>
         <groupId>org.springframework</groupId>
         <artifactId>spring-context</artifactId>
      </dependency>
      <dependency>
         <groupId>org.apache.camel</groupId>
         <artifactId>camel-spring</artifactId>
         <version>2.20.0</version>
         <exclusions>
            <exclusion>
               <groupId>org.slf4j</groupId>
               <artifactId>slf4j-api</artifactId>
            </exclusion>
         </exclusions>
      </dependency>
      <dependency>
         <groupId>org.apache.camel</groupId>
         <artifactId>camel-jms</artifactId>
         <version>2.20.0</version>
         <exclusions>
            <exclusion>
               <groupId>org.slf4j</groupId>
               <artifactId>slf4j-api</artifactId>
            </exclusion>
            <exclusion>
               <groupId>org.apache.geronimo.specs</groupId>
               <artifactId>geronimo-jms_2.0_spec</artifactId>
            </exclusion>
         </exclusions>
      </dependency>
   </dependencies>
</project>

This pom should include everything you need and filter out everything
that's already provided by the broker so there are no conflicts.

And here's the applicationContext.xml:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans";
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
       xmlns:context="http://www.springframework.org/schema/context";
       xsi:schemaLocation="
       http://www.springframework.org/schema/beans
       http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
       http://www.springframework.org/schema/context
       http://www.springframework.org/schema/context/spring-context-2.5.xsd
       http://camel.apache.org/schema/spring
       http://camel.apache.org/schema/spring/camel-spring.xsd";>

   <bean id="artemisConnectionFactory"
class="org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory">
      <constructor-arg name="url" value="tcp://localhost:61616"/>
   </bean>

   <bean id="artemisConfig"
class="org.apache.camel.component.jms.JmsConfiguration">
      <property name="connectionFactory" ref="artemisConnectionFactory"/>
      <property name="concurrentConsumers" value="10"/>
   </bean>

   <bean id="artemis" class="org.apache.camel.component.jms.JmsComponent">
      <property name="configuration" ref="artemisConfig"/>
   </bean>

   <camelContext id="bridgeContext" trace="false" xmlns="
http://camel.apache.org/schema/spring";>
      <route id="exampleRoute">
         <from uri="artemis:queue:sausage-factory"/>
         <to uri="artemis:queue:mincing-machine"/>
      </route>
   </camelContext>
</beans>


Justin



On Tue, Nov 21, 2017 at 6:45 AM, alisu <alisu7...@gmail.com> wrote:

> I have managed to sort out the dependency conflict problem. Actually both
> camel-spring and activemq-camel come with jaxb. So I just made sure they
> both use the same version of jaxb. e.g. by using activemq-camel-5.15.1 and
> camel-spring-2.20.1 where they both use jaxb-2.2.11.
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

Reply via email to