it contains javax.jms because the jar contains the SPEC - the JMS API. Then you add vendor jars to provide the connection factory implementations etc.
2012/10/26 Caa_man <c...@acs-it.ru>: > Jens is right! > I studied all dependencies which were loaded with ActiveMQ. One of > dependencies is geronimo-jms_1.1_spec. This jar has javax.jms packages (WHY > THE HELL???). As a result I removed geronimo jars from compiled archive and > this change yielded application deployment to be Ok. > > <dependency> > <groupId>org.apache.activemq</groupId> > <artifactId>activemq-camel</artifactId> > <version>5.7.0</version> > </dependency> > <dependency> > <groupId>org.apache.activemq</groupId> > <artifactId>activemq-core</artifactId> > <version>5.7.0</version> > </dependency> > <dependency> > <groupId>org.apache.activemq</groupId> > <artifactId>activemq-pool</artifactId> > <version>5.7.0</version> > </dependency> > <dependency> > <groupId>org.apache.geronimo.specs</groupId> > <artifactId>geronimo-jms_1.1_spec</artifactId> > <version>1.1.1</version> > <scope>provided</scope> > </dependency> > <dependency> > <groupId>org.apache.geronimo.specs</groupId> > <artifactId>geronimo-jta_1.0.1B_spec</artifactId> > <version>1.0.1</version> > <scope>provided</scope> > </dependency> > <dependency> > <groupId>org.apache.geronimo.specs</groupId> > <artifactId>geronimo-j2ee-management_1.1_spec</artifactId> > <version>1.0.1</version> > <scope>provided</scope> > </dependency> > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/ActiveMQ-and-WebSphereMQ-tp5721492p5721586.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
