[jboss-jira] [JBoss JIRA] Resolved: (AS7-732) Add start level support to OSGi subsystem
Thomas Diesler (JIRA)
jira-events at lists.jboss.org
Tue May 10 14:21:18 EDT 2011
[ https://issues.jboss.org/browse/AS7-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Diesler resolved AS7-732.
--------------------------------
Resolution: Done
Done
{code}
<subsystem xmlns="urn:jboss:domain:osgi:1.0" activation="eager">
<configuration pid="org.apache.felix.webconsole.internal.servlet.OsgiManager">
<property name="manager.root">jboss-osgi</property>
</configuration>
<properties>
<!--
A comma seperated list of module identifiers. Each system module
is added as a dependency to the OSGi framework module. The packages
from these system modules can be made visible as framework system packages.
http://www.osgi.org/javadoc/r4v42/org/osgi/framework/Constants.html#FRAMEWORK_SYSTEMPACKAGES_EXTRA
-->
<property name="org.jboss.osgi.system.modules">
org.apache.log4j,
org.jboss.as.osgi,
</property>
<!--
Framework environment property identifying extra packages which the system bundle
must export from the current execution environment
-->
<property name="org.osgi.framework.system.packages.extra">
org.apache.log4j;version=1.2,
org.jboss.as.osgi.service;version=7.0,
org.jboss.osgi.spi.capability;version=1.0,
org.jboss.osgi.spi.util;version=1.0,
org.jboss.osgi.testing;version=1.0,
</property>
<!-- Specifies the beginning start level of the framework -->
<property name="org.osgi.framework.startlevel.beginning">2</property>
</properties>
<modules>
<!-- modules registered with the OSGi layer on startup -->
<module identifier="org.jboss.as.arquillian.aggregate"/>
<module identifier="org.jboss.logging"/>
<!-- bundles installed on startup -->
<module identifier="org.apache.aries.util"/>
<module identifier="org.jboss.osgi.webconsole"/>
<module identifier="org.osgi.compendium"/>
<!-- bundles started in startlevel 1 -->
<module identifier="org.apache.aries.jmx" startlevel="1"/>
<module identifier="org.apache.felix.configadmin" startlevel="1"/>
<module identifier="org.apache.felix.eventadmin" startlevel="1"/>
<module identifier="org.apache.felix.log" startlevel="1"/>
<module identifier="org.jboss.as.osgi.configadmin" startlevel="1"/>
<module identifier="org.jboss.osgi.common" startlevel="1"/>
<module identifier="org.jboss.osgi.jmx" startlevel="1"/>
<!-- bundles started in startlevel 2 -->
<module identifier="org.apache.felix.metatype" startlevel="2"/>
<module identifier="org.apache.felix.webconsole" startlevel="2"/>
<module identifier="org.jboss.osgi.http" startlevel="2"/>
<!-- bundles started in startlevel 3 -->
<module identifier="org.jboss.osgi.blueprint" startlevel="3"/>
<module identifier="org.jboss.osgi.webapp" startlevel="3"/>
<module identifier="org.jboss.osgi.xerces" startlevel="3"/>
</modules>
</subsystem>
{code}
> Add start level support to OSGi subsystem
> -----------------------------------------
>
> Key: AS7-732
> URL: https://issues.jboss.org/browse/AS7-732
> Project: Application Server 7
> Issue Type: Feature Request
> Reporter: Thomas Diesler
> Assignee: Thomas Diesler
> Fix For: 7.0.0.CR1
>
>
> Currently the OSGi subsytem installs/starts a minimum set of bundles that are available from the 'bundles' directory. The complete set of distributed bundles should be available for startup - divided into a number of start levels
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list