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

[JBoss JIRA] (JBOSGI-732) Populate repository with metadata from system modules/bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-732?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-732: ---------------------------------- Component/s: Repository WildFly > Populate repository with metadata from system modules/bundles > ------------------------------------------------------------- > > Key: JBOSGI-732 > URL: https://issues.jboss.org/browse/JBOSGI-732 > Project: JBoss OSGi > Issue Type: Task > Components: Repository, WildFly > Reporter: Thomas Diesler > > The OSGi configuration supports ModuleIdentifiers. So for example > {code} > <capability name="javax.transaction.api"/> > {code} > references the JTA API module. This actually delegates to the repository implementations which in turn delegates to the ModuleIdentityArtifactProvider. > If the AppServer supports the notion of multiple directories where modules can get loaded from, the ServerEnvironment should reflect that properly. I cannot just load a module on trial/error basis because we use the Repository for impact ananlysis. i.e. Find the modules/bundles that provide the transitive set of capabilities for a given set of requirements (without modifying the runtime). -- 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-731) Remove hard wired dependency on configadmin

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-731?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-731: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Remove hard wired dependency on configadmin > ------------------------------------------- > > Key: JBOSGI-731 > URL: https://issues.jboss.org/browse/JBOSGI-731 > Project: JBoss OSGi > Issue Type: Task > Components: ConfigurationAdmin, WildFly > Reporter: Thomas Diesler > > {code} > interface SystemPackagesIntegration { > String[] DEFAULT_SYSTEM_MODULES = new String[] { > "javax.api", > "javax.inject.api", > "org.apache.xerces", > "org.jboss.as.configadmin", > "org.jboss.as.controller-client", > "org.jboss.as.osgi", > "org.jboss.dmr", > "org.jboss.logging", > "org.jboss.modules", > "org.jboss.msc", > "org.jboss.osgi.framework", > "org.jboss.osgi.repository", > "org.jboss.osgi.resolver" > }; > {code} > A modular build that contains osgi must currently also contain configadmin -- 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-732) Populate repository with metadata from system modules/bundles

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-732?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-732: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Populate repository with metadata from system modules/bundles > ------------------------------------------------------------- > > Key: JBOSGI-732 > URL: https://issues.jboss.org/browse/JBOSGI-732 > Project: JBoss OSGi > Issue Type: Task > Components: Repository, WildFly > Reporter: Thomas Diesler > > The OSGi configuration supports ModuleIdentifiers. So for example > {code} > <capability name="javax.transaction.api"/> > {code} > references the JTA API module. This actually delegates to the repository implementations which in turn delegates to the ModuleIdentityArtifactProvider. > If the AppServer supports the notion of multiple directories where modules can get loaded from, the ServerEnvironment should reflect that properly. I cannot just load a module on trial/error basis because we use the Repository for impact ananlysis. i.e. Find the modules/bundles that provide the transitive set of capabilities for a given set of requirements (without modifying the runtime). -- 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-731) Remove hard wired dependency on configadmin

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-731?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-731: ---------------------------------- Component/s: ConfigurationAdmin WildFly > Remove hard wired dependency on configadmin > ------------------------------------------- > > Key: JBOSGI-731 > URL: https://issues.jboss.org/browse/JBOSGI-731 > Project: JBoss OSGi > Issue Type: Task > Components: ConfigurationAdmin, WildFly > Reporter: Thomas Diesler > > {code} > interface SystemPackagesIntegration { > String[] DEFAULT_SYSTEM_MODULES = new String[] { > "javax.api", > "javax.inject.api", > "org.apache.xerces", > "org.jboss.as.configadmin", > "org.jboss.as.controller-client", > "org.jboss.as.osgi", > "org.jboss.dmr", > "org.jboss.logging", > "org.jboss.modules", > "org.jboss.msc", > "org.jboss.osgi.framework", > "org.jboss.osgi.repository", > "org.jboss.osgi.resolver" > }; > {code} > A modular build that contains osgi must currently also contain configadmin -- 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-723) Provide management view for the OSGi Repository

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-723?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-723. ----------------------------------- Resolution: Won't Fix > Provide management view for the OSGi Repository > ----------------------------------------------- > > Key: JBOSGI-723 > URL: https://issues.jboss.org/browse/JBOSGI-723 > Project: JBoss OSGi > Issue Type: Task > Reporter: Thomas Diesler > Labels: roadmap > -- 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-722) Remove support for legacy osgi subsystem namespaces

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-722?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-722: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Remove support for legacy osgi subsystem namespaces > --------------------------------------------------- > > Key: JBOSGI-722 > URL: https://issues.jboss.org/browse/JBOSGI-722 > Project: JBoss OSGi > Issue Type: Task > Components: WildFly > 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-722) Remove support for legacy osgi subsystem namespaces

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-722?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-722: ---------------------------------- Component/s: WildFly > Remove support for legacy osgi subsystem namespaces > --------------------------------------------------- > > Key: JBOSGI-722 > URL: https://issues.jboss.org/browse/JBOSGI-722 > Project: JBoss OSGi > Issue Type: Task > Components: WildFly > 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-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: ---------------------------------- Component/s: WildFly > Add support for Framework restart > --------------------------------- > > Key: JBOSGI-727 > URL: https://issues.jboss.org/browse/JBOSGI-727 > Project: JBoss OSGi > Issue Type: Task > Components: WildFly > 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-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: ---------------------------------- Component/s: Core Framework > Add support for Framework restart > --------------------------------- > > Key: JBOSGI-727 > URL: https://issues.jboss.org/browse/JBOSGI-727 > Project: JBoss OSGi > Issue Type: Task > Components: Core Framework, WildFly > 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: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Remove dependency on custom extension in XMLParserActivator > ----------------------------------------------------------- > > Key: JBOSGI-724 > URL: https://issues.jboss.org/browse/JBOSGI-724 > Project: JBoss OSGi > Issue Type: Task > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013