August 2009 - jboss-osgi-dev - Jboss List Archives

[JBoss OSGi Development] - Package cannot have two exporters

by thomas.diesler＠jboss.com

Still working on the SimpleLogServiceTestCase When I add the PackageRequirement regardless of whether it is also part of the exports I get | 2009-08-24 23:22:47,038 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController:1141] Error resolving dependencies for ClassLoader: name=vfszip:/home/tdiesler/svn/jboss-osgi/trunk/reactor/runtime/microcontainer/target/test-libs/bundles/org.apache.felix.log.jar/ state=Describe mode=Manual requiredState=Installed | java.lang.IllegalStateException: VFSDeploymentClassLoaderPolicyModule org.apache.felix.log:1.1.0.SNAPSHOT cannot be added because it is exports package org.osgi.service.log which conflicts with VFSDeploymentClassLoaderPolicyModule osgi.cmpn:4.2.0.200907101024 | at org.jboss.classloading.spi.dependency.ClassLoadingSpace.join(ClassLoadingSpace.java:223) | at org.jboss.classloading.spi.dependency.ClassLoadingSpace.joinAndResolve(ClassLoadingSpace.java:120) | at org.jboss.classloading.spi.dependency.ClassLoadingSpace.joinAndResolve(ClassLoadingSpace.java:169) | at org.jboss.classloading.spi.dependency.ClassLoadingSpace.resolve(ClassLoadingSpace.java:326) | at org.jboss.classloading.spi.dependency.Module.resolveModule(Module.java:909) | at org.jboss.classloading.spi.dependency.RequirementDependencyItem.resolve(RequirementDependencyItem.java:91) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251308#4251308 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251308

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Development] - HOWTO chage the behaviour of the CL policy

by thomas.diesler＠jboss.com

Currently bundle class loading uses VFSClassLoaderPolicy, which seems to load the class from the private packages first rather than considering imports. This is related to https://jira.jboss.org/jira/browse/JBOSGI-135 How can I configure/swap the policy being used? More specifically I see in BaseClassLoaderDomain that | Loader findLoaderInImports(ClassLoaderInformation info, String name, boolean trace) | { | List<? extends DelegateLoader> delegates = info.getDelegates(); | if (delegates == null || delegates.isEmpty()) | { | if (trace) | log.trace(this + " not loading " + name + " from imports it has no delegates"); | return null; | } | does not have delegates for imports. At the end of the day I want org.apache.felix.log.jar to load [org.osgi.service.log.LogService] from org.osgi.compendium.jar You can reproduce the issue by running | [tdiesler@tdvaio trunk]$ mvn -Dtest=SimpleLogServiceTestCase test | | Running org.jboss.test.osgi.integration.simple.SimpleLogServiceTestCase | FIXME [JBOSGI-135] Cannot handle package beeing imported and exported by the same bundle | Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.355 sec | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251255#4251255 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251255

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Development] - Re: Bundle.start() does not transition to ACTIVE

by thomas.diesler＠jboss.com

Yes, I agree. The OSGiBundleClassLoadingDeployer currently contains this TODO [core] // [TODO] Import package requirements should probably resolve against export capabilities boolean isExportPackage = exportedNames.contains(packageName); [/core] The configured system packages are now set as a filter on the parent domain. Please see OSGiClassLoaderSystem for details. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251227#4251227 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251227

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Development] - Re: Bundle.start() does not transition to ACTIVE

by alesj

"thomas.diesler(a)jboss.com" wrote : | I fixed by only adding PackageRequirement for packages that are not system and not exported. | This looks like a hack, at least the "not exported" part. Where it might make sense for system stuff, which doesn't go over MC's CLDescribe deployer, hence not describing its exporting packages --> making sense to exclude them. But I don't see why this would be useful for imports? The imports are declarative info, so why should it be excluded if it's also found in exports? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251225#4251225 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251225

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Development] - FrameworkUtil and Filter implementations

by thomas.diesler＠jboss.com

There is org.jboss.osgi.plugins.framework.FrameworkUtil org.jboss.osgi.plugins.filter.FilterImpl which seem to duplicate http://www.osgi.org/javadoc/r4v41/org/osgi/framework/FrameworkUtil.html Could you please give a little more background on why we needs this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251016#4251016 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251016

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Development] - Re: Bundle.start() does not transition to ACTIVE

