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

[JBoss JIRA] Created: (JBOSGI-177) HttpService bundles need to import org.ops4j.pax.web.service

by Thomas Diesler (JIRA)

HttpService bundles need to import org.ops4j.pax.web.service ------------------------------------------------------------ Key: JBOSGI-177 URL: https://jira.jboss.org/jira/browse/JBOSGI-177 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Compendium Services Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x The example-http and the webconsole need to import org.ops4j.pax.web.service on the MC framework but not on Felix Find out whether this import is justified and if not why the mc framework needs it. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-154) Add Clover test coverage

by Thomas Diesler (JIRA)

Add Clover test coverage ------------------------ Key: JBOSGI-154 URL: https://jira.jboss.org/jira/browse/JBOSGI-154 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.x Smarter testing, better code! Improving test coverage with Clover throughout your development cycle is the key to finding bugs early and raising the quality of your code. http://www.atlassian.com/software/clover/ -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-305) Clarify ServiceReference.getUsingBundles() in ServiceFactory.ungetService()

by Thomas Diesler (JIRA)

Clarify ServiceReference.getUsingBundles() in ServiceFactory.ungetService() --------------------------------------------------------------------------- Key: JBOSGI-305 URL: https://jira.jboss.org/jira/browse/JBOSGI-305 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Consider final boolean[] allGood = new boolean[2]; ServiceFactory factory = new ServiceFactory() { @Override public Object getService(Bundle bundle, ServiceRegistration sreg) { ServiceReference sref = sreg.getReference(); Bundle[] users = sref.getUsingBundles(); assertNotNull("Users not null", users); assertEquals(1, users.length); assertEquals(bundle, users[0]); allGood[0] = true; return new Runnable() { public void run() { } }; } @Override public void ungetService(Bundle bundle, ServiceRegistration sreg, Object service) { ServiceReference sref = sreg.getReference(); Bundle[] users = sref.getUsingBundles(); assertNotNull("Users not null", users); assertEquals(1, users.length); assertEquals(bundle, users[0]); allGood[1] = true; } }; Here we expect the service user to be the same in getService() and ungetService(). This works in Felix-2.0.4 but in Equinox-3.5.2. In Equinox getUsingBundles() returns null in ungetService() The Core TCK 4.2 expects the Felix behaviour in ServiceHookTests.testListenerHook03, AFAICS. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-368) Intermittent failures with resolver preferences

by Thomas Diesler (JIRA)

Intermittent failures with resolver preferences ------------------------------------------------- Key: JBOSGI-368 URL: https://jira.jboss.org/browse/JBOSGI-368 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Running org.jboss.test.osgi.resolver.ResolverTestCase FIXME testPreferredExporterResolved fails occasionally FIXME testPreferredExporterResolvedReverse fails occasionally FIXME testPreferredExporterLowerId fails occasionally FIXME testPreferredExporterLowerIdReverse fails occasionally Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.884 sec -- 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-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-191) OSGi Bundle clustered (farming) deployment

by Thomas Diesler (JIRA)

OSGi Bundle clustered (farming) deployment ------------------------------------------ Key: JBOSGI-191 URL: https://jira.jboss.org/jira/browse/JBOSGI-191 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Cedric sais: ... At the end of the day, I'm looking for a simple way to deploy bundles to a cluster of OSGi containers. JBoss farming does exactly that with J2EE deployables but will all deployables supported by JBoss MC support distributed deployment (farming) ? And more specifically, are/will OSGi bundle farming be supported ? -- 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-419) Cannot start example webapp through console

by Thomas Diesler (JIRA)

Cannot start example webapp through console ------------------------------------------- Key: JBOSGI-419 URL: https://jira.jboss.org/browse/JBOSGI-419 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webapp Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta10 Caused by: org.apache.felix.log.LogException: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:129) at org.ops4j.util.xml.ElementHelper.getRootElement(ElementHelper.java:68) at org.ops4j.pax.web.extender.war.internal.parser.dom.DOMWebXmlParser.parse(DOMWebXmlParser.java:63) at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.createWebAppMetadata(WebXMLParserInterceptor.java:82) at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.invoke(WebXMLParserInterceptor.java:67) at org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:279) at org.jboss.osgi.framework.plugin.internal.LifecycleInterceptorPluginImpl.handleStateChange(LifecycleInterceptorPluginImpl.java:106) at org.jboss.osgi.framework.bundle.AbstractBundle.changeState(AbstractBundle.java:443) at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:192) -- 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-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-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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues April 2011