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

[JBoss JIRA] Created: (JBOSGI-141) Service integration with MC

by Thomas Diesler (JIRA)

Service integration with MC --------------------------- Key: JBOSGI-141 URL: https://jira.jboss.org/jira/browse/JBOSGI-141 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Fix For: Framework 1.0.x and vice versa. * Service --> MC The service layer is not so well integrated with the MC. It does just enough to be "OSGi compliant" (of course that's not yet tested). So this is at the moment very simple. The OSGiServiceState which should eventually turn into an MC context implementation has two "facades", the standard ServiceRegistration and ServiceReference interfaces. * MC --> Service Services are also largely complete. What's missing is that we want to expose MC pojos and JMX MBeans etc. as OSGi services. The proper way to do this would be to push the OSGi Filter into kernel project and use the MDR INSTANCE scope as the attributes. There would be a gotcha in that OSGi expect attributes to have case insensitive names, but we would only have to enforce that for OSGi created services. -- 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

15 years, 3 months

2
15
0 / 0

[JBoss JIRA] Created: (JBOSGI-205) Document MC/OSGi Service integration

by Thomas Diesler (JIRA)

Document MC/OSGi Service integration ------------------------------------ Key: JBOSGI-205 URL: https://jira.jboss.org/jira/browse/JBOSGI-205 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Ales Justin Please create a section in the user guide that explains what added benefit this MC/OSGi Service integration brings to the user. If applicable, there should be examples that the user can run and look at. This integration work is the first piece of functionality that we do to justify our effort to implement an OSGi core framework, hence special care should be taken to explain and show the actual benefits. * OSGi services will be exposed as MC beans I suppose that means you can reference/inject OSGi services in the an MC descriptor. Could you describe/show how this would look like? How would this work with service properties. How would this work with multiple implementations of the same service interface? * MC beans will be listed as a OSGi services I suppose that means you can reference/inject MC beans in a BP descriptor. Here as well, could you please describe/show how this would look like? Do MC beans support service properties i.e. Can I use an LDAP filter to find the target service? Can you have multiple implementations of the same service interface? How would the service event model work i.e. Can I use ServiceTracker to track MC beans? -- 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

15 years, 3 months

1
9
0 / 0

[JBoss JIRA] Created: (JBOSGI-143) Implement DynamicImport-Package

by Thomas Diesler (JIRA)

Implement DynamicImport-Package ------------------------------- Key: JBOSGI-143 URL: https://jira.jboss.org/jira/browse/JBOSGI-143 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: Framework 1.0.0 Alpha1 -- 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

15 years, 4 months

1
16
0 / 0

[JBoss JIRA] Created: (JBOSGI-138) Proper system BundleContext implementation

by Thomas Diesler (JIRA)

Proper system BundleContext implementation ------------------------------------------ Key: JBOSGI-138 URL: https://jira.jboss.org/jira/browse/JBOSGI-138 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Fix For: Framework 1.0.0 Alpha1 Currently we have OSGiSystemBundle extends OSGiBundleState which initializes the OSGiBundleState with a null DeploymentUnit All Bundle and BundleContext methods that internally access the DU fail for the system bundle An improved abstraction would be OSGiSystemBundle extends AbstractBundle OSGiBundle extends AbstractBundle -- 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

15 years, 4 months

1
11
0 / 0

[JBoss JIRA] Created: (JBOSGI-139) Implement system BundleContext.loadClass()

by Thomas Diesler (JIRA)

Implement system BundleContext.loadClass() ------------------------------------------ Key: JBOSGI-139 URL: https://jira.jboss.org/jira/browse/JBOSGI-139 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Priority: Critical Fix For: Framework 1.0.0 Alpha1 -- 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

15 years, 4 months

1
7
0 / 0

[JBoss JIRA] Created: (JBOSGI-278) Revisit ControllerContext handling

by Thomas Diesler (JIRA)

Revisit ControllerContext handling ---------------------------------- Key: JBOSGI-278 URL: https://jira.jboss.org/jira/browse/JBOSGI-278 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Ales Justin -- 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

15 years, 4 months

1
8
0 / 0

[JBoss JIRA] Created: (JBOSGI-301) Enable VFS3 leak detection in runtime and jbossas

by Thomas Diesler (JIRA)

Enable VFS3 leak detection in runtime and jbossas ------------------------------------------------- Key: JBOSGI-301 URL: https://jira.jboss.org/jira/browse/JBOSGI-301 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 Code which does not properly cleanup a mount point can be detected by enabling leak detection. Leak detection can be enabled by setting the jboss.vfs.leakDebugging system property to true. -- 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

15 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-94) Remove DeploymentProvidedDeploymentUnitFilter

by Thomas Diesler (JIRA)

Remove DeploymentProvidedDeploymentUnitFilter --------------------------------------------- Key: JBOSGI-94 URL: https://jira.jboss.org/jira/browse/JBOSGI-94 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Remove this class when this functionallity is natively supported by all target containers -- 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

15 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-298) InstanceAlreadyExistsException: osgi.core:type=framework, version=1.5

by Thomas Diesler (JIRA)

InstanceAlreadyExistsException: osgi.core:type=framework,version=1.5 -------------------------------------------------------------------- Key: JBOSGI-298 URL: https://jira.jboss.org/jira/browse/JBOSGI-298 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta7 MBeans might get registered twice. 2010-03-04 20:40:11,113 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=serviceState,version=1.5 2010-03-04 20:40:11,131 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.BundleStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=bundleState,version=1.5 2010-03-04 20:40:11,134 INFO [org.apache.aries.jmx] Registering org.osgi.jmx.framework.PackageStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@ce16ad with name osgi.core:type=packageState,version=1.5 2010-03-04 20:40:11,136 ERROR [org.apache.aries.jmx] MBean is already registered org.apache.felix.log.LogException: javax.management.InstanceAlreadyExistsException: osgi.core:type=packageState,version=1.5 at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:453) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1484) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:963) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:917) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:312) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) at org.apache.aries.jmx.agent.JMXAgentImpl.registerMBeans(JMXAgentImpl.java:128) at org.apache.aries.jmx.agent.JMXAgentContext.registerMBeans(JMXAgentContext.java:58) at org.apache.aries.jmx.MBeanServiceTracker$1.run(MBeanServiceTracker.java:61) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) 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) This is probably due to a asynchronous delay of a previous unregister -- 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

15 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-213) Unexpected dependee state changes

by Thomas Diesler (JIRA)

Unexpected dependee state changes --------------------------------- Key: JBOSGI-213 URL: https://jira.jboss.org/jira/browse/JBOSGI-213 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler B --> X install(X) install(B) start(B) B == ACTIVE X == RESOLVED uninstall(X) B == ACTIVE The MC framework unexpectedly changes the state of B to RESOLVED -- 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

15 years, 5 months

2
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues March 2010