org.osgi.framework.system.packages.extra
In several places, http://felix.apache.org/site/apache-felix-framework-launching-and-embedding.html says: This is achieved using the org.osgi.framework.system.packages.extra configuration property previously presented. It does not seem to me to be previously presented. Is it on some other page? I'm trying to work out in my head how to set up an embedded situation that has the classpath issue discussed here. I have a family of bundles that can be asked to do some work. I have to push work in and get answers out from code outside. Now, I could throw my hands in the air and, essentially, put a web service in there, having (e.g.) JSON flow through. If I want actual Java objects to flow, I'm understanding the situation to be that I need: - a Non-bundle jar file that defines the interface and data that flow in and out of the container - to build the bundles to see themselves as importing this - to make it available at real runtime as system packages - to learn how to make the pax-exam unit tests for these bundles to get this code as system package instead of as imported bundles. Does this make sense? - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
Re: org.osgi.framework.system.packages.extra
On 11/17/14 10:27 , Benson Margulies wrote: In several places, http://felix.apache.org/site/apache-felix-framework-launching-and-embedding.html says: This is achieved using the org.osgi.framework.system.packages.extra configuration property previously presented. It does not seem to me to be previously presented. Is it on some other page? Here: http://felix.apache.org/documentation/subprojects/apache-felix-framework/apache-felix-framework-configuration-properties.html And in the OSGi specification. I'm trying to work out in my head how to set up an embedded situation that has the classpath issue discussed here. I have a family of bundles that can be asked to do some work. I have to push work in and get answers out from code outside. Now, I could throw my hands in the air and, essentially, put a web service in there, having (e.g.) JSON flow through. If I want actual Java objects to flow, I'm understanding the situation to be that I need: - a Non-bundle jar file that defines the interface and data that flow in and out of the container - to build the bundles to see themselves as importing this - to make it available at real runtime as system packages - to learn how to make the pax-exam unit tests for these bundles to get this code as system package instead of as imported bundles. Does this make sense? Sounds like it. - richard - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
org.osgi.framework version range chosen by plugin
the maven-bundle-plugin decided to put the following into the manifest, even though I'm using a much newer version of OSGi. Should I just add an instruction to set a version I like better, or is there something more subtle I've missed that would clue it in? org.osgi.framework;version=[1.4,2) - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
Embedding Felix and not finding org.osgi.framework
I am following the general line of breadcrumbs from: http://felix.apache.org/site/apache-felix-framework-launching-and-embedding.html and using felix 4.0.3. One of my bundles has an activator, so the bundle plugin set up an Import-Package for org.osgi.framework. I tried adding that to FRAMEWORK_SYSTEMPACKAGES_EXTRA, but that did not help. Help? ERROR: Bundle com.basistech.osgi.rosette-osgi-test-component [6] Error starting file:/Users/benson/x/rosette-osgi/container/target/bundles/rosette-osgi-test-component-0.0.1-SNAPSHOT.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.basistech.osgi.rosette-osgi-test-component [6]: Unable to resolve 6.0: missing requirement [6.0] osgi.wiring.package; ((osgi.wiring.package=org.osgi.framework)(version=1.4.0)(!(version=2.0.0 org.osgi.framework.BundleException: Unresolved constraint in bundle com.basistech.osgi.rosette-osgi-test-component [6]: Unable to resolve 6.0: missing requirement [6.0] osgi.wiring.package; ((osgi.wiring.package=org.osgi.framework)(version=1.4.0)(!(version=2.0.0))) - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
Re: Embedding Felix and not finding org.osgi.framework
Please ignore the below. On Mon, Nov 17, 2014 at 9:22 PM, Benson Margulies ben...@basistech.com wrote: I am following the general line of breadcrumbs from: http://felix.apache.org/site/apache-felix-framework-launching-and-embedding.html and using felix 4.0.3. One of my bundles has an activator, so the bundle plugin set up an Import-Package for org.osgi.framework. I tried adding that to FRAMEWORK_SYSTEMPACKAGES_EXTRA, but that did not help. Help? ERROR: Bundle com.basistech.osgi.rosette-osgi-test-component [6] Error starting file:/Users/benson/x/rosette-osgi/container/target/bundles/rosette-osgi-test-component-0.0.1-SNAPSHOT.jar (org.osgi.framework.BundleException: Unresolved constraint in bundle com.basistech.osgi.rosette-osgi-test-component [6]: Unable to resolve 6.0: missing requirement [6.0] osgi.wiring.package; ((osgi.wiring.package=org.osgi.framework)(version=1.4.0)(!(version=2.0.0 org.osgi.framework.BundleException: Unresolved constraint in bundle com.basistech.osgi.rosette-osgi-test-component [6]: Unable to resolve 6.0: missing requirement [6.0] osgi.wiring.package; ((osgi.wiring.package=org.osgi.framework)(version=1.4.0)(!(version=2.0.0))) - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
Re: org.osgi.framework version range chosen by plugin
Hi Am 18.11.2014 um 03:04 schrieb Benson Margulies ben...@basistech.com: the maven-bundle-plugin decided to put the following into the manifest, even though I'm using a much newer version of OSGi. Should I just add an instruction to set a version I like better, or is there something more subtle I've missed that would clue it in? org.osgi.framework;version=[1.4,2)“ If you have an explicit OSGi Core dependency in your Maven project but the bundle plugin still uses a different version, it may be that through transitive dependencies (I generally switch this off by using scope=provided in bundles) Maven pulls a different OSGi core library version into the class path in front of your explicit declaration. Regards Felix - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
