Can you move the camel-osgi-2.0-M3.jar before the camel-spring-2.0-M3.jar?
It will do a trick to let camel-spring find the camel-osgi module before
it register the spring handler to parser camelContext element.
Willem
otech wrote:
Sorry, I have edited the previous post. The actual file is:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Desktop
Bundle-SymbolicName:desktop;singleton:=true
Bundle-Version: 1.0.0
Bundle-Activator: desktop.Activator
Bundle-Vendor: com
Require-Bundle: org.eclipse.ui,
org.eclipse.core.runtime,
org.eclipse.core.databinding;bundle-version="1.2.0",
org.eclipse.core.databinding.beans;bundle-version="1.2.0",
org.eclipse.core.databinding.property;bundle-version="1.2.0",
org.eclipse.jface.databinding;bundle-version="1.3.0"
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-ActivationPolicy: lazy
Bundle-ClassPath: libs/glazedlists-1.8.0_java15.jar,
libs/net.sourceforge.nattable.core_2.0.0.200906211946.jar,
libs/net.sourceforge.nattable.extension.glazedlists_2.0.0.200906211946.jar,
.,
libs/commons-lang-2.4.jar,
libs/activemq-all-5.2.0.jar,
libs/commons-beanutils-1.8.0.jar,
libs/commons-logging-1.1.1.jar,
libs/log4j-1.2.14.jar,
libs/spring-beans-2.5.6.jar,
libs/spring-context-2.5.6.jar,
libs/spring-core-2.5.6.jar,
libs/spring-jms-2.5.6.jar,
libs/spring-tx-2.5.6.jar,
libs/xbean-spring-3.2.jar,
libs/k170-1.0.jar,
libs/spring-aop-2.0.8.jar,
libs/camel-jms-2.0-M3.jar,
libs/jencks-2.0.jar,
libs/jencks-amqpool-2.0.jar,
libs/commons-pool-1.5.2.jar,
libs/camel-core-2.0-M3.jar,
libs/camel-spring-2.0-M3.jar,
libs/activemq-camel-5.2.0.jar,
libs/camel-osgi-2.0-M3.jar
willem.jiang wrote:
I didn't find the camel-osgi-2.0-M3.jar in the MANIFEST.MF file.