apache-karaf

I am looking into ways to deploy and update an OSGI (Karaf, specifically) application. It seems that there are several options. One is to use The OSGi Bundle Repository (OBR), another is to use Features in Karaf, and the third is to use Karaf Cave . I'm not really sure how these options are really different. They all seem to be doing the same things. Are they just different implementations of the same functionality? Could someone please explain the differences or provide some recommendations? Karaf features and OBR are different ways of solving the (sort of) same problem. Both allow you to

I'm using apacheservicemix and I try to validate a xml document with apache camel. I have this route called students_route.xml : <?xml version="1.0" encoding="UTF-8"?> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation=" http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd"> <camelContext xmlns="http://camel.apache.org/schema/blueprint"> <route> <from uri="file:project/students.xml"/> <doTry> <to uri="validator:file:project/students.xsd"/> <to uri="file:valid"/>

Is anyone using Karaf instead of Servicemix? If so, how did you come to this decision? I'm aware that Servicemix adds a layer of functionality around Karaf, just curious if Karaf is being used on its own and why... earcam We're using Karaf for a number of our applications. We were already using Camel (JMS and Esper) for integration between several different platforms (a JBoss 4.2 instance, a Tomcat and several Felix instances) and as this was working well there was little justification in migrating this too (which would have been cause to consider ServiceMix). The only reason we have some

I have some services in tomcat and trying to move to apache karaf. I have a existing service which uses logback for logging configuration. I tried to make same configuration in osgi, but could not achieve. Any please let me know what could be the problem? org.ops4j.pax.logging.cfg org.ops4j.pax.logging.logback.config.file=${karaf.home}/etc/logback.xml logback.xml is available at ${karaf.home}/etc/ --. Apache Karaf version : 3.0 , pax logging 1.7.1 which is packaged with karaf from build. After above configuration change, my karaf.log contents are : Jul 02, 2014 4:21:32 PM org.apache.karaf.main

I have creating a simple Kafka Producer & Consumer.I am using kafka_2.11-0.9.0.0. Here is my Producer code, public class KafkaProducerTest { public static String topicName = "test-topic-2"; public static void main(String[] args) { // TODO Auto-generated method stub Properties props = new Properties(); props.put("bootstrap.servers", "localhost:9092"); props.put("acks", "all"); props.put("retries", 0); props.put("batch.size", 16384); props.put("linger.ms", 1); props.put("buffer.memory", 33554432); props.put("key.serializer", StringSerializer.class.getName()); props.put("value.serializer",

I decided to build an application on top of OSGI and Karaf - I really like this stuff. However, I'm struggling a bit with a daily deployment on my local, development machine. I mean.. I make a change and then I would like to test it on my local Karaf instance. And it can happen like couple times per hour. The way I'm doing it now is a maven build that creates a JAR bundle and then it's copied into the Karaf's deploy directory. I think that it isn't elegant at all. I was trying to find a way around (google). I read about Karaf's features but it seems that despite the fact that it is a nice

Apache Karaf is a sub project of Apache Felix . It is defined as "a lightweight OSGi container". I don't understand when should I use the heavyweight and when to use the lightweight. Their site doesn't explain this too much. The 'lightweight OSGi container' label is contrasting Karaf with more feature rich OSGi containers, not with Felix . To quote Guillaume Nodet (Karaf's author) from here : Felix is just the OSGi core runtime. Karaf provides a "distribution" based on Felix by adding other features such as a console, an SSH remoting mechanism, a file deployer and more. In this diagram of the