Hi Thomas

Did you take a look on the Karaf documentation ? There is description of what 
is a feature, req/cap, ...

Regards
JB

On Feb 5, 2017, 05:53, at 05:53, Thomas Vandahl <[email protected]> wrote:
>Hi folks,
>
>I'm a newbie in the OSGi area, so please excuse if I ask silly
>questions. However, even intensive googling did not help.
>
>We've created an application that consists of eight bundles based on
>Camel, CXF and Blueprint. We could run it in Karaf 4.0.7 just fine when
>all dependency features/bundles were installed manually.
>
>The obvious idea was to combine all bundles and their dependencies in a
>Karaf-feature for automatic installation. From reading the docs, I
>thought that having my bundles as dependencies of the feature artifact
>would do the trick. The feature file looked promising but Karaf could
>not resolve several packages, nor could I get the feature to
>karaf:verify successfully.
>
>What else did I try:
>- building the feature file by hand as an exact copy of what had been
>done manually at the Karaf console -> no success (the usual suspects
>you
>find when searching the internet: missing blueprint container, spring
>beans, jaxb AnnotationReader, aop alliance Advice etc)
>- reducing the complexity to just one basic bundle -> no success
>- defining boot-features and prerequisites as mentioned in some
>postings
>-> no success
>- adding required features as Maven dependencies -> no success
>- copy the structure of existing feature files -> no success
>- build a KAR instead of a feature -> no success
>
>Did I even get the whole idea right? Could you please point me to a
>tutorial-kind-of-thing that explains step by step how a feature
>artifact
>is supposed to work? Or to some help with debugging?
>
>Thanks in advance for any hint you can give.
>Bye, Thomas

Reply via email to