by thomas.diesler＠jboss.com

I now throw a BundleException on unresolved RequirementDependencyItems The problem of org.osgi.framework.BundleException: Cannot start bundle Bundle{simple-bundle:0.0.0}, because of unresolved dependencies PackageRequirement{org.osgi.framework [0.0.0,?)}, PackageRequirement{org.jboss.test.osgi.simple.bundle [0.0.0,?)}] I fixed by only adding PackageRequirement for packages that are not system and not exported. Please see OSGiBundleClassLoadingDeployer for details This probably needs some more work, because a simple package name match between the import and the export is not sufficient View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251007#4251007 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251007

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Development] - Re: Bundle.start() does not transition to ACTIVE

by thomas.diesler＠jboss.com

I added some cause analysis and it seems that both PackageRequirements should either not be there or get resolved. org.osgi.framework: from declared system packages org.jboss.test.osgi.simple.bundle: from the bundle itself | testBundleInstallLauchAPI(org.jboss.test.osgi.simple.SimpleBundleTestCase) Time elapsed: 4.215 sec <<< ERROR! | org.osgi.framework.BundleException: Cannot start bundle Bundle{simple-bundle:0.0.0}, because of unresolved dependencies | [PackageRequirement{org.osgi.framework [0.0.0,?)}, PackageRequirement{org.jboss.test.osgi.simple.bundle [0.0.0,?)}] | at org.jboss.osgi.plugins.facade.bundle.OSGiBundleManager.start(OSGiBundleManager.java:494) | at org.jboss.osgi.plugins.facade.bundle.OSGiBundleState.start(OSGiBundleState.java:736) | at org.jboss.osgi.plugins.facade.bundle.OSGiBundleState.start(OSGiBundleState.java:724) | at org.jboss.osgi.plugins.facade.bundle.OSGiBundleWrapper.start(OSGiBundleWrapper.java:176) | at org.jboss.test.osgi.simple.SimpleBundleTestCase.testBundleInstallLauchAPI(SimpleBundleTestCase.java:62) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251006#4251006 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251006

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Dev] - Re: Bundle.start() does not transition to ACTIVE

by thomas.diesler＠jboss.com

I'll have a look https://jira.jboss.org/jira/browse/JBOSGI-130 https://jira.jboss.org/jira/browse/JBOSGI-131 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251000#4251000 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4251000

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Dev] - MCFacade Hudson job

by thomas.diesler＠jboss.com

http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-mc-facade/ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250892#4250892 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250892

14 years, 8 months

1
0
0 / 0

[JBoss OSGi Dev] - Bundle.start() does not transition to ACTIVE

by thomas.diesler＠jboss.com

It seems that bundle.start() does not transition the bundle's state. | [tdiesler@tdvaio osgi-int]$ mvn -Dtest=SimpleBundleTestCase install | | Running org.jboss.test.osgi.simple.SimpleBundleTestCase | Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.793 sec <<< FAILURE! | | java.lang.AssertionError: Bundle state expected:<32> but was:<2> | at org.junit.Assert.fail(Assert.java:92) | at org.junit.Assert.failNotEquals(Assert.java:689) | at org.junit.Assert.assertEquals(Assert.java:127) | at org.junit.Assert.assertEquals(Assert.java:514) | at org.jboss.test.osgi.simple.SimpleBundleTestCase.testBundleInstall(SimpleBundleTestCase.java:78) | I see | /** | * Start a bundle | * | * @param bundleState the bundle state | * @throws BundleException the bundle exception | */ | public void start(OSGiBundleState bundleState) throws BundleException | { | try | { | // todo check actually changed state | deployerClient.change(bundleState.getDeploymentUnit().getName(), DeploymentStages.INSTALLED); | } | catch (DeploymentException e) | { | Throwable t = e.getCause(); | if (t instanceof BundleException) | throw (BundleException) t; | throw new BundleException("Error starting " + bundleState, e); | } | } | Could you please explain how this is supposed to work? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250889#4250889 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250889

14 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-dev August 2009