You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by bo...@apache.org on 2018/05/30 19:44:58 UTC
[09/10] logging-log4net git commit: LOG4NET-586 document
XmlLayoutSchemaLog4jNS
LOG4NET-586 document XmlLayoutSchemaLog4jNS
Project: http://git-wip-us.apache.org/repos/asf/logging-log4net/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4net/commit/cc8a0575
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4net/tree/cc8a0575
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4net/diff/cc8a0575
Branch: refs/heads/feature/LOG4NET-586
Commit: cc8a05758aad812c5286ff0e26744e831078c69d
Parents: 3ca7996
Author: Stefan Bodewig <bo...@apache.org>
Authored: Wed May 30 18:21:12 2018 +0200
Committer: Stefan Bodewig <bo...@apache.org>
Committed: Wed May 30 21:44:36 2018 +0200
----------------------------------------------------------------------
src/site/xdoc/release/framework-support.xml | 9 +++++++++
src/site/xdoc/release/manual/introduction.xml | 23 +++++++++++++++-------
2 files changed, 25 insertions(+), 7 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/logging-log4net/blob/cc8a0575/src/site/xdoc/release/framework-support.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/release/framework-support.xml b/src/site/xdoc/release/framework-support.xml
index 15a42ae..36eb84c 100644
--- a/src/site/xdoc/release/framework-support.xml
+++ b/src/site/xdoc/release/framework-support.xml
@@ -634,6 +634,15 @@ limitations under the License.
<code>CallContext</code>. Prior to log4net 2.0.8
they haven't been supported for .NET Standard at
all.</p>
+
+ <p><code>log4net.Layout.XmlLayoutSchemaLog4j</code>
+ causes an exception at runtime - as does
+ <code>log4net.Layout.XmlLayout</code> if you
+ specify a prefix. You can try
+ <code>log4net.Layout.XmlLayoutSchemaLog4jNS</code>
+ as an alternative but the resulting XML will not
+ be exactly the same and may not be usable by your
+ downstream tools.</p>
</section>
<section id="net1.0" name="Microsoft .NET Framework 1.0">
http://git-wip-us.apache.org/repos/asf/logging-log4net/blob/cc8a0575/src/site/xdoc/release/manual/introduction.xml
----------------------------------------------------------------------
diff --git a/src/site/xdoc/release/manual/introduction.xml b/src/site/xdoc/release/manual/introduction.xml
index 674635d..5629bda 100644
--- a/src/site/xdoc/release/manual/introduction.xml
+++ b/src/site/xdoc/release/manual/introduction.xml
@@ -989,26 +989,35 @@ ILog y = LogManager.GetLogger("wombat");]]></source>
complies with the log4j event dtd.
</td>
</tr>
+ <tr>
+ <td><a href="../sdk/html/T_log4net_Layout_XmlLayoutSchemaLog4jNS.htm">log4net.Layout.XmlLayoutSchemaLog4jNS</a></td>
+ <td>
+ Formats the logging event as an XML element that
+ is similar to the log4j event dtd
+ but uses an XML namespace with
+ "log4j" as prefix.
+ </td>
+ </tr>
</table>
</div>
</section>
-
+
<section id="renderers" name="Object Renderers">
<p>
- Just as importantly, log4net will render the content of the log message
- according to user specified criteria. For example, if you frequently need to
+ Just as importantly, log4net will render the content of the log message
+ according to user specified criteria. For example, if you frequently need to
log
- <span class="code">Oranges</span>, an object type used in your current project,
+ <span class="code">Oranges</span>, an object type used in your current project,
then you can register an
<span class="code">OrangeRenderer</span>
that will be invoked whenever an orange needs to be logged.
</p>
<p>
- Object rendering follows the class hierarchy. For example, assuming oranges are
+ Object rendering follows the class hierarchy. For example, assuming oranges are
fruits, if you register an
- <span class="code">FruitRenderer</span>, all fruits including oranges will be
+ <span class="code">FruitRenderer</span>, all fruits including oranges will be
rendered by the
- <span class="code">FruitRenderer</span>, unless of course you registered an
+ <span class="code">FruitRenderer</span>, unless of course you registered an
orange specific
<span class="code">OrangeRenderer</span>.
</p>