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

[JBoss JIRA] (JBOSGI-520) Remove dependency on blueprint from aries-jndi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-520?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-520: ---------------------------------- Fix Version/s: Awaiting Volunteers > Remove dependency on blueprint from aries-jndi > ---------------------------------------------- > > Key: JBOSGI-520 > URL: https://issues.jboss.org/browse/JBOSGI-520 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Enterprise OSGi > Reporter: Thomas Diesler > Labels: jndi > Fix For: Awaiting Volunteers > > > aries-jndi-0.3.1 cannot be used without blueprint being installed. The two techs are unrelated however. -- 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-728) Dynamic dependencies for non OSGi deployments

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-728?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-728: ---------------------------------- Fix Version/s: Awaiting Volunteers > Dynamic dependencies for non OSGi deployments > --------------------------------------------- > > Key: JBOSGI-728 > URL: https://issues.jboss.org/browse/JBOSGI-728 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > Currently the RestEasyIntegrationTestCase deploys a JAXRS endpoint that integrates with an OSGi service. The endoint deployment does not trigger the OSGi subsystem to start up, but depends on the compendium being deployed. The compendium gets deployed during OSGi subsystem startup. > There is currently no way for deployment foo to declare a dependency on deployment bar when bar gets deployed during subsystem startup, which gets triggered by deployment foo. > OSGi has the notion of dynamic package import which seems to be required here for non-osgi deployments -- 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-522) Update felix/equinox modules for meaningful performance data

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-522?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-522: ---------------------------------- Fix Version/s: Awaiting Volunteers > Update felix/equinox modules for meaningful performance data > ------------------------------------------------------------ > > Key: JBOSGI-522 > URL: https://issues.jboss.org/browse/JBOSGI-522 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Distribution > Reporter: Thomas Diesler > 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

[JBoss JIRA] (JBOSGI-421) Provide singned versions of the osgi archives

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-421?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-421: ---------------------------------- Fix Version/s: Awaiting Volunteers > Provide singned versions of the osgi archives > --------------------------------------------- > > Key: JBOSGI-421 > URL: https://issues.jboss.org/browse/JBOSGI-421 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Distribution > Reporter: Thomas Diesler > 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

[JBoss JIRA] (JBOSGI-726) Decouple naming & transaction from OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-726?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-726: ---------------------------------- Fix Version/s: Awaiting Volunteers > Decouple naming & transaction from OSGi > --------------------------------------- > > Key: JBOSGI-726 > URL: https://issues.jboss.org/browse/JBOSGI-726 > Project: JBoss OSGi > Issue Type: Task > Components: WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > Currently the naming & transaction subsystem register services on behalf of OSGi > {code} > [tdiesler@tdvaio jboss-as]$ git grep "\"xservice\"" > naming/src/main/java/org/jboss/as/naming/subsystem/NamingSubsystemOSGiService.java: ServiceName serviceName = ServiceName.of("jbosgi", "xservice", regi > transactions/src/main/java/org/jboss/as/txn/service/TransactionManagerService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", Tran > transactions/src/main/java/org/jboss/as/txn/service/UserTransactionService.java: serviceBuilder.addAliases(ServiceName.of("jbosgi", "xservice", UserTra > {code} -- 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-724) Remove dependency on custom extension in XMLParserActivator

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-724?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-724: ---------------------------------- Fix Version/s: Awaiting Volunteers > Remove dependency on custom extension in XMLParserActivator > ----------------------------------------------------------- > > Key: JBOSGI-724 > URL: https://issues.jboss.org/browse/JBOSGI-724 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > We currently overwrite this extension > {code} > activator = new XMLParserActivator() { > @Override > protected URL getResourceURL(Bundle parserBundle, String resname) { > return resloader.getResource(resname); > } > }; > activator.start(syscontext); > {code} > which is not part of the standard API. -- 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-566) Add support for entry/resource related APIs on Module adaptors

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-566?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-566: ---------------------------------- Fix Version/s: Awaiting Volunteers > Add support for entry/resource related APIs on Module adaptors > -------------------------------------------------------------- > > Key: JBOSGI-566 > URL: https://issues.jboss.org/browse/JBOSGI-566 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > 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

[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: ---------------------------------- Fix Version/s: Awaiting Volunteers > Optimize OSGi subsystem bootstrap > --------------------------------- > > Key: JBOSGI-691 > URL: https://issues.jboss.org/browse/JBOSGI-691 > Project: JBoss OSGi > Issue Type: Feature Request > Components: WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > 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-398) Profile framework startup and bundle deployment

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-398?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-398: ---------------------------------- Fix Version/s: Awaiting Volunteers > Profile framework startup and bundle deployment > ----------------------------------------------- > > Key: JBOSGI-398 > URL: https://issues.jboss.org/browse/JBOSGI-398 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > 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

[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: ---------------------------------- Fix Version/s: Awaiting Volunteers > Complete support for OSGi JTA > ----------------------------- > > Key: JBOSGI-692 > URL: https://issues.jboss.org/browse/JBOSGI-692 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Labels: roadmap > Fix For: Awaiting Volunteers > > > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013