When you install Camel components, you should use the features rather than the
bundles. That will make sure you get all the dependencies for that particular
component.
feature:install camel-sql
> On Oct 23, 2018, at 1:15 PM, John F. Berry
> wrote:
>
> Again.. Quinn.. Thanks!
>
> OK..
Again.. Quinn.. Thanks!
OK.. now I feel this is a Karaf issue inside a Camel forum (sorry folks).I did
install that hapi "bundle" into Karaf... that only made it complain about
camel-sql, but given your example, I found the "bundle" to install for that..
then it complained about
You’ll need to add HAPI to the container
install mvn:ca.uhn.hapi/hapi-osgi-base/2.3
> On Oct 22, 2018, at 9:12 AM, John F. Berry
> wrote:
>
>
>
> I have added these to the POM... just in case that solved the Karaf issue.
> No luck!
>
>
> ca.uhn.hapi
> hapi-base
> 2.1
>
>
>
>
I have added these to the POM... just in case that solved the Karaf issue. No
luck!
ca.uhn.hapi
hapi-base
2.1
ca.uhn.hapi
hapi-osgi-base
2.0
On Monday, October 22, 2018, 9:34:31 AM EDT, John F. Berry
wrote:
You've been so much help Quinn, thanks!
I did not
You've been so much help Quinn, thanks!
I did not realize you could import a bundle though maven like that
So close...
I got an error because of some unresolved requirements with OSGi and my hl7
parsing package:
osgi.wiring.package; (osgi.wiring.package=ca.uhn.hl7v2.model) Unresolved
I could be a Karaf install issue. The Karaf setup is usually pretty simple
- expand the Karaf archive
- start Karaf ( $KARAF_HOME/bin/start )
- login to the Karaf console ($KARAF_HOME/bin/client)
- add the Came feature repositoryl into the Karaf container ( feature:repo-add
camel 2.21.1)
-
Thanks Quinn for your advice and patience (and for the rest of the forum
members!)
I did attempt to make the changes below.. and to research the elements you
presented to understand them better.. However, I'm still at an impasse.
I still cannot "deploy" into Karaf.. Perhaps this is a Karaf
Assuming you’re using Maven, you can use the maven-bundle-plugin to generate
the OSGi metadata in the MANIFEST.MF (which is what makes a jar a bundle).
You’ll add something like the following to your build plugins
org.apache.felix
maven-bundle-plugin
3.5.0
true
and you’ll
Thank you François,
I understand blueprint archetype runs under Karaf... but my original question
was do I need to disassemble my developed Java DSL route and rewrite for the
Blueprint (looks like Spring) from java? Or can I simply embed a call in a
Blueprint archetype to call a jar,
Hi,
As Quinn say, you can use Blueprint in Karaf.
If you are new on Karaf, you can start by looking at the examples in the
distribution :
https://karaf.apache.org/documentation.html
regards,
François Papon
fpa...@apache.org
Le 05/09/2018 à 17:17, John F. Berry a écrit :
> Thanks Quinn,
> I
Thanks Quinn,
I haven't converted my jar at all.. I've only packaged my camel java DSL
project into an executable jar from maven.
So I think you're giving me step #2 of a process if I already converted my jar
to an OSGi bundle. I haven't and don't know offhand how to.
If I had this jar as an
The easiest way to bootstrap a route in Karaf is to use Blueprint. I’m
assuming you’ve already converted your jar to an OSGi bundle.
If you add a small XML file to src/main/resources/OSGI-INF/blueprint (assuming
you’re using Maven for this) the route should startup in Karaf when you install
I've posted a few questions over the past month about various steps in a camel
route. I had developed both a Spring version and a Java DSL version
simultaneously at the beginning, because of either the lack or abundance of
certain endpoint development in each. The Java DSL version worked out
13 matches
Mail list logo
