Inside Karaf's standard feature descriptor, there is
conditional
conditionwebconsole/condition
bundle
start-level=30mvn:org.apache.karaf.webconsole/org.apache.karaf.webconsole.instance/3.0.3/bundle
bundle
Hi Martin,
Could the info on this page https://issues.apache.org/jira/browse/KARAF-1718
help you a little bit?
Regards,
Danijel
On Mon, Mar 9, 2015 at 12:45 PM, Martin Lichtin lich...@yahoo.com wrote:
Inside Karaf's standard feature descriptor, there is
conditional
Conditional means, this part is conditionally installed in case the
webconsole is already installed or in case the webconsole is just installed
those bundles are also installed. This is for better seperation of concerns
and meant as a trigger.
You'll see a lot of conditionals in the current master
Hi Martin,
It means that:
1/ if the webconsole feature is installed, the bundles will be installed
2/ when the webconsole feature will be installed, the bundles will be
installed
The condition/ contains a feature name but I created Jira to enhance
it: for instance, in order to allow
ServiceMix 5.4/Karaf 2.4.1/Cellar 2.3.4
Earlier REST services sync'ed to all nodes in cluster.
Now a SOAP service bundle-install'ed and bundle-start'ed on one node is not
installing to remote nodes.
It shows up in bundle-list output on the remote node, but not in the la
output on that node.
Thanks for the info and yes, the JIRA helped a bit :)
I ran into it while debugging an issue with the karaf-maven-plugin.
It seems to not really handle conditionals.
Eg:
descriptors
Hi,
I'm trying to get the jolokia agent set up on one of my karaf installs.
I've installed the osgi only bundle like so:
install -s mvn:org.jolokia/jolokia-osgi/1.2.3
I've also installed the following bundles to satisfy its dependencies:
install -s mvn:javax.servlet/servlet-api/2.3
install -s
More info - the logs on the remote machine are as shown below.
All services I have deployed were done using bundle-install using a maven
repository URL local to one node in the cluster. (i.e. bundle-install
myCluster mvn:com.company.soaim.services/pire-server/1.0-SNAPSHOT)
As the log snippet
OK, it turns out that the original services installed did have a copy of the
maven repository on the remote node. That must be the difference.
Is it correct to say that remote nodes do require access to the installation
maven repository when bundle-install'ing from a maven URL
Hi,
let me suggest, to uninstall your own bundles prior of installing the http
feature.
The HttpFeature does install all required bundles. Especially since you
seem to have installed two versions of the servlet api.
After the http feature, the jolokia bundle can be installed.
regards, Achim
10 matches
Mail list logo