log: Update BundleEvent mapping table
Spec work for
@@ -880,7 +880,7 @@ logger.error("Cannot access file %s", myFile);</programlisting>
linkend="org.osgi.service.log.LogEntry" xrefstyle="hyperlink"/> object
according to the following table.</para>
- <table>
+ <table xml:id="service.log-table.bundle.event.log.entries">
<title>Mapping of Bundle Events to Log Entries</title>
<tgroup cols="2">
@@ -980,6 +980,21 @@ logger.error("Cannot access file %s", myFile);</programlisting>
<para><code>UNRESOLVED</code> - "BundleEvent
UNRESOLVED"</para>
</listitem>
+
+ <listitem>
+ <para><code>STARTING</code> - "BundleEvent
+ STARTING"</para>
+ </listitem>
+
+ <listitem>
+ <para><code>STOPPING</code> - "BundleEvent
+ STOPPING"</para>
+ </listitem>
+
+ <listitem>
+ <para><code>LAZY_ACTIVATION</code> - "BundleEvent
+ LAZY_ACTIVATION"</para>
+ </listitem>
</itemizedlist></entry>
</row>
</tbody>
@@ -1544,7 +1559,8 @@ logger.error("Cannot access file %s", myFile);</programlisting>
<bibliolist>
<bibliomixed
- xml:id="service.log-slf4j.ref"><title>SLF4J</title><biblioid class="uri"><link
+ xml:id="service.log-slf4j.ref"><title>SLF4J</title><biblioid
+ class="uri"><link
xlink:href="http://www.slf4j.org"/></biblioid></bibliomixed>
</bibliolist>
</section>
@@ -1552,44 +1568,11 @@ logger.error("Cannot access file %s", myFile);</programlisting>
<section>
<title>Changes</title>
- <para>This release of the Log Service specification includes a significant
- number of enhancements and new features.</para>
-
<itemizedlist>
<listitem>
- <para>The log methods of LogService are deprecated and replaced by the
- new Logger type. Loggers are named and have dedicated methods to log
- to the defined log levels. The new Logger Factory service is used to
- obtain Loggers.</para>
- </listitem>
-
- <listitem>
- <para>The new Log Stream Provider service creates Push Streams of Log
- Entries which can be used to receive Log Entries as they are created.
- This is an alternative to using the Log Reader Service.</para>
- </listitem>
-
- <listitem>
- <para>Log Entry is extended to hold the name of the Logger, a sequence
- number which orders log entries, and thread and stack trace
- information about the logging code.</para>
- </listitem>
-
- <listitem>
- <para>The LogLevel enum type specified the supported log levels which
- includes new log levels AUDIT and TRACE.</para>
- </listitem>
-
- <listitem>
- <para>The new Logger Admin service allows the effective log levels of
- named loggers to be configured. It supports integration with
- Configuration Admin so logger configuration can be managed in
- Configuration Admin.</para>
- </listitem>
-
- <listitem>
- <para>Service capabilities are defined for all the specified
- services.</para>
+ <para>The list of Bundle Event types in <xref
+ linkend="service.log-table.bundle.event.log.entries"/> has been
+ updated to include additional event types.</para>
</listitem>
</itemizedlist>
</section>
