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

[JBoss JIRA] Created: (JBOSGI-322) [EOSGi] Integrate the OSGi Remote Services implementation from CXF

by David Bosschaert (JIRA)

[EOSGi] Integrate the OSGi Remote Services implementation from CXF ------------------------------------------------------------------ Key: JBOSGI-322 URL: https://jira.jboss.org/jira/browse/JBOSGI-322 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Compendium Services Reporter: David Bosschaert The Enterprise OSGi Spec describes OSGi Remote Services which is a way to Distribute OSGi Services. An implementation on top of Web Services and REST is available at the CXF Distributed OSGi project (http://cxf.apache.org/distributed-osgi.html). Integrating this in the JBoss OSGi distribution would provide it with support for this important OSGi spec. -- 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, 6 months

6
10
0 / 0

[JBoss JIRA] Created: (JBOSGI-193) Support OSGi webapp deployments in JBossWeb

by Thomas Diesler (JIRA)

Support OSGi webapp deployments in JBossWeb ------------------------------------------- Key: JBOSGI-193 URL: https://jira.jboss.org/jira/browse/JBOSGI-193 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Integration (JBoss) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x OSGi webapps are currenly been deployed onto jboss-osgi-webapp, which contains an embedded PAX-Web WAR extender that in turn delegates to the PAX-Web provided WebContainer based on Jetty. OSGi webapps should be handled by JBossWeb and be deployed onto the JBoss embedded Tomcat instance. -- 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
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-385) IllegalStateException when deploying & starting a bundle through web console

by David Bosschaert (JIRA)

IllegalStateException when deploying & starting a bundle through web console ---------------------------------------------------------------------------- Key: JBOSGI-385 URL: https://jira.jboss.org/browse/JBOSGI-385 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework, jboss-osgi-webconsole Affects Versions: JBossOSGi 1.0.0 Beta8 Reporter: David Bosschaert When installing a bundle through the web console and ticking the start tickbox as well, it often generates an exception (see below). It is probably related to the fact that if you don't select the start tickbox, the bundle gets started anyway. With the tickbox enabled it seems like the system is trying to start the bundle twice concurrently. org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot start bundle: exporting-bundle:0.0.0 at org.jboss.osgi.container.bundle.HostBundle.startInternal(HostBundle.java:239) at org.jboss.osgi.container.bundle.AbstractBundle.start(AbstractBundle.java:478) at org.jboss.osgi.container.plugin.internal.StartLevelPluginImpl$3.run(StartLevelPluginImpl.java:162) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalStateException: BundleContext already available at org.jboss.osgi.container.bundle.AbstractBundle.createBundleContext(AbstractBundle.java:170) at org.jboss.osgi.container.bundle.HostBundle.startInternal(HostBundle.java:179) ... 5 more -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-345) Support specifying start levels for bundles deployed in the deploy directory

by David Bosschaert (JIRA)

Support specifying start levels for bundles deployed in the deploy directory ---------------------------------------------------------------------------- Key: JBOSGI-345 URL: https://jira.jboss.org/browse/JBOSGI-345 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Affects Versions: JBossOSGi 1.0.0 Beta7 Reporter: David Bosschaert Assignee: David Bosschaert When deloying bundles by placing them in the deploy directory it should be possible to specify their start level and whether they need to be started or just installed. One idea is to start supporting 'companion' files that have the same name as the bundle but then with a different extension. So information like this could be placed in a myBundle.md file for a bundle called myBundle.jar. The .md file would be placed in the deploy directory as well and needs to be there before the bundle. Another note is that this mechanism should also work when JBosgi is run in AS -- 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

2
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-62) Distributed OSGi Example

by Thomas Diesler (JIRA)

Distributed OSGi Example ------------------------ Key: JBOSGI-62 URL: https://jira.jboss.org/jira/browse/JBOSGI-62 Project: JBossOSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation 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/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-321) Integrate Apache Aries examples

by Thomas Diesler (JIRA)

Integrate Apache Aries examples ------------------------------- Key: JBOSGI-321 URL: https://jira.jboss.org/jira/browse/JBOSGI-321 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) 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/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-82) Remove the requirement to set the context classloader for JNDI access

by Thomas Diesler (JIRA)

Remove the requirement to set the context classloader for JNDI access --------------------------------------------------------------------- Key: JBOSGI-82 URL: https://jira.jboss.org/jira/browse/JBOSGI-82 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Assignee: Thomas Diesler -- 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-58) Framework injection in SLSB

by Thomas Diesler (JIRA)

Framework injection in SLSB --------------------------- Key: JBOSGI-58 URL: https://jira.jboss.org/jira/browse/JBOSGI-58 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta1 I'm tring to access the OSGIFramework from my Stateless and I got this error: Caused by: javax.management.InstanceNotFoundException: jboss.osgi:service=Framework is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529) at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:675) at org.jboss.mx.util.MBeanProxyExt.init(MBeanProxyExt.java:407) at org.jboss.mx.util.MBeanProxyExt.(MBeanProxyExt.java:99) at org.jboss.mx.util.MBeanProxyExt.create(MBeanProxyExt.java:394) at org.jboss.mx.util.MBeanProxyExt.create(MBeanProxyExt.java:349) at org.jboss.injection.DependsFieldInjector.inject(DependsFieldInjector.java:66) @Stateless public class TestStatelessBean implements TestStatelessRemote { @Depends("jboss.osgi:service=Framework") OSGiFramework framework; @Override public void test() throws NamingException { System.out.println(framework.getSystemBundle()); } -- 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
6
0 / 0

[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-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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues March 2011