diff --git a/build.gradle b/build.gradle
index c7802a38..e9b9a1a2 100644
--- a/build.gradle
+++ b/build.gradle
@@ -3,10 +3,23 @@ def projectNameLowerCase = 'openmuc'
configure(allprojects) {
apply plugin: 'java'
- version = '0.13.1'
+ version = '0.14.0'
group = 'org.openmuc.framework'
}
+allprojects {
+ gradle.projectsEvaluated {
+ tasks.withType(JavaCompile) {
+ options.encoding = "UTF-8"
+ options.compilerArgs << "-Xlint:unchecked" << "-Xlint:deprecation"
+ }
+ }
+
+ javadoc {
+ options.encoding = "UTF-8"
+ }
+}
+
project.ext {
distributionProjects = subprojects.findAll {
it.getPath() == ':openmuc-core-api' ||
@@ -21,6 +34,7 @@ project.ext {
it.getPath() == ':openmuc-driver-iec62056p21' ||
it.getPath() == ':openmuc-driver-knx' ||
it.getPath() == ':openmuc-driver-mbus' ||
+ it.getPath() == ':openmuc-driver-wmbus' ||
it.getPath() == ':openmuc-driver-modbus' ||
it.getPath() == ':openmuc-driver-s7plc' ||
it.getPath() == ':openmuc-driver-snmp' ||
@@ -33,8 +47,7 @@ project.ext {
it.getPath() == ':openmuc-webui-channelconfigurator' ||
it.getPath() == ':openmuc-webui-userconfigurator' ||
it.getPath() == ':openmuc-server-restws' ||
- it.getPath() == ':openmuc-server-asciisocket' ||
- it.getPath() == ':openmuc-server-modbus'
+ it.getPath() == ':openmuc-server-asciisocket'
}
docProjects = distributionProjects.findAll {
@@ -55,8 +68,7 @@ configure(subprojects) {
targetCompatibility = 1.6
repositories {
- mavenCentral()
-// maven { url 'http://repo1.maven.org/maven2/' }
+ mavenCentral()
flatDir {
dirs 'dependencies', rootDir.getPath() + "/dependencies"
}
@@ -88,7 +100,6 @@ configure(subprojects) {
uploadArchives {
repositories {
mavenDeployer {
- beforeDeployment { MavenDeployment deployment -> signing.signPom(deployment) }
repository(url: project.properties.repository) {
authentication(userName: project.properties.artifactoryUser, password: project.properties.artifactoryPass)
@@ -206,7 +217,6 @@ task(tar, type: Tar) {
include 'demo/framework/felix/**'
include 'demo/framework/bundle/**'
include 'demo/framework/conf/**'
- include 'demo/framework/openmuc-config.xml'
include 'demo/framework/README.txt'
include 'demo/framework/run-openmuc.bat.winfile'
include 'demo/framework/build.gradle'
diff --git a/demo/framework/build.gradle b/demo/framework/build.gradle
index 6c35ebc4..c37955a2 100644
--- a/demo/framework/build.gradle
+++ b/demo/framework/build.gradle
@@ -6,7 +6,7 @@ configurations.create('osgibundles')
configurations.osgibundles.transitive = false;
dependencies {
- def openmucversion = '0.13.1'
+ def openmucversion = '0.14.0'
osgibundles files('../../build/libs/openmuc-core-api-' + openmucversion + '.jar')
osgibundles files('../../build/libs/openmuc-core-spi-' + openmucversion + '.jar')
@@ -26,39 +26,55 @@ dependencies {
osgibundles files('../projects/simpleappdemo/build/libs/openmuc-demo-simpleapp-' + openmucversion + '.jar')
osgibundles files('../projects/dummydriver/build/libs/openmuc-driver-dummy-' + openmucversion + '.jar')
- //The Apache Felix Gogo standard shell for OSGi (http://felix.apache.org/site/apache-felix-gogo.html)
+ //--------------------------------------------------------------------------------------------------
+ // The Apache Felix Gogo standard shell for OSGi (http://felix.apache.org/site/apache-felix-gogo.html)
+ //--------------------------------------------------------------------------------------------------
osgibundles group: 'org.apache.felix', name: 'org.apache.felix.gogo.runtime', version: '0.12.1'
osgibundles group: 'org.apache.felix', name: 'org.apache.felix.gogo.command', version: '0.14.0'
osgibundles group: 'org.apache.felix', name: 'org.apache.felix.gogo.shell', version: '0.10.0'
- //Adds a telnet server so that the Felix Gogo Shell can be accessed
- //using telnet clients. By default this server only listens on
- //localhost port 6666. Therefor you can on only access it from the
- //same host on which felix is running.
+ //--------------------------------------------------------------------------------------------------
+ // Adds a telnet server so that the Felix Gogo Shell can be accessed
+ // using telnet clients. By default this server only listens on
+ // localhost port 6666. Therefor you can on only access it from the
+ // same host on which felix is running.
+ //--------------------------------------------------------------------------------------------------
osgibundles group: 'org.apache.felix', name: 'org.apache.felix.shell.remote', version: '1.1.2'
- //message logging libraries, SLF4J is a light-weight logging API,
- //Logback is a message logger implementation that implements SLF4J
- //natively
- osgibundles group: 'org.slf4j', name: 'slf4j-api', version: '1.7.7'
+ //--------------------------------------------------------------------------------------------------
+ // message logging libraries, SLF4J is a light-weight logging API,
+ // Logback is a message logger implementation that implements SLF4J
+ // natively
+ //--------------------------------------------------------------------------------------------------
+ osgibundles group: 'org.slf4j', name: 'slf4j-api', version: '1.7.10'
osgibundles group: 'ch.qos.logback', name: 'logback-classic', version: '1.1.2'
osgibundles group: 'ch.qos.logback', name: 'logback-core', version: '1.1.2'
- //Apache Felix Service Component Runtime that implements the OSGi Declarative Services Specification
- //the OpenMUC core bundles use declarative services and thus depend on them
+ //--------------------------------------------------------------------------------------------------
+ // Apache Felix Service Component Runtime that implements the OSGi Declarative Services Specification
+ // the OpenMUC core bundles use declarative services and thus depend on them
+ //--------------------------------------------------------------------------------------------------
osgibundles group: 'org.apache.felix', name: 'org.apache.felix.scr', version: '1.8.2'
- //An implementation of the OSGi HTTP Service Specification, needed by the WebUI bundles
- osgibundles group: 'org.apache.felix', name: 'org.apache.felix.http.bundle', version: '2.3.0'
- //Implementation of the OSGi Event Admin Service needed by org.apache.felix.http.jetty
- osgibundles group: 'org.apache.felix', name: 'org.apache.felix.eventadmin', version: '1.4.0'
+ //--------------------------------------------------------------------------------------------------
+ // An implementation of the OSGi HTTP Service Specification, needed by the WebUI bundles
+ //--------------------------------------------------------------------------------------------------
+ osgibundles group: 'org.apache.felix', name: 'org.apache.felix.http.bundle', version: '2.3.2'
+ //--------------------------------------------------------------------------------------------------
+ // Implementation of the OSGi Event Admin Service needed by org.apache.felix.http.jetty
+ //--------------------------------------------------------------------------------------------------
+ osgibundles group: 'org.apache.felix', name: 'org.apache.felix.eventadmin', version: '1.4.2'
- //An implementation of the OSGi Configuration Admin Service, needed by the BundleConfigurator WebUI
- //to enable users to dynamically configure running bundles.
+ //--------------------------------------------------------------------------------------------------
+ // An implementation of the OSGi Configuration Admin Service, needed by the BundleConfigurator WebUI
+ // to enable users to dynamically configure running bundles.
+ //--------------------------------------------------------------------------------------------------
osgibundles group: 'org.apache.felix', name: 'org.apache.felix.configadmin', version: '1.8.0'
- //An implementation of the OSGi MetaType Service, needed by the BundleConfigurator WebUI to receive
- //information about the running bundles:
+ //--------------------------------------------------------------------------------------------------
+ // An implementation of the OSGi MetaType Service, needed by the BundleConfigurator WebUI to receive
+ // information about the running bundles:
+ //--------------------------------------------------------------------------------------------------
osgibundles group: 'org.apache.felix', name: 'org.apache.felix.metatype', version: '1.0.10'
}
diff --git a/demo/framework/bundle/openmuc-core-api-0.13.1.jar b/demo/framework/bundle/openmuc-core-api-0.14.0.jar
similarity index 70%
rename from demo/framework/bundle/openmuc-core-api-0.13.1.jar
rename to demo/framework/bundle/openmuc-core-api-0.14.0.jar
index f0d7fab1..30d584da 100644
Binary files a/demo/framework/bundle/openmuc-core-api-0.13.1.jar and b/demo/framework/bundle/openmuc-core-api-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-core-datamanager-0.13.1.jar b/demo/framework/bundle/openmuc-core-datamanager-0.13.1.jar
deleted file mode 100644
index 29ddcf19..00000000
Binary files a/demo/framework/bundle/openmuc-core-datamanager-0.13.1.jar and /dev/null differ
diff --git a/demo/framework/bundle/openmuc-core-datamanager-0.14.0.jar b/demo/framework/bundle/openmuc-core-datamanager-0.14.0.jar
new file mode 100644
index 00000000..d1205188
Binary files /dev/null and b/demo/framework/bundle/openmuc-core-datamanager-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-core-spi-0.13.1.jar b/demo/framework/bundle/openmuc-core-spi-0.13.1.jar
deleted file mode 100644
index 03a1452a..00000000
Binary files a/demo/framework/bundle/openmuc-core-spi-0.13.1.jar and /dev/null differ
diff --git a/demo/framework/bundle/openmuc-core-spi-0.14.0.jar b/demo/framework/bundle/openmuc-core-spi-0.14.0.jar
new file mode 100644
index 00000000..a6d65b2b
Binary files /dev/null and b/demo/framework/bundle/openmuc-core-spi-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-datalogger-ascii-0.13.1.jar b/demo/framework/bundle/openmuc-datalogger-ascii-0.13.1.jar
deleted file mode 100644
index f40637dd..00000000
Binary files a/demo/framework/bundle/openmuc-datalogger-ascii-0.13.1.jar and /dev/null differ
diff --git a/demo/framework/bundle/openmuc-datalogger-ascii-0.14.0.jar b/demo/framework/bundle/openmuc-datalogger-ascii-0.14.0.jar
new file mode 100644
index 00000000..bd1a2e16
Binary files /dev/null and b/demo/framework/bundle/openmuc-datalogger-ascii-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-datalogger-slotsdb-0.13.1.jar b/demo/framework/bundle/openmuc-datalogger-slotsdb-0.14.0.jar
similarity index 83%
rename from demo/framework/bundle/openmuc-datalogger-slotsdb-0.13.1.jar
rename to demo/framework/bundle/openmuc-datalogger-slotsdb-0.14.0.jar
index dee13520..b62fee7f 100644
Binary files a/demo/framework/bundle/openmuc-datalogger-slotsdb-0.13.1.jar and b/demo/framework/bundle/openmuc-datalogger-slotsdb-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-demo-simpleapp-0.13.1.jar b/demo/framework/bundle/openmuc-demo-simpleapp-0.14.0.jar
similarity index 68%
rename from demo/framework/bundle/openmuc-demo-simpleapp-0.13.1.jar
rename to demo/framework/bundle/openmuc-demo-simpleapp-0.14.0.jar
index 36488b62..5c6fcb2e 100644
Binary files a/demo/framework/bundle/openmuc-demo-simpleapp-0.13.1.jar and b/demo/framework/bundle/openmuc-demo-simpleapp-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-driver-dummy-0.13.1.jar b/demo/framework/bundle/openmuc-driver-dummy-0.13.1.jar
deleted file mode 100644
index 1c45b3d6..00000000
Binary files a/demo/framework/bundle/openmuc-driver-dummy-0.13.1.jar and /dev/null differ
diff --git a/demo/framework/bundle/openmuc-driver-dummy-0.14.0.jar b/demo/framework/bundle/openmuc-driver-dummy-0.14.0.jar
new file mode 100644
index 00000000..3d3fe9de
Binary files /dev/null and b/demo/framework/bundle/openmuc-driver-dummy-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-server-restws-0.13.1.jar b/demo/framework/bundle/openmuc-server-restws-0.13.1.jar
deleted file mode 100644
index 89dc5e2c..00000000
Binary files a/demo/framework/bundle/openmuc-server-restws-0.13.1.jar and /dev/null differ
diff --git a/demo/framework/bundle/openmuc-server-restws-0.14.0.jar b/demo/framework/bundle/openmuc-server-restws-0.14.0.jar
new file mode 100644
index 00000000..4d245a45
Binary files /dev/null and b/demo/framework/bundle/openmuc-server-restws-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-webui-base-0.13.1.jar b/demo/framework/bundle/openmuc-webui-base-0.14.0.jar
similarity index 99%
rename from demo/framework/bundle/openmuc-webui-base-0.13.1.jar
rename to demo/framework/bundle/openmuc-webui-base-0.14.0.jar
index 3a3404eb..ec37010c 100644
Binary files a/demo/framework/bundle/openmuc-webui-base-0.13.1.jar and b/demo/framework/bundle/openmuc-webui-base-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-webui-bundleconfigurator-0.13.1.jar b/demo/framework/bundle/openmuc-webui-bundleconfigurator-0.14.0.jar
similarity index 98%
rename from demo/framework/bundle/openmuc-webui-bundleconfigurator-0.13.1.jar
rename to demo/framework/bundle/openmuc-webui-bundleconfigurator-0.14.0.jar
index 5a3fb1ef..52a5cecc 100644
Binary files a/demo/framework/bundle/openmuc-webui-bundleconfigurator-0.13.1.jar and b/demo/framework/bundle/openmuc-webui-bundleconfigurator-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-webui-channelaccesstool-0.13.1.jar b/demo/framework/bundle/openmuc-webui-channelaccesstool-0.14.0.jar
similarity index 72%
rename from demo/framework/bundle/openmuc-webui-channelaccesstool-0.13.1.jar
rename to demo/framework/bundle/openmuc-webui-channelaccesstool-0.14.0.jar
index eebad2f1..046eb8cb 100644
Binary files a/demo/framework/bundle/openmuc-webui-channelaccesstool-0.13.1.jar and b/demo/framework/bundle/openmuc-webui-channelaccesstool-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-webui-channelconfigurator-0.13.1.jar b/demo/framework/bundle/openmuc-webui-channelconfigurator-0.14.0.jar
similarity index 53%
rename from demo/framework/bundle/openmuc-webui-channelconfigurator-0.13.1.jar
rename to demo/framework/bundle/openmuc-webui-channelconfigurator-0.14.0.jar
index 9cefaa74..2ce55750 100644
Binary files a/demo/framework/bundle/openmuc-webui-channelconfigurator-0.13.1.jar and b/demo/framework/bundle/openmuc-webui-channelconfigurator-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-webui-dataexporter-0.13.1.jar b/demo/framework/bundle/openmuc-webui-dataexporter-0.14.0.jar
similarity index 80%
rename from demo/framework/bundle/openmuc-webui-dataexporter-0.13.1.jar
rename to demo/framework/bundle/openmuc-webui-dataexporter-0.14.0.jar
index 7755970e..0f388a41 100644
Binary files a/demo/framework/bundle/openmuc-webui-dataexporter-0.13.1.jar and b/demo/framework/bundle/openmuc-webui-dataexporter-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-webui-dataplotter-0.13.1.jar b/demo/framework/bundle/openmuc-webui-dataplotter-0.14.0.jar
similarity index 97%
rename from demo/framework/bundle/openmuc-webui-dataplotter-0.13.1.jar
rename to demo/framework/bundle/openmuc-webui-dataplotter-0.14.0.jar
index 69b7b126..7dfd751c 100644
Binary files a/demo/framework/bundle/openmuc-webui-dataplotter-0.13.1.jar and b/demo/framework/bundle/openmuc-webui-dataplotter-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-webui-spi-0.13.1.jar b/demo/framework/bundle/openmuc-webui-spi-0.14.0.jar
similarity index 70%
rename from demo/framework/bundle/openmuc-webui-spi-0.13.1.jar
rename to demo/framework/bundle/openmuc-webui-spi-0.14.0.jar
index f6e10da3..b1a8d503 100644
Binary files a/demo/framework/bundle/openmuc-webui-spi-0.13.1.jar and b/demo/framework/bundle/openmuc-webui-spi-0.14.0.jar differ
diff --git a/demo/framework/bundle/openmuc-webui-userconfigurator-0.13.1.jar b/demo/framework/bundle/openmuc-webui-userconfigurator-0.14.0.jar
similarity index 74%
rename from demo/framework/bundle/openmuc-webui-userconfigurator-0.13.1.jar
rename to demo/framework/bundle/openmuc-webui-userconfigurator-0.14.0.jar
index 8fa21103..c22295d5 100644
Binary files a/demo/framework/bundle/openmuc-webui-userconfigurator-0.13.1.jar and b/demo/framework/bundle/openmuc-webui-userconfigurator-0.14.0.jar differ
diff --git a/demo/framework/bundle/org.apache.felix.eventadmin-1.4.0.jar b/demo/framework/bundle/org.apache.felix.eventadmin-1.4.2.jar
similarity index 60%
rename from demo/framework/bundle/org.apache.felix.eventadmin-1.4.0.jar
rename to demo/framework/bundle/org.apache.felix.eventadmin-1.4.2.jar
index 796b9d81..1df22266 100644
Binary files a/demo/framework/bundle/org.apache.felix.eventadmin-1.4.0.jar and b/demo/framework/bundle/org.apache.felix.eventadmin-1.4.2.jar differ
diff --git a/demo/framework/bundle/org.apache.felix.http.bundle-2.3.0.jar b/demo/framework/bundle/org.apache.felix.http.bundle-2.3.2.jar
similarity index 92%
rename from demo/framework/bundle/org.apache.felix.http.bundle-2.3.0.jar
rename to demo/framework/bundle/org.apache.felix.http.bundle-2.3.2.jar
index b73f7a2a..b08f8944 100644
Binary files a/demo/framework/bundle/org.apache.felix.http.bundle-2.3.0.jar and b/demo/framework/bundle/org.apache.felix.http.bundle-2.3.2.jar differ
diff --git a/demo/framework/bundle/slf4j-api-1.7.10.jar b/demo/framework/bundle/slf4j-api-1.7.10.jar
new file mode 100644
index 00000000..744e9ec5
Binary files /dev/null and b/demo/framework/bundle/slf4j-api-1.7.10.jar differ
diff --git a/demo/framework/bundle/slf4j-api-1.7.7.jar b/demo/framework/bundle/slf4j-api-1.7.7.jar
deleted file mode 100644
index bebabd96..00000000
Binary files a/demo/framework/bundle/slf4j-api-1.7.7.jar and /dev/null differ
diff --git a/demo/framework/openmuc-config.xml b/demo/framework/conf/channels.xml
similarity index 100%
rename from demo/framework/openmuc-config.xml
rename to demo/framework/conf/channels.xml
diff --git a/demo/framework/conf/logback.xml b/demo/framework/conf/logback.xml
index b8afe0bd..5e7941b7 100644
--- a/demo/framework/conf/logback.xml
+++ b/demo/framework/conf/logback.xml
@@ -20,6 +20,5 @@
-
diff --git a/demo/framework/conf/system.properties b/demo/framework/conf/system.properties
index 9b1b36fe..e99c7ef2 100644
--- a/demo/framework/conf/system.properties
+++ b/demo/framework/conf/system.properties
@@ -2,28 +2,34 @@
logback.configurationFile=conf/logback.xml
java.util.logging.config.file=conf/jul.properties
+# Required by Apache Felix to enable the HTTP Server
+org.apache.felix.http.jettyEnabled=true
+
+# set the location of the channel config file
+# the default is conf/channels.xml
+#org.openmuc.framework.channelconfig=conf/channels.xml
+
# Required by jSSDP. This configuration makes OpenMUC announce its REST-Service as a SSDP Multicast Message
-org.openmuc.framework.util.ssdp.rest.searchtarget=openmuc:rest
-org.openmuc.framework.util.ssdp.rest.uri.prefix=http://
-org.openmuc.framework.util.ssdp.rest.uri.port=8888
-org.openmuc.framework.util.ssdp.rest.uri.suffix=/rest
+#org.openmuc.framework.util.ssdp.rest.searchtarget=openmuc:rest
+#org.openmuc.framework.util.ssdp.rest.uri.prefix=http://
+#org.openmuc.framework.util.ssdp.rest.uri.port=8888
+#org.openmuc.framework.util.ssdp.rest.uri.suffix=/rest
# Set this value to true, if you want to have the unscaled value in the modbus server. (Default: false)
# This helps to translate modbus-rtu into modbus-tcp.
# Example: Register content: "803" which has to be interpreted as "80,3".
# By defining the Channel as Double Value and specifying a scalingFactor of "0.1" OpenMUC will internally display
# the input as a correct floating point value. On Modbus-TCP Server it will again be "803" if set to true. "80" if false.
-org.openmuc.framework.server.modbus.useUnscaledValues=false
+#org.openmuc.framework.server.modbus.useUnscaledValues=false
# If false (default) then https is used for writing channels via PUT requests.
# If true then the unsecure http is used for writing channels via PUT requests.
-org.openmuc.framework.server.restws.channel.ChannelResource.enableHttpWrite=false
+#org.openmuc.framework.server.restws.channel.ChannelResource.enableHttpWrite=false
# Set all combinations of serial ports / ttys. This fixes bugs on most of the embedded Linux Systems
-gnu.io.rxtx.SerialPorts=/dev/ttyACM0:/dev/ttyACM1:/dev/ttyACM2:/dev/ttyACM3:/dev/ttyACM4:/dev/ttyACM5:/dev/ttyACM6:/dev/ttyACM7:/dev/ttyACM8:/dev/ttyACM9:/dev/ttyACM10:/dev/ttyAMA0:/dev/ttyAMA1:/dev/ttyAMA2:/dev/ttyAMA3:/dev/ttyAMA4:/dev/ttyAMA5:/dev/ttyAMA6:/dev/ttyAMA7:/dev/ttyAMA8:/dev/ttyAMA9:/dev/ttyAMA10:/dev/ttyUSB0:/dev/ttyUSB1:/dev/ttyUSB2:/dev/ttyUSB3:/dev/ttyUSB4:/dev/ttyUSB5:/dev/ttyUSB6:/dev/ttyUSB7:/dev/ttyUSB8:/dev/ttyUSB9:/dev/ttyUSB10:/dev/ttyS0:/dev/ttyS1:/dev/ttyS2:/dev/ttyS3:/dev/ttyS4:/dev/ttyS5:/dev/ttyS6:/dev/ttyS7:/dev/ttyS8:/dev/ttyS9:/dev/ttyS10:/dev/ttyO0:/dev/ttyO1:/dev/ttyO2:/dev/ttyO3:/dev/ttyO4:/dev/ttyO5:/dev/ttyO6:/dev/ttyO7:/dev/ttyO8:/dev/ttyO9:/dev/ttyO10:COM0:COM1:COM2:COM3:COM4:COM5:COM6:COM7:COM8:COM9:COM10:COM11:COM12:COM13:COM14:COM15:COM16:COM17:COM18:COM19:COM20
+#gnu.io.rxtx.SerialPorts=/dev/ttyACM0:/dev/ttyACM1:/dev/ttyACM2:/dev/ttyACM3:/dev/ttyACM4:/dev/ttyACM5:/dev/ttyACM6:/dev/ttyACM7:/dev/ttyACM8:/dev/ttyACM9:/dev/ttyACM10:/dev/ttyAMA0:/dev/ttyAMA1:/dev/ttyAMA2:/dev/ttyAMA3:/dev/ttyAMA4:/dev/ttyAMA5:/dev/ttyAMA6:/dev/ttyAMA7:/dev/ttyAMA8:/dev/ttyAMA9:/dev/ttyAMA10:/dev/ttyUSB0:/dev/ttyUSB1:/dev/ttyUSB2:/dev/ttyUSB3:/dev/ttyUSB4:/dev/ttyUSB5:/dev/ttyUSB6:/dev/ttyUSB7:/dev/ttyUSB8:/dev/ttyUSB9:/dev/ttyUSB10:/dev/ttyS0:/dev/ttyS1:/dev/ttyS2:/dev/ttyS3:/dev/ttyS4:/dev/ttyS5:/dev/ttyS6:/dev/ttyS7:/dev/ttyS8:/dev/ttyS9:/dev/ttyS10:/dev/ttyO0:/dev/ttyO1:/dev/ttyO2:/dev/ttyO3:/dev/ttyO4:/dev/ttyO5:/dev/ttyO6:/dev/ttyO7:/dev/ttyO8:/dev/ttyO9:/dev/ttyO10:COM0:COM1:COM2:COM3:COM4:COM5:COM6:COM7:COM8:COM9:COM10:COM11:COM12:COM13:COM14:COM15:COM16:COM17:COM18:COM19:COM20
# TBD.
org.eclipse.jetty.server.Request.maxFormKeys=2000
-# Required by Apache Felix to enable the HTTP Server
-org.apache.felix.http.jettyEnabled=true
+
diff --git a/demo/framework/felix/felix-4.4.1-doc/DEPENDENCIES b/demo/framework/felix/felix-4.6.0-doc/DEPENDENCIES
similarity index 86%
rename from demo/framework/felix/felix-4.4.1-doc/DEPENDENCIES
rename to demo/framework/felix/felix-4.6.0-doc/DEPENDENCIES
index ac01909e..ce175835 100644
--- a/demo/framework/felix/felix-4.4.1-doc/DEPENDENCIES
+++ b/demo/framework/felix/felix-4.6.0-doc/DEPENDENCIES
@@ -1,5 +1,5 @@
Apache Felix Main Distribution
-Copyright 2013 The Apache Software Foundation
+Copyright 2015 The Apache Software Foundation
This software was developed at the Apache Software Foundation
(http://www.apache.org) and may have dependencies on other
@@ -9,7 +9,7 @@ I. Included Third-Party Software
This product includes software developed at
The OSGi Alliance (http://www.osgi.org/).
-Copyright (c) OSGi Alliance (2000, 2012).
+Copyright (c) OSGi Alliance (2000, 2014).
Licensed under the Apache License 2.0.
This product includes software from http://kxml.sourceforge.net.
@@ -20,7 +20,7 @@ II. Used Third-Party Software
This product uses software developed at
The OSGi Alliance (http://www.osgi.org/).
-Copyright (c) OSGi Alliance (2000, 2012).
+Copyright (c) OSGi Alliance (2000, 2014).
Licensed under the Apache License 2.0.
This product uses software developed at
diff --git a/demo/framework/felix/felix-4.4.1-doc/LICENSE b/demo/framework/felix/felix-4.6.0-doc/LICENSE
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/LICENSE
rename to demo/framework/felix/felix-4.6.0-doc/LICENSE
diff --git a/demo/framework/felix/felix-4.4.1-doc/LICENSE.kxml2 b/demo/framework/felix/felix-4.6.0-doc/LICENSE.kxml2
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/LICENSE.kxml2
rename to demo/framework/felix/felix-4.6.0-doc/LICENSE.kxml2
diff --git a/demo/framework/felix/felix-4.4.1-doc/NOTICE b/demo/framework/felix/felix-4.6.0-doc/NOTICE
similarity index 84%
rename from demo/framework/felix/felix-4.4.1-doc/NOTICE
rename to demo/framework/felix/felix-4.6.0-doc/NOTICE
index ad3a64fb..1cf00224 100644
--- a/demo/framework/felix/felix-4.4.1-doc/NOTICE
+++ b/demo/framework/felix/felix-4.6.0-doc/NOTICE
@@ -1,5 +1,5 @@
Apache Felix Main Distribution
-Copyright 2014 The Apache Software Foundation
+Copyright 2015 The Apache Software Foundation
This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).
@@ -7,7 +7,7 @@ Licensed under the Apache License 2.0.
This product includes software developed at
The OSGi Alliance (http://www.osgi.org/).
-Copyright (c) OSGi Alliance (2000, 2012).
+Copyright (c) OSGi Alliance (2000, 2014).
Licensed under the Apache License 2.0.
This product includes software from http://kxml.sourceforge.net.
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties.html b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties.html
similarity index 66%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties.html
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties.html
index 045f998a..f5a04dd7 100644
--- a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties.html
+++ b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties.html
@@ -1,12 +1,10 @@
-
+
Apache Felix - Apache Felix Framework Configuration Properties
-
+
@@ -22,41 +20,30 @@
This document describes the various configuration properties related
to the Apache Felix Framework. Technically, there are framework
properties and launcher properties. If you are using the Felix
- Framework JAR file (i.e., org.apache.felix.framework-x.y.x.jar), then you can only
- use framework properties. On the other hand, if you are using the Felix Main launcher JAR
- (i.e., felix.jar or org.apache.felix.main-x.y.z.jar), then you can use
- both framework and launcher properties. This document will describe both sets of properties.
-
+ Framework JAR file (i.e., org.apache.felix.framework-x.y.x.jar), then you can only use framework properties. On the other
+ hand, if you are using the Felix Main launcher JAR (i.e., felix.jar or org.apache.felix.main-x.y.z.jar), then you
+ can use both framework and launcher properties. This document will describe both sets of properties.
Note that the framework does not use system properties to find its
configuration properties, it only consults the map passed into its
@@ -83,17 +68,14 @@
Overview<
launcher, it will copy all configuration properties it finds in the
system properties to the configuration map passed into the framework
constructor, which allows you to set configuration properties on the
- command line. This feature is not available if you are just using the Felix framework
- JAR file.
+ command line. This feature is not available if you are just using the Felix framework JAR file.
-
Framework
- configuration properties
+
Framework configuration properties
-
The following configuration properties are for the framework (properties starting with "felix"
- are specific to Felix, while those starting with "org.osgi" are standard OSGi
- properties):
+
The following configuration properties are for the framework (properties starting with "felix" are specific to Felix, while
+ those starting with "org.osgi" are standard OSGi properties):
org.osgi.framework.executionenvironment - Sets the
@@ -102,23 +84,22 @@
The following configuration properties are for the launcher:
-
felix.auto.deploy.dir - Specifies the auto-deploy directory from which bundles
- are automatically deployed at framework startup. The default is the bundle/
- directory of the current directory.
+
felix.auto.deploy.dir - Specifies the auto-deploy directory from which bundles are automatically deployed at framework
+ startup. The default is the bundle/ directory of the current directory.
felix.auto.deploy.action
- Specifies a comma-delimited list of actions to be performed on bundle
- JAR files found in the auto-deploy directory. The possible actions are install,
- update, start, and uninstall.
+ JAR files found in the auto-deploy directory. The possible actions are install, update, start, and
+ uninstall.
An undefined or blank value is equivalent to disabling auto-deploy
processing; there is no default value, so this value must be defined to
enable it.
-
felix.auto.install.<n> - Space-delimited list of bundle URLs to
- automatically install when Felix is started, where <n> is the start level
- into which the bundle will be installed (e.g., felix.auto.install.2).
+
felix.auto.install.<n> - Space-delimited list of bundle URLs to automatically install when Felix is started,
+ where <n> is the start level into which the bundle will be installed (e.g., felix.auto.install.2).
-
felix.auto.start.<n> - Space-delimited list of bundle URLs to
- automatically install and start when Felix is started, where <n> is the
- start level into which the bundle will be installed (e.g., felix.auto.start.2).
+
felix.auto.start.<n> - Space-delimited list of bundle URLs to automatically install and start when Felix is
+ started, where <n> is the start level into which the bundle will be installed (e.g., felix.auto.start.2).
felix.shutdown.hook
- Specifies whether the launcher should install a shutdown hook to
@@ -231,8 +202,7 @@
-
Migrating
- from Earlier Versions
+
Migrating from Earlier Versions
Apache Felix Framework 2.0.0 introduced significant
configuration property changes. This section describes the differences
@@ -241,44 +211,36 @@
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/apache.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/apache.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/apache.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/apache.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/button.html b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/button.html
similarity index 55%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/button.html
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/button.html
index 8d2e211b..320aeb10 100644
--- a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/button.html
+++ b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/button.html
@@ -3,9 +3,8 @@
-
+
\ No newline at end of file
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/button_data/2010-na-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/button_data/2010-na-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/button_data/2010-na-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/button_data/2010-na-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/logo.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/logo.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/logo.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/logo.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/site.css b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/site.css
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-configuration-properties_files/site.css
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-configuration-properties_files/site.css
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding.html b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding.html
similarity index 79%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding.html
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding.html
index 87d0646d..407ee44b 100644
--- a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding.html
+++ b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding.html
@@ -1,12 +1,10 @@
-
+
Apache Felix - Apache Felix Framework Launching and Embedding
-
+
@@ -22,32 +20,24 @@
The Felix framework is implemented by the org.apache.felix.framework.Felix class or
- just Felix
+
The Felix framework is implemented by the org.apache.felix.framework.Felix class or just Felix
for short. As part of the R4.2 OSGi specification, the launching and
embedding API of the OSGi framework has been standardized. The approach
- is to have the framework implement the org.osgi.framework.launch.Framework
- interface, which extends the org.osgi.framework.Bundle interface. These interfaces
- provide the necessary means to launch and manage framework instances. The Bundle
- interface is defined as:
+ is to have the framework implement the org.osgi.framework.launch.Framework interface, which extends the org.osgi.framework.Bundle
+ interface. These interfaces provide the necessary means to launch and manage framework instances. The Bundle interface is
+ defined as:
The framework factory can be used to create configured framework instances. It is obtained
- following the standard META-INF/services approach.
+
The framework factory can be used to create configured framework instances. It is obtained following the standard META-INF/services
+ approach.
-
- Creating
- and Configuring the Framework Instance
+
Creating and Configuring the
+ Framework Instance
You use the framework factory to construct and configure a framework
instance (or by directly instantiating the Felix class). The
configuration map may contain any of the framework configuration
- properties listed in the Apache Felix Framework
- Configuration Properties
+ properties listed in the Apache Felix Framework Configuration
+ Properties
document, not the launcher configuration properties. The configuration
map is copied and the keys are treated as case insensitive. You are not
able to change the framework's configuration after construction. If you
@@ -224,12 +195,11 @@
-
-
WARNING Felix configuration properties have change considerably
- starting from 1.4.0; if you are upgrading from an earlier version, the
- configuration
+
+
WARNING Felix configuration properties have change considerably starting from 1.4.0; if you are
+ upgrading from an earlier version, the configuration
property document describes the configuration property changes.
@@ -239,62 +209,49 @@
-
Starting
- the Framework Instance
+
Starting the Framework Instance
-
The start() method is used to start the framework instance. If the init()
- method was not invoked prior to calling start(), then it is invoked by
- start(). The two methods result in two different framework state transitions:
+
The start() method is used to start the framework instance. If the init() method was not invoked prior to calling
+ start(), then it is invoked by start(). The two methods result in two different framework state transitions:
-
init() results in the framework instance in the Bundle.STARTING state.
-
-
start() results in the framework instance in the Bundle.ACTIVE state.
-
+
init() results in the framework instance in the Bundle.STARTING state.
+
start() results in the framework instance in the Bundle.ACTIVE state.
-
The init() method is necessary since the framework does not have a
- BundleContext when it is first created, so a transition to the
- Bundle.STARTING state is required to acquire its context (via Bundle.getBundleContext())
- for performing various tasks, such as installing bundles. Note that the Felix framework also
- provides the felix.systembundle.activators property that serves a similar purpose,
- but is not standard. After the init() method completes, the follow actions have
+
The init() method is necessary since the framework does not have a BundleContext when it is first created, so a
+ transition to the Bundle.STARTING state is required to acquire its context (via Bundle.getBundleContext()) for
+ performing various tasks, such as installing bundles. Note that the Felix framework also provides the felix.systembundle.activators
+ property that serves a similar purpose, but is not standard. After the init() method completes, the follow actions have
been performed:
Event handling is enabled.
The security manager is installed if it is enabled.
The framework is set to start level 0.
-
All bundles in the bundle caches are reified and their state is set to Bundle.INSTALLED.
-
+
All bundles in the bundle caches are reified and their state is set to Bundle.INSTALLED.
The framework gets a valid BundleContext.
-
All framework-provided services are made available (e.g., PackageAdmin, StartLevel,
- etc.).
-
+
All framework-provided services are made available (e.g., PackageAdmin, StartLevel, etc.).
The framework enters the Bundle.STARTING state.
-
A call to start() is necessary to start the framework instance, if the
- init() method is invoked manually. Invoking init() or start() on
- an already started framework as no effect.
+
A call to start() is necessary to start the framework instance, if the init() method is invoked manually. Invoking
+ init() or start() on an already started framework as no effect.
-
Stopping
- the Framework Instance
+
Stopping the Framework Instance
-
To stop the framework instance, invoke the stop() method, which will asynchronously
- stop the framework. To know when the framework has finished its shutdown sequence, use the
- waitForStop() method to wait until it is complete. A stopped framework will be in
- the Bundle.RESOLVED state. It is possible to restart the framework, using the
- normal combination of init()/start() methods as previously described.
+
To stop the framework instance, invoke the stop() method, which will asynchronously stop the framework. To know when the
+ framework has finished its shutdown sequence, use the waitForStop() method to wait until it is complete. A stopped
+ framework will be in the Bundle.RESOLVED state. It is possible to restart the framework, using the normal combination of
+ init()/start() methods as previously described.
-
Launching a
- Framework
+
Launching a Framework
Launching a framework is fairly simple and involves only four steps:
@@ -313,37 +270,31 @@
Felix launcher defines reusable functionality to automatically install
and/or start bundles upon framework startup; see the usage
- document for more information on configuring the Felix framework and on the various
- configuration properties.
+ document for more information on configuring the Felix framework and on the various configuration properties.
-
The remainder of this section describes how the standard Felix launcher works as well as how
- to create a custom launcher.
+
The remainder of this section describes how the standard Felix launcher works as well as how to create a custom launcher.
-
Standard
- Felix Framework Launcher
+
Standard Felix Framework Launcher
The standard Felix framework launcher is very simple and is not
intended to solve every possible requirement; it is intended to work
for most standard situations. Most special launching requirements
should be resolved by creating a custom launcher. This section
describes how the standard launcher works. The following code
- represents the complete main() method of the standard launcher, each numbered
- comment will be described in more detail below:
+ represents the complete main() method of the standard launcher, each numbered comment will be described in more detail
+ below:
Create a framework instance using the FrameworkFactory passing in the configuration properties, then initialize the
+ factory instance; see the custom launcher example below
+ to see how the META-INF/services FrameworkFactory is obtained.
-
Use org.apache.felix.main.AutoProcessor, which will automatically deploy any
- bundles in the auto-deploy directory as well as bundles specified in the felix.auto.install
- and felix.auto.start
+
Use org.apache.felix.main.AutoProcessor, which will automatically deploy any bundles in the auto-deploy directory as
+ well as bundles specified in the felix.auto.install and felix.auto.start
configuration properties during framework startup to automatically
install and/or start bundles; see the usage document for more
information bundle
auto-deploy.
-
Invoke waitForStop() to wait for the framework to stop to force the VM to exit;
- this is necessary because the framework never calls System.exit() and some
- libraries (e.g., Swing) create threads that will not allow the VM to exit.
+
Invoke waitForStop() to wait for the framework to stop to force the VM to exit; this is necessary because the framework
+ never calls System.exit() and some libraries (e.g., Swing) create threads that will not allow the VM to exit.
@@ -524,8 +463,7 @@
-
Custom
- Framework Launcher
+
Custom Framework Launcher
This section creates a bare-bones launcher to demonstrate the
minimum requirements for creating an interactive launcher for the Felix
@@ -559,8 +497,8 @@
After executing this command, a "felix-cache/" directory is created that contains
- the cached bundles, which were installed from the bundle/ directory.
+
After executing this command, a "felix-cache/" directory is created that contains the cached bundles, which were installed
+ from the bundle/ directory.
-
Embedding
- the Felix Framework
+
Embedding the Felix Framework
Embedding the Felix framework into a host application is a simple
way to provide a sophisticated extensibility mechanism (i.e., a plugin
@@ -747,12 +676,10 @@
-
Host/Felix
- Interaction
+
Host/Felix Interaction
-
In the section on launching the framework
- above, the Felix class accepts a configuration property called felix.systembundle.activators,
+
In the section on launching the framework above, the
+ Felix class accepts a configuration property called felix.systembundle.activators,
which is a list of bundle activator instances. These bundle activator
instances provide a convenient way for host applications to interact
with the Felix framework.
Each activator instance passed into the constructor effectively becomes part of the system
- bundle. This means that the start()/stop() methods of each activator
- instance in the list gets invoked when the system bundle's activator start()/stop()
- methods gets invoked, respectively. Each activator instance will be given the system
- bundle's BundleContext object so that they can interact with the framework.
- Consider following snippet of a bundle activator:
+
Each activator instance passed into the constructor effectively becomes part of the system bundle. This means that the
+ start()/stop() methods of each activator instance in the list gets invoked when the system bundle's activator start()/stop()
+ methods gets invoked, respectively. Each activator instance will be given the system bundle's BundleContext object so that
+ they can interact with the framework. Consider following snippet of a bundle activator:
-
public class HostActivator implements BundleActivator
+
public class HostActivator implements BundleActivator
{
private BundleContext m_context = null;
@@ -825,8 +747,7 @@
Providing services from the host application to bundles inside the
embedded Felix framework instance follows the basic approach laid out
@@ -895,8 +815,8 @@
This package is simply part of the host application, which is potentially packaged into a JAR
- file and started with the "java -jar"
+
This package is simply part of the host application, which is potentially packaged into a JAR file and started with the "java
+ -jar"
command. Now consider the following host application bundle activator,
which will be used to register/unregister the property lookup service
when the embedded framework instance starts/stops:
Using services provided by bundles follows the same general approach
of using a host application bundle activator. The main complication for
@@ -1072,8 +981,7 @@
This package is simply part of the host application, which is potentially packaged into a JAR
- file and started with the "java -jar"
+
This package is simply part of the host application, which is potentially packaged into a JAR file and started with the "java
+ -jar"
command. Now consider the previously introduced host application bundle
activator below, which simply provides access to the system bundle
context:
It possible for the host application to use services provided by
bundles without having access to the service interface classes and thus
@@ -1252,12 +1153,10 @@
-
Other Approaches
-
+
Other Approaches
-
The Transloader
- project is another attempt at dealing with issues of classes loaded from different class
- loaders and may be of interest.
+
The Transloader project is another attempt
+ at dealing with issues of classes loaded from different class loaders and may be of interest.
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/apache.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/apache.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/apache.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/apache.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button.html b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button.html
similarity index 55%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button.html
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button.html
index 8d2e211b..320aeb10 100644
--- a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button.html
+++ b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button.html
@@ -3,9 +3,8 @@
-
+
\ No newline at end of file
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2008-usa-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2008-usa-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2008-usa-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2008-usa-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2009-europe-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2009-europe-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2009-europe-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2009-europe-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2009-usa-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2009-usa-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2009-usa-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2009-usa-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2010-na-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2010-na-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2010-na-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/button_data/2010-na-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/forbidden.gif b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/forbidden.gif
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/forbidden.gif
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/forbidden.gif
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/linkext7.gif b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/linkext7.gif
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/linkext7.gif
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/linkext7.gif
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/logo.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/logo.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/logo.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/logo.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/mail_small.gif b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/mail_small.gif
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/mail_small.gif
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/mail_small.gif
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/site.css b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/site.css
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-launching-and-embedding_files/site.css
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-launching-and-embedding_files/site.css
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation.html b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation.html
similarity index 66%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation.html
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation.html
index 3d5c5a31..451b8eaa 100644
--- a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation.html
+++ b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation.html
@@ -1,12 +1,10 @@
-
+
Apache Felix - Apache Felix Framework Usage Documentation
-
+
@@ -14,82 +12,64 @@
Go to the downloads page and download the latest Felix framework
- distribution.
+
Go to the downloads page and download the latest Felix
+ framework distribution.
-
Starting the
- Framework
+
Starting the Framework
Start the framework from the installation directory by typing:
@@ -100,8 +80,7 @@
St
-
The framework launcher starts the framework and installs and starts all bundles contained in
- the bundle
+
The framework launcher starts the framework and installs and starts all bundles contained in the bundle
directory of the current directory. By default, the bundle directory
contains shell-related bundles providing a textual user interface to
interact with the framework. Bundles installed into the framework are
@@ -129,20 +108,18 @@
St
-
+
Useful Information Previous
versions of the framework prompted for a profile name when executed.
The profile name was used to create a directory inside .felix/
in the user home directory. This approach allowed users to have
different sets of bundles for different purposes, e.g., testing,
production, etc. If this behavior is still desired, it is very easy to
- mimic. Modify conf/config.properties to include "felix.cache.rootdir=${user.home}/.felix".
- Now, if you start Felix with something like "java -jar bin/felix.jar
- foo", it will use "${user.home}/.felix/foo/" as the bundle
- cache directory, where "${user.home}" is automatically substituted with
- the appropriate system property by the launcher.
+ mimic. Modify conf/config.properties to include "felix.cache.rootdir=${user.home}/.felix". Now, if you
+ start Felix with something like "java -jar bin/felix.jar foo", it will use "${user.home}/.felix/foo/"
+ as the bundle cache directory, where "${user.home}" is automatically substituted with the appropriate system
+ property by the launcher.
@@ -153,10 +130,9 @@
St
Framework Shell
-
The main way to interact with the framework is via the supplied Apache Felix Gogo shell.
- After starting the framework, type help into the shell to see the list of the
- available commands and help <command-name> to get help for a specific
- command.
+
The main way to interact with the framework is via the supplied Apache Felix Gogo shell. After starting the framework, type
+ help into the shell to see the list of the available commands and help <command-name> to get help for a
+ specific command.
@@ -166,14 +142,11 @@
Framewor
-
-
Useful Information In Gogo, command names are made up of two parts:
- <scope>:<name>. This is similar to a fully qualified class
- name in Java and is used to avoid naming collisions. If the
- <name> portion of the command is unique, then you only need to
- type it. If not, then you must either type the full <scope>:<name>
+
+
Useful Information In Gogo, command names are made up of two parts: <scope>:<name>. This
+ is similar to a fully qualified class name in Java and is used to avoid naming collisions. If the <name>
+ portion of the command is unique, then you only need to type it. If not, then you must either type the full <scope>:<name>
or arrange the scope search path accordingly.
@@ -181,19 +154,16 @@
Framewor
-
To install bundles, use the felix:install command, which is described in more detail
- in the next sub-section. To
- list installed bundles, use the felix:lb command. To stop the framework type stop
- 0
+
To install bundles, use the felix:install command, which is described in more detail in the next sub-section. To list installed bundles, use the felix:lb
+ command. To stop the framework type stop 0
to stop the System Bundle; any installed bundles will automatically be
reloaded (and potentially restarted) the next time you launch with the
associated cache.
-
Installing Bundles
-
+
Installing Bundles
A bundle is the OSGi term for a component for the OSGi framework. A
bundle is simply a JAR file containing a manifest and some combination
@@ -209,16 +179,15 @@
Insta
Command (basic set of commands), and Bundle Repository (a bundle
repository service). In addition to these bundles, the bundle
repository provides access to other bundles for easy installation. The
- bundle repository service provides a set of shell commands in the obr:* scope;
- refer to the Apache Felix OSGi Bundle
- Repository for more information.
+ bundle repository service provides a set of shell commands in the obr:* scope; refer to the Apache
+ Felix OSGi Bundle Repository for more information.
Before installing any bundles, it is important to understand how
bundles are manually deployed into the framework. Bundles are deployed
in two stages; first they are installed, then they are started. To
- install a bundle use the felix:install shell command followed by a bundle URL. For
- example, to install a bundle.jar bundle you type:
+ install a bundle use the felix:install shell command followed by a bundle URL. For example, to install a
+ bundle.jar bundle you type:
@@ -227,8 +196,8 @@
Insta
-
Once a bundle is installed, it can then be started by using the felix:start command
- and the bundle identifier of the desired bundle. The felix:lb
+
Once a bundle is installed, it can then be started by using the felix:start command and the bundle identifier of the desired
+ bundle. The felix:lb
command is used to list installed bundles and to obtain the bundle's
identifier. The following Felix shell session illustrates how to start
the bundle.jar bundle:
@@ -252,17 +221,14 @@
Insta
-
The felix:stop command is used to stop a bundle and the felix:uninstall
- command is used to remove a bundle from the bundle cache. As an alternative to using the
- felix:install and felix:start commands explicitly, it is also possible to
- install and start a bundle in one step by using the felix:start command with a
- bundle URL.
+
The felix:stop command is used to stop a bundle and the felix:uninstall command is used to remove a bundle from the
+ bundle cache. As an alternative to using the felix:install and felix:start commands explicitly, it is also
+ possible to install and start a bundle in one step by using the felix:start command with a bundle URL.
Bundles can be updated using the felix:update command. The
update command allows you to specify an URL from which to retrieve the
updated bundle, but if one is not specified it will try to update the
- bundle from the bundle's Bundle-UpdateLocation manifest attribute, if present, or
- the bundle's original location URL.
+ bundle from the bundle's Bundle-UpdateLocation manifest attribute, if present, or the bundle's original location URL.
@@ -272,16 +238,14 @@
Insta
-
+
Useful Information When you use felix:update or felix:uninstall,
the changes appear to take effect immediately, but in reality the
changes are only partially enacted. If a bundle is updated or
uninstalled and it was exporting packages, these packages are not
- removed until the framework is refreshed using the PackageAdmin
- service. The Felix shell offers a convenient refresh command for this
- purpose. This is the correct behavior as defined by the OSGi specification.
+ removed until the framework is refreshed using the PackageAdmin service. The Felix shell offers a convenient
+ refresh command for this purpose. This is the correct behavior as defined by the OSGi specification.
@@ -292,8 +256,8 @@
Insta
-
Web
- Proxy Issues when Installing Bundles
+
Web Proxy Issues when Installing Bundles
+
If you use a proxy for Web access, then you may run into difficulty
using the Gogo shell to install bundles from remote URLs. To remedy
@@ -311,23 +275,20 @@
These system properties can be set directly on the command line when starting the JVM using the standard "-D<prop>=<value>"
+ syntax or you can put them in the lib/system.properties file of your Felix installation; see the next section on configuring Felix for more information.
-
Bundle Auto-Deploy
-
+
Bundle Auto-Deploy
To minimize the amount of configuration necessary to install bundles
when you launch the framework, the Felix launcher uses the concept of
an "auto-deploy" directory. The Felix launcher deploys all bundles in
the auto-deploy directory into the framework instance during startup.
- By default, the auto-deploy directory is "bundle" in the current directory, but it
- can be specified on the command line like this:
+ By default, the auto-deploy directory is "bundle" in the current directory, but it can be specified on the command line
+ like this:
@@ -344,18 +305,16 @@
Bundle
respectively:
-
felix.auto.deploy.dir - Specifies the auto-deploy directory from which bundles
- are automatically deploy at framework startup. The default is the bundle/
- directory of the current directory.
+
felix.auto.deploy.dir - Specifies the auto-deploy directory from which bundles are automatically deploy at framework
+ startup. The default is the bundle/ directory of the current directory.
felix.auto.deploy.action
- Specifies the auto-deploy actions to be performed on the bundle JAR
- files found in the auto-deploy directory. The possible actions are install,
- update, start, and uninstall.
+ files found in the auto-deploy directory. The possible actions are install, update, start, and uninstall.
If no actions are specified, then the auto-deploy directory is not
processed (i.e., it is disabled). There is no default value for this
- property, but the default config.properties file installed with the Felix
- framework distribution sets the value to: install, start
+ property, but the default config.properties file installed with the Felix framework distribution sets the value to:
+ install, start
@@ -363,15 +322,14 @@
Bundle
-
Configuring the
- Framework
+
Configuring the Framework
Both the Felix framework and the launcher use configuration
properties to alter their default behavior. The framework can only be
configured by passing properties into its constructor, but the launcher
provides a mechanism to configure the framework via a property file.
- The framework launcher reads configuration properties from conf/config.properties.
- This file uses standard Java property file syntax.
+ The framework launcher reads configuration properties from conf/config.properties. This file uses standard Java property
+ file syntax.
The launcher also supports setting system properties via the conf/system.properties
file. This file is purely for convenience when you need to repeatedly
@@ -380,9 +338,8 @@
-
It is possible to specify different locations for these property files using the felix.config.properties
- and felix.system.properties system properties when executing the framework. For
- example:
+
It is possible to specify different locations for these property files using the felix.config.properties and felix.system.properties
+ system properties when executing the framework. For example:
@@ -391,29 +348,25 @@
-
Configuration and system properties are accessible at run time via BundleContext.getProperty(),
- but configuration properties override system properties.
+
Configuration and system properties are accessible at run time via BundleContext.getProperty(), but configuration properties
+ override system properties.
The following configuration properties are for the launcher:
-
felix.auto.deploy.dir - Specifies the auto-deploy directory from which bundles
- are automatically deploy at framework startup. The default is the bundle/
- directory of the current directory.
+
felix.auto.deploy.dir - Specifies the auto-deploy directory from which bundles are automatically deploy at framework
+ startup. The default is the bundle/ directory of the current directory.
felix.auto.deploy.action
- Specifies a comma-delimited list of actions to be performed on bundle
- JAR files found in the auto-deploy directory. The possible actions are install,
- update, start, and uninstall. An undefined or blank value is
- equivalent to disabling auto-deploy processing.
+ JAR files found in the auto-deploy directory. The possible actions are install, update, start, and
+ uninstall. An undefined or blank value is equivalent to disabling auto-deploy processing.
-
felix.auto.install.<n> - Space-delimited list of bundle URLs to
- automatically install when Felix is started, where <n> is the start level
- into which the bundle will be installed (e.g., felix.auto.install.2).
+
felix.auto.install.<n> - Space-delimited list of bundle URLs to automatically install when Felix is started,
+ where <n> is the start level into which the bundle will be installed (e.g., felix.auto.install.2).
-
felix.auto.start.<n> - Space-delimited list of bundle URLs to
- automatically install and start when Felix is started, where <n> is the
- start level into which the bundle will be installed (e.g., felix.auto.start.2).
+
felix.auto.start.<n> - Space-delimited list of bundle URLs to automatically install and start when Felix is
+ started, where <n> is the start level into which the bundle will be installed (e.g., felix.auto.start.2).
felix.shutdown.hook
- Specifies whether the launcher should install a shutdown hook to
@@ -422,28 +375,25 @@
-
The following configuration properties are for the framework (properties starting with "felix"
- are specific to Felix, while those starting with "org.osgi" are standard OSGi
- properties):
+
The following configuration properties are for the framework (properties starting with "felix" are specific to Felix, while
+ those starting with "org.osgi" are standard OSGi properties):
-
org.osgi.framework.storage - Sets the directory to use as the bundle cache; by
- default bundle cache directory is felix-cache
+
org.osgi.framework.storage - Sets the directory to use as the bundle cache; by default bundle cache directory is felix-cache
in the current working directory. The value should be a valid directory
name. The directory name can be either absolute or relative. Relative
directory names are relative to the current working directory. The
specified directory will be created if it does not exist.
-
felix.cache.rootdir - Sets the root directory used to calculate the bundle
- cache directory for relative directory names. If org.osgi.framework.storage
+
felix.cache.rootdir - Sets the root directory used to calculate the bundle cache directory for relative directory
+ names. If org.osgi.framework.storage
is set to a relative name, by default it is relative to the current
working directory. If this property is set, then it will be calculated
as being relative to the specified root directory.
-
org.osgi.framework.storage.clean - Determines whether the bundle cache is
- flushed. The value can either be "none" or "onFirstInit", where "none"
- does not flush the bundle cache and "onFirstInit" flushes the bundle cache when
- the framework instance is first initialized. The default value is "none".
+
org.osgi.framework.storage.clean - Determines whether the bundle cache is flushed. The value can either be
+ "none" or "onFirstInit", where "none" does not flush the bundle cache and "onFirstInit"
+ flushes the bundle cache when the framework instance is first initialized. The default value is "none".
felix.cache.bufsize
- Sets the buffer size to be used by the cache; the default value is
@@ -459,9 +409,8 @@
org.osgi.framework.system.packages.extra
- Specifies a comma-delimited list of packages that should be exported
via the System Bundle from the framework class loader in addition to
- the packages in org.osgi.framework.system.packages. The default value is empty.
- If a value is specified, it is appended to the list of default or specified packages in
- org.osgi.framework.system.packages.
+ the packages in org.osgi.framework.system.packages. The default value is empty. If a value is specified, it is appended
+ to the list of default or specified packages in org.osgi.framework.system.packages.
org.osgi.framework.bootdelegation
- Specifies a comma-delimited list of packages that should be made
@@ -469,11 +418,9 @@
-
org.osgi.framework.bundle.parent - Specifies which class loader is used for
- boot delegation. Possible values are: boot for the boot class loader,
- app for the application class loader, ext for the extension class
- loader, and framework for the framework's class loader. The default is
- boot.
+
org.osgi.framework.bundle.parent - Specifies which class loader is used for boot delegation. Possible values are: boot
+ for the boot class loader, app for the application class loader, ext for the extension class loader, and framework
+ for the framework's class loader. The default is boot.
felix.bootdelegation.implicit
- Specifies whether the framework should try to guess when to
@@ -499,15 +446,12 @@
-
org.osgi.framework.startlevel.beginning - The initial start level of the
- framework once it starts execution; the default value is 1.
+
org.osgi.framework.startlevel.beginning - The initial start level of the framework once it starts execution; the
+ default value is 1.
-
felix.startlevel.bundle - The default start level for newly installed bundles;
- the default value is 1.
-
-
felix.service.urlhandlers - Flag to indicate whether to activate the URL
- Handlers service for the framework instance; the default value is "true".
- Activating the URL Handlers service will result in the URL.setURLStreamHandlerFactory()
+
felix.startlevel.bundle - The default start level for newly installed bundles; the default value is 1.
+
felix.service.urlhandlers - Flag to indicate whether to activate the URL Handlers service for the framework instance;
+ the default value is "true". Activating the URL Handlers service will result in the URL.setURLStreamHandlerFactory()
and URLConnection.setContentHandlerFactory() being called.
@@ -517,53 +461,44 @@
-
Migrating
- from Earlier Versions
+
Migrating from Earlier Versions
-
Apache Felix Framework 2.0.0 introduced some configuration property changes. This
- section describes the differences from older versions of the framework.
+
Apache Felix Framework 2.0.0 introduced some configuration property changes. This section describes the differences from
+ older versions of the framework.
Removed
-
felix.embedded.execution - No longer needed, since the framework now
- never calls System.exit(); the creator of the framework is now always
- responsible for exiting the VM.
-
-
felix.strict.osgi - No longer needed, since all non-specification
- features have been removed.
+
felix.embedded.execution - No longer needed, since the framework now never calls System.exit(); the
+ creator of the framework is now always responsible for exiting the VM.
-
felix.cache.dir - No longer needed, since Felix no longer uses bundle
- cache profiles for saving sets of bundles.
+
felix.strict.osgi - No longer needed, since all non-specification features have been removed.
+
felix.cache.dir - No longer needed, since Felix no longer uses bundle cache profiles for saving sets of
+ bundles.
-
felix.cache.profile - No longer needed, since the framework no longer
- uses bundle cache profiles for saving sets of bundles.
-
-
felix.fragment.validation - No longer needed, since the framework
- supports fragments.
+
felix.cache.profile - No longer needed, since the framework no longer uses bundle cache profiles for saving
+ sets of bundles.
+
felix.fragment.validation - No longer needed, since the framework supports fragments.
Renamed
-
felix.cache.profiledir - The equivalent of this property is now named
- org.osgi.framework.storage.
-
-
felix.startlevel.framework - The equivalent of this property is now
- named org.osgi.framework.startlevel.beginning.
+
felix.cache.profiledir - The equivalent of this property is now named org.osgi.framework.storage.
+
felix.startlevel.framework - The equivalent of this property is now named org.osgi.framework.startlevel.beginning.
Introduced
-
org.osgi.framework.system.packages.extra - New property, as described
- above, added to align with standard framework API.
+
org.osgi.framework.system.packages.extra - New property, as described above, added to align with standard
+ framework API.
-
org.osgi.framework.storage.clean - New property, as described above,
- added to align with standard framework API.
+
org.osgi.framework.storage.clean - New property, as described above, added to align with standard framework
+ API.
-
felix.cache.rootdir - Introduced as a result of removing bundle
- profiles to help resolve relative bundle cache directories.
+
felix.cache.rootdir - Introduced as a result of removing bundle profiles to help resolve relative bundle cache
+ directories.
@@ -576,12 +511,10 @@
-
System
- Property Substitution
+
System Property Substitution
-
It is possible to use system properties to specify the values of properties in the conf/config.properties
- file. This is achieved through system property substitution, which is instigated by using
- ${<property>} syntax, where <property>
+
It is possible to use system properties to specify the values of properties in the conf/config.properties file. This is
+ achieved through system property substitution, which is instigated by using ${<property>} syntax, where <property>
is the name of a system property to substitute. When the properties
file is read, any such property values are substituted as appropriate.
It is possible to have nested system property substitution, in which
@@ -590,8 +523,7 @@
-
Configuring Bundles
-
+
Configuring Bundles
Some bundles use properties to configure certain aspects of their
behavior. It is a good idea, when implementing bundles, to parameterize
@@ -599,22 +531,20 @@
Conf
configuration options for specific bundles, refer to the documentation
that accompanies them.
-
Bundle properties may also be defined in the conf/config.properties property file.
- Any property placed in this file will be accessible via BundleContext.getProperty()
+
Bundle properties may also be defined in the conf/config.properties property file. Any property placed in this file will be
+ accessible via BundleContext.getProperty()
at run time. The property file uses the standard Java property file
syntax (i.e., attribute-value pairs). For information on changing the
- default location of this file, refer to the section on configuring
+ default location of this file, refer to the section on configuring
Felix.
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/apache.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/apache.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/apache.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/apache.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button.html b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button.html
similarity index 55%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button.html
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button.html
index 8d2e211b..320aeb10 100644
--- a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button.html
+++ b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button.html
@@ -3,9 +3,8 @@
-
+
\ No newline at end of file
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2008-usa-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2008-usa-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2008-usa-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2008-usa-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2009-europe-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2009-europe-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2009-europe-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2009-europe-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2009-usa-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2009-usa-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2009-usa-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2009-usa-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2010-na-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2010-na-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2010-na-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/button_data/2010-na-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/information.gif b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/information.gif
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/information.gif
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/information.gif
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/linkext7.gif b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/linkext7.gif
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/linkext7.gif
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/linkext7.gif
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/logo.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/logo.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/logo.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/logo.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/mail_small.gif b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/mail_small.gif
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/mail_small.gif
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/mail_small.gif
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/site.css b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/site.css
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-framework-usage-documentation_files/site.css
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-framework-usage-documentation_files/site.css
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/apache.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/apache.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/apache.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/apache.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/button.html b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/button.html
similarity index 55%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/button.html
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/button.html
index 8d2e211b..320aeb10 100644
--- a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/button.html
+++ b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/button.html
@@ -3,9 +3,8 @@
-
+
\ No newline at end of file
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/button_data/2010-na-125x125.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/button_data/2010-na-125x125.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/button_data/2010-na-125x125.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/button_data/2010-na-125x125.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/logo.png b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/logo.png
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/logo.png
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/logo.png
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/site.css b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/site.css
similarity index 100%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo-Dateien/site.css
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo-Dateien/site.css
diff --git a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo.html b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo.html
similarity index 71%
rename from demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo.html
rename to demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo.html
index 0aea1b7f..01e665f1 100644
--- a/demo/framework/felix/felix-4.4.1-doc/doc/apache-felix-gogo.html
+++ b/demo/framework/felix/felix-4.6.0-doc/doc/apache-felix-gogo.html
@@ -1,5 +1,4 @@
-
+
@@ -10,33 +9,23 @@
Apache Felix Gogo is a subproject of Apache Felix implementing the
OSGi RFC 147, which describes a standard shell for OSGi-based
- environments. See RFC 147 Overview for more information.
To simplify deploying and using available bundles with Felix.
-
To encourage independent bundle development so that communities of interest can grow.
-
+
To encourage independent bundle development so that communities of interest can grow.
@@ -101,8 +86,8 @@
Motivation
Note: OBR provides access to the Felix' default bundle repository,
but you can also use it to deploy your own bundles by creating a bundle
- repository meta-data file for your local bundles; see the obr list-url, obr
- add-url, and obr remove-url commands for more details.
+ repository meta-data file for your local bundles; see the obr list-url, obr add-url, and obr remove-url
+ commands for more details.
@@ -120,30 +105,23 @@
Overview
OBR defines the following entities:
-
Repository Admin - a service to access a federation of repositories.
-
+
Repository Admin - a service to access a federation of repositories.
Repository - provides access to a set of resources.
-
Resource - a description of an artifact to be installed on a device.
-
+
Resource - a description of an artifact to be installed on a device.
Capability - a named set of properties.
Requirement - an assertion on a capability.
-
Resolver - an object to resolve resource dependencies and to deploy
- them.
-
+
Resolver - an object to resolve resource dependencies and to deploy them.
Repository file - XML file containing resource meta-data.
The following diagram illustrates the relationships among these entities:
-
+
-
The client has access to a federated set of repositories via the Repository Admin service;
- such as depicted in this view:
+
The client has access to a federated set of repositories via the Repository Admin service; such as depicted in this view:
-
+
@@ -151,11 +129,9 @@
OBR Reposito
The OBR repository file is an XML-based representation of bundle
meta-data. The goal is provide a generic model for describing
- dependencies among resources; as such, the term resource is used instead of
- bundle in the OBR repository syntax; a detailed description of the OBR
- meta-data format is available in the OSGi
- RFC 112
+ dependencies among resources; as such, the term resource is used instead of bundle in the OBR
+ repository syntax; a detailed description of the OBR meta-data format is available in the OSGi RFC 112
document; this document is not completely in sync with the
implementation, but the concepts are still correct. The following XML
snippet depicts the overall structure of a repository file:
@@ -219,8 +195,7 @@
OBR Reposito
versions greater than '1.0.0'. Although this syntax looks rather
complicated with the '\&' and '\>=' syntax, it is simply the
standard OSGi LDAP query syntax in XML form (additionally, Peter Kriens
- has created a tool called bindex to generate this meta-data from a bundle's
- manifest).
+ has created a tool called bindex to generate this meta-data from a bundle's manifest).
With this generic dependency model, OBR is able to provide mappings
for the various OSGi bundle dependencies; e.g., import/export package,
@@ -249,8 +224,7 @@
OBR Service API<
-
publicinterface RepositoryAdmin
+
publicinterface RepositoryAdmin
{
public Resource[] discoverResources(String filterExpr);
public Resolver resolver();
@@ -258,8 +232,7 @@
OBR Service API<
throws Exception;
publicboolean removeRepository(URL repository);
public Repository[] listRepositories();
- public Resource getResource(String respositoryId);
+ public Resource getResource(String respositoryId);
}
@@ -270,8 +243,7 @@
OBR Service API<
-
publicinterface Resolver
+
publicinterface Resolver
{
public void add(Resource resource);
public Requirement[] getUnsatisfiedRequirements();
@@ -336,10 +308,9 @@
OBR Service API<
In the general case, OBR user's will not use the OBR API directly,
but will use its functionality indirectly from another tool or user
interface. For example, interactive access to OBR is available via a
- command for Felix' shell service. The OBR shell command is
- discussed in the next section.
+ command for Felix' shell service. The OBR shell command is discussed in the next section.
+
@@ -453,8 +424,7 @@
obr info
-
The above example retrieves the meta-data for version "1.0.0" of the bundle named "Bundle
- Repository".
+
The above example retrieves the meta-data for version "1.0.0" of the bundle named "Bundle Repository".
@@ -510,8 +480,7 @@
obr start
-
The above example installs and starts the "1.0.0" version of the bundle named "Bundle
- Repository" and its dependencies.
+
The above example installs and starts the "1.0.0" version of the bundle named "Bundle Repository" and its dependencies.
@@ -594,18 +563,15 @@
Using OBR w
-
Bundle Source Packaging
-
+
Bundle Source Packaging
Coming soon...
-
Note on OSGi R3 Bundles
-
+
Note on OSGi R3 Bundles
-
In contrast to OSGi R4 the previous specifications, most notably R3, allowed bundles without
- the Bundle-SymbolicName
+
In contrast to OSGi R4 the previous specifications, most notably R3, allowed bundles without the Bundle-SymbolicName
header. The Felix OSGi Bundle Repository implementation heavily relies
on the symbolic name being defined in bundles. As a consequence bundles
without a symbolic name are not fully supported by the Bundle
@@ -614,8 +580,8 @@
Note on OS
Bundles installed in the framework are used by the Bundle
Repository implementation to resolve dependencies regardless of whether
- they have a Bundle-SymbolicName header or not. Resolution of dependencies
- against the installed bundles takes place based on the Export-Package headers.
+ they have a Bundle-SymbolicName header or not. Resolution of dependencies against the installed bundles takes place
+ based on the Export-Package headers.
Bundles installed in the framework without a Bundle-SymbolicName
header cannot be updated by the Bundle Repository implementation
@@ -629,10 +595,8 @@