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

[JBoss JIRA] (JBOSGI-727) Add support for Framework restart

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-727?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-727: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Add support for Framework restart > --------------------------------- > > Key: JBOSGI-727 > URL: https://issues.jboss.org/browse/JBOSGI-727 > Project: JBoss OSGi > Issue Type: Task > Reporter: Thomas Diesler > > It should be possible to modify the framework configuration and restart the framework in AS7. This is especially important for a Framework instance running in OpenShift. -- 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: ---------------------------------- Component/s: XML Parsing/Binding > 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: XML Parsing/Binding > Reporter: Thomas Diesler > > 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-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: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Dynamic dependencies for non OSGi deployments > --------------------------------------------- > > Key: JBOSGI-728 > URL: https://issues.jboss.org/browse/JBOSGI-728 > Project: JBoss OSGi > Issue Type: Task > Components: REST > Reporter: Thomas Diesler > > 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-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: ---------------------------------- Component/s: WildFly > Dynamic dependencies for non OSGi deployments > --------------------------------------------- > > Key: JBOSGI-728 > URL: https://issues.jboss.org/browse/JBOSGI-728 > Project: JBoss OSGi > Issue Type: Task > Components: REST, WildFly > Reporter: Thomas Diesler > > 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-729) Allign deployment phases with OSGi terminology

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-729?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-729: ---------------------------------- Component/s: WildFly > Allign deployment phases with OSGi terminology > ---------------------------------------------- > > Key: JBOSGI-729 > URL: https://issues.jboss.org/browse/JBOSGI-729 > Project: JBoss OSGi > Issue Type: Task > Components: WildFly > Reporter: Thomas Diesler > > In OSGi we have > * INSTALLED > * RESOLVED > * ACTIVE > * UNINSTALLED > It'd be useful to talk about modules and osgi bundles in the same jagon - i.e > If a deployment is INSTALLED it has valid metadata > If a deployment is RESOLVED it has Module/ClassLoader associated > If a deployment is ACTIVE it can perform its normal operation > If a deployment is UNINSTALLED it can be removed from the system > The task here is mainly to rename/revisit the deployment phases -- 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: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Decouple naming & transaction from OSGi > --------------------------------------- > > Key: JBOSGI-726 > URL: https://issues.jboss.org/browse/JBOSGI-726 > Project: JBoss OSGi > Issue Type: Task > Reporter: Thomas Diesler > > 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-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: ---------------------------------- Component/s: WildFly > 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 > > 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-721) Separate feature provisioning service from OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-721?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-721: ---------------------------------- Comment: was deleted (was: Won't Fix for now - it can stay with the OSGi subsystem because we integrate/provision at that level.) > Separate feature provisioning service from OSGi > ------------------------------------------------ > > Key: JBOSGI-721 > URL: https://issues.jboss.org/browse/JBOSGI-721 > Project: JBoss OSGi > Issue Type: Task > 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-720) Complete support for HttpService

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-720?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-720: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Complete support for HttpService > -------------------------------- > > Key: JBOSGI-720 > URL: https://issues.jboss.org/browse/JBOSGI-720 > Project: JBoss OSGi > Issue Type: Task > Components: HttpService, WildFly > Reporter: Thomas Diesler > Labels: roadmap > > #1 Add support for MimeType, Content-Lenght, etc > #2 Delegate authentication/authorisation to HttpContext > #3 Add support for "/" root context > #4 Make HttpService an optional capability > #5 Make virtual host/port configurable > This issue is complete when the TCK passes -- 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-721) Separate feature provisioning service from OSGi

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-721?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-721: ---------------------------------- Component/s: Provisioner > Separate feature provisioning service from OSGi > ------------------------------------------------ > > Key: JBOSGI-721 > URL: https://issues.jboss.org/browse/JBOSGI-721 > Project: JBoss OSGi > Issue Type: Task > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013