Initial support for DynamicImport-Package JBOSGI-143 - DynamicImport-Package Adrian says: There are three issues here: 1) The dynamic imports are not getting added to the ClassLoadingMetaData requirements (this is because of number 2) ... 
Service mix part deux (II.) Starting a new fresh thread, as the old one is pretty much tangled up with a bunch of useless tracking-impl info. * http://www.jboss.org/index.html?module=bb&op=viewtopic&t=160504 OK, I have cleaned up OSGi M... 
Initial support for Bundle-NativeCode Initial support for navtive code is provided by the OSGiBundleNativeCodeDeployer http://fisheye.jboss.org/browse/JBossOSGi/projects/runtime/framework/trunk/src/main/java/org/jboss/osgi/framework/deployers/OSGi... Initial support for Bundle.update() 4.4.9 Updating Bundles The Bundle interface defines two methods for updating a bundle: • update() – This method updates a bundl... Resolving a bundle in start() breaks ServiceMix Ales, could you please document comprehensively in javadoc how this ServiceMix stuff is supposed to work. This code required by the TCK breaks the ServiceMix tests // If ... BundleContext should not become reusable A BundleContext should not become reusable after bundle.stop() bundle.start() public void testStopedBundleContext() throws Exception { Bundle b... JBoss OSGi logging policy Logging in JBoss OSGi is done through multiple logging frameworks. There are bundles that use commons-logging, slf4j and of course jboss-logging. Ultimately all logging is routed to log4j. For surefire tests this is ... Good news on service mix I integrated framework/trunk in jboss-osgi. All example and functional tests pass in embedded mode. This means that the new OSGi Service implementation shows the expected results for all the use cases covered ... No explicit control over bundle.start() https://jira.jboss.org/jira/browse/JBOSGI-204 The MC Framework incorrectly uninstalls the bundle if there is a failure in bundle.start() The controller context reached its required stage DESCRIBED after bundle insta... Unexpected dependee state changes Bundle B depends on bundle X install(X) install(B) start(B) B == ACTIVE X == RESOLVED uninstall(X) B == ACTIVE The MC framework unexpectedly changes the state of B to RESOLVED https://jira.jboss.org/jira/br... Snapshot of resolver issues Folks, I have now removed the dependencies on the Resolver API and use PackageAdmin instead. Have a look at AbstractImportExportTest. There are currently three variations of this test case. * BasicResolver * RuleBas... Service integration with MC and vice versa. * Service --> MC "adrian@jboss.org" wrote: The service layer is not so well integrated with the MC. It does just enough to be "OSGi compliant" (of course that's not yet tested). So this is at the... Define non OSGi bundle handling by the Framework https://jira.jboss.org/jira/browse/JBOSGI-203 There have been changes going forth and back with respect to non-osgi deployment handling. The objectives and scope of functionality still need to be defined. I had to r... PROPERTY_AUTO_START Further to the resolver discussion; I've removed the use of PROPERTY_AUTO_START since this is already available in the deployment layer as DeploymentUnit.getRequiredStage() Any processing done in OSGi, should respect... 
Goals of OSGi integration Beyond the obvious goal of implementing the OSGi spec the other part to having the OSGi framework implemented on top of the MC/Deployers is so you can control other types of deployments using the Bundle/Service api. ... How does bundle resolution work Here is a short explanation of how bundle resolution (currently) works. The OSGiBundleClassLoadingDeployer creates the package capabilities/requirements that map to package exports/imports respectively. At runtime th... Handle potential bundle:// protocol with VFS WRT https://jira.jboss.org/jira/browse/JBOSGI-201 "alesj" wrote: We should be able to handle bundle:// protocol. e.g. bundle://<bundle_id>/<resource_path> "thomas" wrote: Could you perhaps give a us... Don't leak implementation details The method getBundleState() on the OSGiBundleWrapper is package protected so that ordinary users can't get to the implementation details and do dangerous things. Making this method public defeats the point of having ... Tests no longer work in eclipse After the lastest round of refactoring the tests now don't run in eclipse. And this is not just the usual log4j mess again. The root cause is an eclipse/maven problem with the classpath, i.e. it is now looking for /... ResolverPlugin is just Wrong RESOLVER PLUGIN IS INOPERABLE WITH OTHER CLASSLOADING Thomas, can you stop working on the ResolverPlugin, it is just plain wrong. One of the major points of developing the MC based OSGi facade is that OSGi bundles s...
Log in to follow, share, and participate in this community.