October 2012 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-611) Unresolvable capability silently prevents entire set to resolve/start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-611?page=com.atlassian.jira.plugin... ] Thomas Diesler moved AS7-5812 to JBOSGI-611: -------------------------------------------- Project: JBoss OSGi (was: Application Server 7) Key: JBOSGI-611 (was: AS7-5812) Workflow: jira (was: GIT Pull Request workflow ) Component/s: Core Framework (was: OSGi) Security: Public Fix Version/s: JBossOSGi 1.2.0 (was: 7.2.0.Alpha1) > Unresolvable capability silently prevents entire set to resolve/start > ---------------------------------------------------------------------- > > Key: JBOSGI-611 > URL: https://issues.jboss.org/browse/JBOSGI-611 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: JBossOSGi 1.2.0 > > > Except a debug log there is no further indication why capabilities do not resolve/start > {code} > 08:48:08,858 DEBUG [org.jboss.osgi.framework] (MSC service thread 1-3) Cannot resolve: [HostBundleRevision[org.apache.felix.configadmin:1.2.8], HostBundleRevision[org.apache.felix.log:1.0.0], HostBundleRevision[jboss-osgi-logging:1.0.0], HostBundleRevision[deferred-bundle-a.jar:0.0.0], HostBundleRevision[jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT]]: org.osgi.service.resolver.ResolutionException: Unable to resolve HostBundleRevision[deferred-bundle-a.jar:0.0.0]: missing requirement XPackageRequirement[atts={osgi.wiring.package=org.acme.foo},[deferred-bundle-a.jar:0.0.0]] > at org.apache.felix.resolver.Candidates.populateResource(Candidates.java:285) [jbosgi-resolver-felix-3.0.0.CR10.jar:3.0.0.CR10] > at org.apache.felix.resolver.Candidates.populate(Candidates.java:153) [jbosgi-resolver-felix-3.0.0.CR10.jar:3.0.0.CR10] > at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:96) [jbosgi-resolver-felix-3.0.0.CR10.jar:3.0.0.CR10] > at org.jboss.osgi.resolver.felix.StatelessResolver.resolve(StatelessResolver.java:56) [jbosgi-resolver-felix-3.0.0.CR10.jar:3.0.0.CR10] > at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:152) [jbosgi-framework-core-2.0.0.CR39.jar:2.0.0.CR39] > at org.jboss.osgi.framework.internal.ResolverPlugin.resolveAndApply(ResolverPlugin.java:167) [jbosgi-framework-core-2.0.0.CR39.jar:2.0.0.CR39] > at org.jboss.osgi.framework.internal.PackageAdminPlugin.resolveBundles(PackageAdminPlugin.java:393) [jbosgi-framework-core-2.0.0.CR39.jar:2.0.0.CR39] > at org.jboss.osgi.framework.spi.BootstrapBundlesResolve.start(BootstrapBundlesResolve.java:96) [jbosgi-framework-core-2.0.0.CR39.jar:2.0.0.CR39] > at org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.start(ServiceTracker.java:278) [jbosgi-framework-core-2.0.0.CR39.jar:2.0.0.CR39] > {code} > This should be logged as an error and prevent the subsystem to start -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-610) Review versions of exported system packages

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-610: ------------------------------------- Summary: Review versions of exported system packages Key: JBOSGI-610 URL: https://issues.jboss.org/browse/JBOSGI-610 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 2.0.0 Alpha1 Most system packages are exported without version. Please review. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

[JBoss JIRA] (JBOSGI-608) Integrate StartLevel with Module adaptors

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-608: ------------------------------------- Summary: Integrate StartLevel with Module adaptors Key: JBOSGI-608 URL: https://issues.jboss.org/browse/JBOSGI-608 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 2.0.0 Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
3
0 / 0

[JBoss JIRA] (JBOSGI-607) Add support for start/stop APIs on Module adaptors

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-607: ------------------------------------- Summary: Add support for start/stop APIs on Module adaptors Key: JBOSGI-607 URL: https://issues.jboss.org/browse/JBOSGI-607 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 2.0.0 Alpha1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] (JBOSGI-408) Bundle entry related functionality for plain modules

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-408?page=com.atlassian.jira.plugin... ] Thomas Diesler deleted JBOSGI-408: ---------------------------------- > Bundle entry related functionality for plain modules > ---------------------------------------------------- > > Key: JBOSGI-408 > URL: https://issues.jboss.org/browse/JBOSGI-408 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > > Fully implement/test ModuleEntriesProvider -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-497) OSGi Core 4.3 support

by David Bosschaert (JIRA)

OSGi Core 4.3 support --------------------- Key: JBOSGI-497 URL: https://issues.jboss.org/browse/JBOSGI-497 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: Core Framework 1.0.0 Reporter: David Bosschaert Assignee: David Bosschaert Make the framework Core 4.3 compliant -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

7
11
0 / 0

[JBoss JIRA] Created: (JBOSGI-498) Make resolver core 4.3 compliant

by David Bosschaert (JIRA)

Make resolver core 4.3 compliant -------------------------------- Key: JBOSGI-498 URL: https://issues.jboss.org/browse/JBOSGI-498 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: jboss-osgi-jmx Affects Versions: JBossOSGi 1.0.0 Reporter: David Bosschaert Assignee: David Bosschaert Update the Felix Resolver to be core 4.3 compliant -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
6
0 / 0

[JBoss JIRA] (JBOSGI-605) Assign implementation specific values for system bundle symbolic name/version

by Thomas Diesler (JIRA)

Thomas Diesler created JBOSGI-605: ------------------------------------- Summary: Assign implementation specific values for system bundle symbolic name/version Key: JBOSGI-605 URL: https://issues.jboss.org/browse/JBOSGI-605 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.2.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] (JBOSGI-606) Add support for systemBundle.stop()

by Guillaume Nodet (JIRA)

Guillaume Nodet created JBOSGI-606: -------------------------------------- Summary: Add support for systemBundle.stop() Key: JBOSGI-606 URL: https://issues.jboss.org/browse/JBOSGI-606 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Guillaume Nodet Assignee: Thomas Diesler This should stop the OSGi framework, the same way than framework.stop(). This needs to be done in a way that will allow framework events to be correctly handled, leading to framework.waitForStop() to unblock when the framework is actually stopped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
5
0 / 0

[JBoss JIRA] (JBOSGI-589) Support reference: URLs

by Harald Wellmann (JIRA)

Harald Wellmann created JBOSGI-589: -------------------------------------- Summary: Support reference: URLs Key: JBOSGI-589 URL: https://issues.jboss.org/browse/JBOSGI-589 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.1.1 Reporter: Harald Wellmann Assignee: Thomas Diesler While this is not an official OSGi standard, Equinox, Felix and Knopflerfish all support {{reference:file:}} URLs for provisioning bundles in place, without copying them to the OSGi storage area. This works both for JARs and for directories (exploded bundles), e.g. {noformat} reference:file:/path/to/my/bundle.jar reference:file:target/classes/ {noformat} For interoperability of frameworks, it would be useful for JBoss OSGi to support this protocol. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues October 2012