[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 moved WFLY-1273 to JBOSGI-731:
---------------------------------------------
Project: JBoss OSGi (was: WildFly)
Key: JBOSGI-731 (was: WFLY-1273)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: (was: ConfigAdmin)
(was: OSGi)
> Remove hard wired dependency on configadmin
> -------------------------------------------
>
> Key: JBOSGI-731
> URL: https://issues.jboss.org/browse/JBOSGI-731
> Project: JBoss OSGi
> Issue Type: Task
> 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
[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 moved WFLY-1244 to JBOSGI-728:
---------------------------------------------
Project: JBoss OSGi (was: WildFly)
Key: JBOSGI-728 (was: WFLY-1244)
Workflow: jira (was: GIT Pull Request workflow )
Component/s: REST
(was: OSGi)
(was: REST)
> 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