February 2011 - jboss-osgi-issues

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

[JBoss JIRA] Created: (JBOSGI-238) TCK: Framework core functionality

by Thomas Diesler (JIRA)

TCK: Framework core functionality --------------------------------- Key: JBOSGI-238 URL: https://jira.jboss.org/jira/browse/JBOSGI-238 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

[JBoss JIRA] Created: (JBOSGI-424) Integration of EventAdmin with AS7 components

by Thomas Diesler (JIRA)

Integration of EventAdmin with AS7 components --------------------------------------------- Key: JBOSGI-424 URL: https://jira.jboss.org/browse/JBOSGI-424 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Non-OSGi components should be able to publish/receive events through EventAdmin and vice versa of course -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-425) Integration of ConfigAdmin with AS7

by Thomas Diesler (JIRA)

Integration of ConfigAdmin with AS7 ----------------------------------- Key: JBOSGI-425 URL: https://jira.jboss.org/browse/JBOSGI-425 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler OSGi service configuration data needs to show up in the domain model and be modifiable through it. Non-OSGi services should be be able to use the same ConfigAdmin service -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-429) BundleUpdateTestCase in functional tests throws NoClassDefFoundError

by David Bosschaert (JIRA)

BundleUpdateTestCase in functional tests throws NoClassDefFoundError -------------------------------------------------------------------- Key: JBOSGI-429 URL: https://jira.jboss.org/browse/JBOSGI-429 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossOSGi 1.0.0 Beta10 Environment: Running against AS7 Alpha2 SNAPSHOT Reporter: David Bosschaert After fixing the Arquillian callback issue (JBOSGI-418) the BundleUpdateTestCase still fails with the exception below [1]. Seems like the exception comes from the side running in AS7 so the test possibly needs to import javax.naming... [1] testUpdateBundle(org.jboss.test.osgi.bundles.BundleUpdateTestCase) Time elapsed: 0.036 sec <<< ERROR! java.lang.NoClassDefFoundError: javax/naming/InitialContext at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2427) at java.lang.Class.getDeclaredMethods(Class.java:1791) at org.junit.runners.model.TestClass.<init>(TestClass.java:38) at org.junit.runners.ParentRunner.<init>(ParentRunner.java:65) at org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:59) at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:74) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:31) at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:24) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:29) at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:57) at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:24) at org.junit.internal.requests.FilterRequest.getRunner(FilterRequest.java:33) at org.junit.runner.JUnitCore.run(JUnitCore.java:136) at org.jboss.arquillian.junit.JUnitTestRunner.execute(JUnitTestRunner.java:69) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethodInternal(JMXTestRunner.java:157) at org.jboss.arquillian.protocol.jmx.JMXTestRunner.runTestMethod(JMXTestRunner.java:119) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:93) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:27) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262) at javax.management.StandardMBean.invoke(StandardMBean.java:391) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at org.jboss.as.jmx.tcl.TcclMBeanServer.invoke(TcclMBeanServer.java:214) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) 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 message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-179) Setup JBoss OSGi on jboss.org

by Thomas Diesler (JIRA)

Setup JBoss OSGi on jboss.org ----------------------------- Key: JBOSGI-179 URL: https://jira.jboss.org/jira/browse/JBOSGI-179 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta5 The current homepage is http://www.jboss.org/community/wiki/JBossOSGi another good source of information is http://jbossosgi.blogspot.com/ The entry point however should be a project on jboss.org http://www.jboss.org/projects/matrix -- 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, 11 months

2
13
0 / 0

[JBoss JIRA] Created: (JBOSGI-192) Access an OSGi service from EJB3

by Thomas Diesler (JIRA)

Access an OSGi service from EJB3 -------------------------------- Key: JBOSGI-192 URL: https://jira.jboss.org/jira/browse/JBOSGI-192 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 Allow access of OSGi services from a SLSB and possibly others. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-313) OSGi service invocation from EE6 WebApp

by Thomas Diesler (JIRA)

OSGi service invocation from EE6 WebApp --------------------------------------- Key: JBOSGI-313 URL: https://jira.jboss.org/jira/browse/JBOSGI-313 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 Please investigate how we access an OSGi service from an existing EE6 webapp. This will eventually boil down to class space consistency at a layer common to both programming models. For the Native Framework this is related to the idea of ServiceMix. Please also investigate if this can be done with existing 3rd party frameworks (i.e. Felix or Equinox) -- 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, 11 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues February 2011