Hello,
I am testing on Karaf an OSGi application that runs successfully in Eclipse
Virgo, WebSphere Liberty and plain Equinox (bndrun) using Pax Web.
The application is running as expected, and in order to provision it I
created a XML feature repository file containing several features and
configurations.
When creating the feature file if I don't or can't use maven URLs, can I use
variable substitutions in file:// URLs in orther to pickup bundles that I
copied into a folder, e.g.:
file:///${karaf.base}/mybundles/my.bundle.jar
Can I do the same to copy to e.g. ${karaf.etc} additional configuration
files (<configfile> feature element)?
As an alternative approach, I would like to try OBR, which would make the
deployment more similar to that of Eclipse Virgo and WebSphere Liberty,
letting me re-use more of the existing build scripts.
By reading the documentation I understood that:
1 - I should install Karaf Cave which provides an OBR repository
2 - I should install OBR which will let Karaf resolve bundle requirements
against Cave
3 - I should deploy my top-level bundles either manually or by placing them
in the OBR repository
and by listing them in a feature using an "obr:" URL.
4 - required bundle dependencies will be found by OBR in the Cave repository
and will be deployed for me
The Karaf documentation explains how to use Cave and how to create and
populate a repository, but:
* - the latest version of Cave, 4.2.0 has completely different shell
commands, in particular "upload" is gone
* - Cave 4.2.0 documentation describes a gateway command (don't know if that
helps) but that command
does not show up in the shell even after installing the corresponding
feature as documented in the guide
With respect to Cave my questions are:
* - how can I create an OBR repository, populate it, and use it for
resolution when using Karaf 4.2.7 and
Cave 4.2.0? If this is only possible with Cave 4.1.x, will the same
capability be available in a future
Cave 4.2.x or is this deprecated?
* - is there a way for Cave to monitor the repo folder and auto-update the
repository.xml (like Virgo and
WebSphere do, which do not even use repository.xml) or do I have to
manually update the
repository every time a bundle is changed?
Thanks in advance.
Giamma.
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
