FWIW I was able to get camel-amqp working in ServiceMix 6.1.1. I deployed
camel-amqp 2.16.5 after giving up on 2.16.2. Here are the files I added to
the servicemix/deploy folder:
camel-amqp-2.16.5.jar
netty-buffer-4.0.41.Final.jar
netty-codec-4.0.41.Final.jar
netty-codec-http-4.0.41.Final.jar
ne
>From the karaf prompt I do a "list" and get the following:
237 | Active | 80 | 0.32 |
qpid-amqp-1-0-client-jms
238 | Active | 80 | 0.32 |
qpid-amqp-1-0-common
239 | Active | 80 | 0.32 |
qpid-amqp-1-0-clie
Just to be clear did you install the qpid jar first? Something like the
below in the karaf prompt.
bundle:install wrap:mvn:org.apache.qpid/qpid-amqp-1-0-client/0.20
Run a bundle list to ensure the bundle is properly installed. Can verify in
the logs. Only then add the camel-amqp.
On Tue, Feb 21,
Thanks for that link. That's where I first found a list of dependencies
that I need. I've also gone through the camel-amqp component source code
for both 2.16.x and 2.18.x to try and figure out the differences. Below
is the output when trying to install camel-amqp version 2.16.2
karaf@root>fea
This should give you some indication of what dependencies are required..
https://mvnrepository.com/artifact/org.apache.camel/camel-amqp/2.18.2
On Tue, Feb 21, 2017 at 10:35 PM, Mark Webb [via Camel] <
ml-node+s465427n5794222...@n5.nabble.com> wrote:
> The problem I'm running in to is figuring out
The problem I'm running in to is figuring out what the dependency and
version I'm missing is. The dependency that is being reported is in
ServiceMix. My guess its a dependency of a dependency and its not getting
reported all the way back. I turned up the logging and don't see anything
there eith
https://servicemix.apache.org/docs/7.x/users-guide/deployer.html
Somewhere in the middle sections there is documentation on the wrapper.
So I think you need to deploy the dependency as a wrapper and then the
camel-amqp as a feature.
On Tue, Feb 21, 2017 at 10:10 PM, Mark Webb [via Camel] <
ml-no
I believe you are correct. The problem with the wrapping of a jar into a
bundle is that you often lose the dependencies and the wrapped bundle
always shows as active even if there are missing dependencies.
On Tue, Feb 21, 2017 at 4:06 PM, souciance wrote:
> I have not worked with ServiceMix b
I have not worked with ServiceMix but with Karaf if the thing you are
deploying is not a osgi bundle you need to use the "wrap" command to wrap
it which will instruct Karaf to add some OSGI stuff to it. Must be
something similar for ServiceMix.
Something like wrap:mvn:org.apache.qpid/qpid-amqp-1-0