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

[JBoss JIRA] (JBOSGI-689) Complete support for OSGi JNDI

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-689?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-689: ---------------------------------- Component/s: JNDI WildFly > Complete support for OSGi JNDI > ------------------------------ > > Key: JBOSGI-689 > URL: https://issues.jboss.org/browse/JBOSGI-689 > Project: JBoss OSGi > Issue Type: Feature Request > Components: JNDI, WildFly > Reporter: Thomas Diesler > Labels: roadmap > > As expected because of the missing integration with the NamingManger singletons, all tests that go through NamingManager to obtain the InitialContextFactory or the ObjectFactory fail. > {code} > Running org.jboss.test.osgi.example.jndi.JNDITestCase > Tests run: 12, Failures: 1, Errors: 2, Skipped: 2, Time elapsed: 15.574 sec <<< FAILURE! > Results : > Failed tests: testContextManagerReferenceBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): expected:<bar> but was:<Reference Class Name: java.lang.String(..) > Tests in error: > testTraditionalAPIValueBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): JBAS011843: Failed instantiate InitialContextFactory org.jboss.test.osgi.example.jndi.bundle.JNDITestActivator$SimpleInitalContextFactory from classloader ModuleClassLoader for Module "deployment.arquillian-service:main" from Service Module Loader > testTraditionalAPIReferenceBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): JBAS011843: Failed instantiate InitialContextFactory org.jboss.test.osgi.example.jndi.bundle.JNDITestActivator$SimpleInitalContextFactory from classloader ModuleClassLoader for Module "deployment.arquillian-service:main" from Service Module Loader > {code} > In reality it means that OSGi Bundles cannot use JNDI with object References and cannot expect the traditional JNDI API to work. These findings generally raise the question how a spec compliant OSGI JNDI Implementation is supposed to work in a container environment. Specifically, in an environment that has already set the NamingManager singletons. > IMHO there is a layer of abstraction missing. Perhaps the container should register a NamingManger service that the JNDI Implementation can use to register its InitialContextFactoryBuilder and ObjectFactoryBuilder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-691) Optimize OSGi subsystem bootstrap

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-691?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-691: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Optimize OSGi subsystem bootstrap > --------------------------------- > > Key: JBOSGI-691 > URL: https://issues.jboss.org/browse/JBOSGI-691 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > > The OSGi subsystem in AS7 is alrady activated lazily. However, in many cases users only want to deploy a simple artefact that "happens to be" an OSGi bundle (i.e. a JDBC driver) and do not want to deploy a large set of interconnected bundles that make up a complex modular enterprise application. For those cases the OSGi subsystem should bootstrap in a jiffy and we should not see a performance impact that is worth talking about. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-692) Complete support for OSGi JTA

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-692?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-692: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Complete support for OSGi JTA > ----------------------------- > > Key: JBOSGI-692 > URL: https://issues.jboss.org/browse/JBOSGI-692 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > Labels: roadmap > > R5 TCK compliance for JTA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-693) Allow OSGi configuration to get modified before subsystem start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-693?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-693: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Allow OSGi configuration to get modified before subsystem start > --------------------------------------------------------------- > > Key: JBOSGI-693 > URL: https://issues.jboss.org/browse/JBOSGI-693 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > > It should be possible to > * start the server > * modify framework properties > * start the osgi subsystem with the updated properties -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-693) Allow OSGi configuration to get modified before subsystem start

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-693?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-693: ---------------------------------- Component/s: Core Framework WildFly > Allow OSGi configuration to get modified before subsystem start > --------------------------------------------------------------- > > Key: JBOSGI-693 > URL: https://issues.jboss.org/browse/JBOSGI-693 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Core Framework, WildFly > Reporter: Thomas Diesler > > It should be possible to > * start the server > * modify framework properties > * start the osgi subsystem with the updated properties -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-694) Complete support for OSGi Blueprint

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-694?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-694: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Complete support for OSGi Blueprint > ----------------------------------- > > Key: JBOSGI-694 > URL: https://issues.jboss.org/browse/JBOSGI-694 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > Labels: roadmap > > R5 TCK compliance for Blueprint -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-682) Add ability to provision adapted modules

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-682?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-682: ---------------------------------- Component/s: Provisioner > Add ability to provision adapted modules > ---------------------------------------- > > Key: JBOSGI-682 > URL: https://issues.jboss.org/browse/JBOSGI-682 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Provisioner > Reporter: Thomas Diesler > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-682) Add ability to provision adapted modules

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-682?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-682: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Add ability to provision adapted modules > ---------------------------------------- > > Key: JBOSGI-682 > URL: https://issues.jboss.org/browse/JBOSGI-682 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Provisioner > Reporter: Thomas Diesler > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-689) Complete support for OSGi JNDI

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-689?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-689: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Complete support for OSGi JNDI > ------------------------------ > > Key: JBOSGI-689 > URL: https://issues.jboss.org/browse/JBOSGI-689 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > Labels: roadmap > > As expected because of the missing integration with the NamingManger singletons, all tests that go through NamingManager to obtain the InitialContextFactory or the ObjectFactory fail. > {code} > Running org.jboss.test.osgi.example.jndi.JNDITestCase > Tests run: 12, Failures: 1, Errors: 2, Skipped: 2, Time elapsed: 15.574 sec <<< FAILURE! > Results : > Failed tests: testContextManagerReferenceBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): expected:<bar> but was:<Reference Class Name: java.lang.String(..) > Tests in error: > testTraditionalAPIValueBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): JBAS011843: Failed instantiate InitialContextFactory org.jboss.test.osgi.example.jndi.bundle.JNDITestActivator$SimpleInitalContextFactory from classloader ModuleClassLoader for Module "deployment.arquillian-service:main" from Service Module Loader > testTraditionalAPIReferenceBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): JBAS011843: Failed instantiate InitialContextFactory org.jboss.test.osgi.example.jndi.bundle.JNDITestActivator$SimpleInitalContextFactory from classloader ModuleClassLoader for Module "deployment.arquillian-service:main" from Service Module Loader > {code} > In reality it means that OSGi Bundles cannot use JNDI with object References and cannot expect the traditional JNDI API to work. These findings generally raise the question how a spec compliant OSGI JNDI Implementation is supposed to work in a container environment. Specifically, in an environment that has already set the NamingManager singletons. > IMHO there is a layer of abstraction missing. Perhaps the container should register a NamingManger service that the JNDI Implementation can use to register its InitialContextFactoryBuilder and ObjectFactoryBuilder. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-237) [TCK] Conditional Permission Admin

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-237?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-237: ---------------------------------- Priority: Optional (was: Major) > [TCK] Conditional Permission Admin > ---------------------------------- > > Key: JBOSGI-237 > URL: https://issues.jboss.org/browse/JBOSGI-237 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Priority: Optional > Fix For: Awaiting Volunteers > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013