July 2011 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-382) Migrate shrinkwrap test bundles

by Thomas Diesler (JIRA)

Migrate shrinkwrap test bundles -------------------------------- Key: JBOSGI-382 URL: https://jira.jboss.org/browse/JBOSGI-382 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Currently we use a rather verbose syntax like // Bundle-SymbolicName: simple-fragA // Export-Package: org.jboss.test.osgi.fragments.fragA // Fragment-Host: simple-hostA final JavaArchive archive = ShrinkWrap.create(JavaArchive.class, "simple-hostA"); archive.addClasses(FragBeanA.class); archive.addResource(getResourceFile("fragments/resource.txt")); archive.setManifest(new Asset() { public InputStream openStream() { OSGiManifestBuilder builder = OSGiManifestBuilder.newInstance(); builder.addBundleManifestVersion(2); builder.addBundleSymbolicName(archive.getName()); builder.addExportPackages(FragBeanA.class); builder.addFragmentHost("simple-hostA"); return builder.openStream(); } }); Bundle fragA = installBundle(archive); assertBundleState(Bundle.INSTALLED, fragA.getState()); This should be supported natively by Shrinkwrap // Bundle-SymbolicName: simple-fragA // Export-Package: org.jboss.test.osgi.fragments.fragA // Fragment-Host: simple-hostA final BundleArchive archive = ShrinkWrap.create(BundleArchive.class, "simple-hostA"); archive.addClasses(FragBeanA.class); archive.addResource(getResourceFile("fragments/resource.txt")); archive.addBundleManifestVersion(2); archive.addBundleSymbolicName(archive.getName()); archive.addExportPackages(FragBeanA.class); archive.addFragmentHost("simple-hostA"); Bundle fragA = installBundle(archive); assertBundleState(Bundle.INSTALLED, fragA.getState()); or simmilar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-189) Provide Virtual File functionality as a bundle

by Thomas Diesler (JIRA)

Provide Virtual File functionality as a bundle ---------------------------------------------- Key: JBOSGI-189 URL: https://jira.jboss.org/jira/browse/JBOSGI-189 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x jboss-vfs is currently on the system classpath. Checkout if we can have this provided by a bundle. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-371) Initial support for PermissionAdmin

by Thomas Diesler (JIRA)

Initial support for PermissionAdmin ----------------------------------- Key: JBOSGI-371 URL: https://jira.jboss.org/browse/JBOSGI-371 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-372) Initial support for ConditionalPermissionAdmin

by Thomas Diesler (JIRA)

Initial support for ConditionalPermissionAdmin ---------------------------------------------- Key: JBOSGI-372 URL: https://jira.jboss.org/browse/JBOSGI-372 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-434) Release 1.0.0

by Thomas Diesler (JIRA)

Release 1.0.0 ------------- Key: JBOSGI-434 URL: https://issues.jboss.org/browse/JBOSGI-434 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta9 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-472) Migrate documentation to confluence

by Thomas Diesler (JIRA)

Migrate documentation to confluence ----------------------------------- Key: JBOSGI-472 URL: https://issues.jboss.org/browse/JBOSGI-472 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.0 David, could you pls create the initial layout - I could then fill in the content. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

2
13
0 / 0

[JBoss JIRA] Created: (JBOSGI-444) Service event failure on Runtime shutdown

by Thomas Diesler (JIRA)

Service event failure on Runtime shutdown ----------------------------------------- Key: JBOSGI-444 URL: https://issues.jboss.org/browse/JBOSGI-444 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler 11:43:17,429 WARN [fail] MSC00004: Failure during stop of service jbosgi.internal.LifecycleInterceptor java.lang.IllegalStateException: Bundle uninstalled: org.apache.felix.log:1.0.0 at org.jboss.osgi.framework.internal.AbstractBundleState.assertNotUninstalled(AbstractBundleState.java:574) at org.jboss.osgi.framework.internal.AbstractBundleState.loadClass(AbstractBundleState.java:416) at org.jboss.osgi.framework.internal.HostBundleState.loadClass(HostBundleState.java:148) at org.jboss.osgi.framework.internal.ServiceState.isAssignableTo(ServiceState.java:335) at org.jboss.osgi.framework.internal.FrameworkEventsPlugin.fireServiceEvent(FrameworkEventsPlugin.java:492) at org.jboss.osgi.framework.internal.ServiceManagerPlugin.unregisterService(ServiceManagerPlugin.java:393) at org.jboss.osgi.framework.internal.ServiceState.unregisterInternal(ServiceState.java:223) at org.jboss.osgi.framework.internal.ServiceState.unregister(ServiceState.java:219) at org.jboss.osgi.framework.internal.ServiceRegistrationWrapper.unregister(ServiceRegistrationWrapper.java:58) at org.jboss.osgi.framework.internal.LifecycleInterceptorPlugin.stop(LifecycleInterceptorPlugin.java:105) at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1779) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-433) [TCK] Intermittent StartLevelControl failure

by Thomas Diesler (JIRA)

[TCK] Intermittent StartLevelControl failure -------------------------------------------- Key: JBOSGI-433 URL: https://issues.jboss.org/browse/JBOSGI-433 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: David Bosschaert Fix For: JBossOSGi 1.0.0 Beta10 There is an intermittent (quite frequent) TCK failure in startlevel Received framework events expected:<org.osgi.framework.FrameworkEvent[source=org.osgi.test.cases.startlevel.tb5:4.2.0]> but was:<FrameworkEvent[type=STARTLEVEL_CHANGED,source=system.bundle:0.0.0]> Stacktrace junit.framework.AssertionFailedError: Received framework events expected:<org.osgi.framework.FrameworkEvent[source=org.osgi.test.cases.startlevel.tb5:4.2.0]> but was:<FrameworkEvent[type=STARTLEVEL_CHANGED,source=system.bundle:0.0.0]> at org.osgi.test.support.OSGiTestCase.assertEquals(OSGiTestCase.java:108) at org.osgi.test.support.OSGiTestCase.assertEquals(OSGiTestCase.java:99) at org.osgi.test.cases.startlevel.junit.StartLevelControl.testExceptionInActivator(StartLevelControl.java:518) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBOSGI-441) Allow for OSGi style Class Filtering

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-441?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-441: ---------------------------------- Fix Version/s: Core Framework 1.0.0 (was: JBossOSGi 1.0.0 CR1) > Allow for OSGi style Class Filtering > ------------------------------------ > > Key: JBOSGI-441 > URL: https://issues.jboss.org/browse/JBOSGI-441 > Project: JBoss OSGi > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Fix For: Core Framework 1.0.0 > > > 3.6.7 Class Filtering > An exporter can limit the visibility of the classes in a package with the > include and exclude directives on the export definition. The value of each of > these directives is a comma-separated list of class names. > The following example shows an export statement, and a list of files with > their visibility status. > Export-Package: com.acme.foo; include:="Qux*,BarImpl";exclude:=QuxImpl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-255) Certified Core Framework

by Thomas Diesler (JIRA)

Certified Core Framework ------------------------ Key: JBOSGI-255 URL: https://jira.jboss.org/jira/browse/JBOSGI-255 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: Framework 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2011