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 2012/02/26 08:36:47 UTC
svn commit: r1293762 [13/15] - in /logging/log4net/site: ./ css/ release/
release/howto/ release/manual/
Propchange: logging/log4net/site/release/manual/introduction.html
------------------------------------------------------------------------------
svn:eol-style = native
Modified: logging/log4net/site/release/manual/plugins.html
URL: http://svn.apache.org/viewvc/logging/log4net/site/release/manual/plugins.html?rev=1293762&r1=1293761&r2=1293762&view=diff
==============================================================================
--- logging/log4net/site/release/manual/plugins.html (original)
+++ logging/log4net/site/release/manual/plugins.html Sun Feb 26 07:36:45 2012
@@ -171,95 +171,95 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to you under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License. -->
-
-
- <a name="main"></a><div class="section"><h2 id="main">Apache log4net™ Manual - Plugins</h2>
- <a name="plugins"></a><div class="section"><h2 id="plugins">Plugins</h2>
- <p>
- Plugins are additional modular components that are attached to a logger repository.
- </p>
- <p>
- Plugins are stored in the <span class="code">PluginMap</span> of an
- <span class="code">ILoggerRepository</span>.
- Plugins are attached to the repository by using the <span class="code">PluginMap.Add</span>
- method.
- </p>
- <p>
- The following plugins are included in the log4net package:
- </p>
- <div class="table">
- <table border="0" class="bodyTable" cellspacing="0">
- <tr class="a">
- <th>
- Type</th>
- <th>
- Description</th>
- </tr>
- <tr class="b">
- <td>log4net.Plugin.RemoteLoggingServerPlugin</td>
- <td>
- Creates a remote logging sink that can receive logging events from a
- <span class="code">RemotingAppender</span>.
- </td>
- </tr>
- </table>
- </div>
- <ul>
- <li>
- <div class="section"><h3>RemoteLoggingServerPlugin<a name="RemoteLoggingServerPlugin"></a></h3>
- <p>
- Creates a remote logging sink that can receive logging events from a
- <span class="code">RemotingAppender</span>.
- </p>
- <p>
- Creates a remoting logging sink. A single
- parameter must be passed to the constructor that specifies the sink URI. This is a
- name used to identify the logging sink object published via remoting and must be
- agreed with the client before communication can take place.
- </p>
- <p>
- Example usage:
- </p>
- <div class="source"><pre>
-LogManager.GetRepository().PluginMap.Add(new RemoteLoggingServerPlugin("LoggingSink"));</pre></div>
- </li>
- </ul>
-
- </div><a name="attributes"></a><div class="section"><h2 id="attributes">Plugin Attributes</h2>
- <p>
- Plugins can be configured using the following assembly-level attributes:
- </p>
- <ul>
- <li>
- <div class="section"><h3>PluginAttribute<a name="PluginAttribute"></a></h3>
- <p>
- Specifies a plugin type to create and attach to the default repository. This attribute
- does not allow plugins to be parameterized. The plugin class must have a public default constructor.
- </p>
- <p>
- This attribute may be used as many times as necessary to attach plugins to the repository.
- </p>
- </li>
- </ul>
- </div></div>
- </div>
-
- </div>
-
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License. -->
+
+
+ <a name="main"></a><div class="section"><h2 id="main">Apache log4net™ Manual - Plugins</h2>
+ <a name="plugins"></a><div class="section"><h2 id="plugins">Plugins</h2>
+ <p>
+ Plugins are additional modular components that are attached to a logger repository.
+ </p>
+ <p>
+ Plugins are stored in the <span class="code">PluginMap</span> of an
+ <span class="code">ILoggerRepository</span>.
+ Plugins are attached to the repository by using the <span class="code">PluginMap.Add</span>
+ method.
+ </p>
+ <p>
+ The following plugins are included in the log4net package:
+ </p>
+ <div class="table">
+ <table border="0" class="bodyTable" cellspacing="0">
+ <tr class="a">
+ <th>
+ Type</th>
+ <th>
+ Description</th>
+ </tr>
+ <tr class="b">
+ <td>log4net.Plugin.RemoteLoggingServerPlugin</td>
+ <td>
+ Creates a remote logging sink that can receive logging events from a
+ <span class="code">RemotingAppender</span>.
+ </td>
+ </tr>
+ </table>
+ </div>
+ <ul>
+ <li>
+ <div class="section"><h3>RemoteLoggingServerPlugin<a name="RemoteLoggingServerPlugin"></a></h3>
+ <p>
+ Creates a remote logging sink that can receive logging events from a
+ <span class="code">RemotingAppender</span>.
+ </p>
+ <p>
+ Creates a remoting logging sink. A single
+ parameter must be passed to the constructor that specifies the sink URI. This is a
+ name used to identify the logging sink object published via remoting and must be
+ agreed with the client before communication can take place.
+ </p>
+ <p>
+ Example usage:
+ </p>
+ <div class="source"><pre>
+LogManager.GetRepository().PluginMap.Add(new RemoteLoggingServerPlugin("LoggingSink"));</pre></div>
+ </li>
+ </ul>
+
+ </div><a name="attributes"></a><div class="section"><h2 id="attributes">Plugin Attributes</h2>
+ <p>
+ Plugins can be configured using the following assembly-level attributes:
+ </p>
+ <ul>
+ <li>
+ <div class="section"><h3>PluginAttribute<a name="PluginAttribute"></a></h3>
+ <p>
+ Specifies a plugin type to create and attach to the default repository. This attribute
+ does not allow plugins to be parameterized. The plugin class must have a public default constructor.
+ </p>
+ <p>
+ This attribute may be used as many times as necessary to attach plugins to the repository.
+ </p>
+ </li>
+ </ul>
+ </div></div>
+ </div>
+
+ </div>
+
</div>
</div>
Propchange: logging/log4net/site/release/manual/plugins.html
------------------------------------------------------------------------------
svn:eol-style = native
Modified: logging/log4net/site/release/manual/repositories.html
URL: http://svn.apache.org/viewvc/logging/log4net/site/release/manual/repositories.html?rev=1293762&r1=1293761&r2=1293762&view=diff
==============================================================================
--- logging/log4net/site/release/manual/repositories.html (original)
+++ logging/log4net/site/release/manual/repositories.html Sun Feb 26 07:36:45 2012
@@ -171,104 +171,104 @@
</div>
<div id="bodyColumn">
<div id="contentBox">
- <!-- Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to you under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License. -->
-
-
- <a name="main"></a><div class="section"><h2 id="main">Apache log4net™ Manual - Repositories</h2>
- <a name="repository"></a><div class="section"><h2 id="repository">Logging Repositories</h2>
- <p>
- Logging repositories are considered advanced functionality. The default behavior
- should be sufficient for most users.
- </p>
- <p>
- Log4net supports logging repositories. A repository is uniquely named.
- Each repository is a (<span class="code">ILoggerRepository</span>).
- Multiple assemblies can link to the same repository.
- </p>
- <p>
- By default there is a single logging repository per process (more precisely per AppDomain). This extends
- across all assemblies loaded into the process and allows them to all share a
- single configuration. The configuration of the repository only needs to be done once,
- typically in the entry point to the application, either programmatically or using
- a configuration attribute.
- </p>
- <p>
- Named logging repositories can be created using the <span class="code">LogManager.CreateRepository</span>
- method. The repository for can be retrieved using the
- <span class="code">LogManager.GetRepository</span> method.
- A repository created in this way will need to be configured programmatically.
- </p>
-
- <a name="attributes"></a><div class="section"><h2 id="attributes">Attributes</h2>
- <p>
- An assembly may choose to utilize a named logging repository rather than the default repository.
- This completely separates the logging for the assembly from the rest of the application.
- This can be very useful to component developers that wish to use log4net for their
- components but do not want to require that all the applications that use their
- component are aware of log4net. It also means that their debugging configuration is
- separated from the applications configuration. The assembly should specify the
- <span class="code">RepositoryAttribute</span> to set its logging repository.
- </p>
- <p>
- The log4net logging repositories can be configured using the following assembly-level
- attributes:
- </p>
- <ul>
- <li>
- <b>AliasRepositoryAttribute</b>
- <p>
- Specifies a named repository to use as this assembly's repository.
- </p>
- <p>
- An assembly's logger repository is defined by its
- <span class="code">RepositoryAttribute</span>, however this can be overridden by an
- assembly loaded before the target assembly.
- </p>
- <p>
- An assembly can alias another assembly's repository by specifying
- this attribute with the name of the target repository.
- </p>
- <p>
- This attribute may be used as many times as necessary to alias all the required
- repositories.
- </p>
- </li>
- <li>
- <b>RepositoryAttribute</b>
- <p>
- Specifies the logging repository for the assembly.
- </p>
- <p>
- Assemblies are mapped to logging repositories. This attribute controls the configuration of the repository. The
- <span class="code">Name</span> property specifies the name of the repository
- for this assembly. The <span class="code">RepositoryType</span>
- property specifies the type of the repository object to create for the assembly.
- If this attribute is not specified and a <span class="code">Name</span>
- is not specified then the assembly will be part of the default shared logging
- repository.
- </p>
- <p>
- This attribute may only be used once per assembly.
- </p>
- </li>
- </ul>
- </div>
- </div>
- </div>
-
+ <!-- Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License. -->
+
+
+ <a name="main"></a><div class="section"><h2 id="main">Apache log4net™ Manual - Repositories</h2>
+ <a name="repository"></a><div class="section"><h2 id="repository">Logging Repositories</h2>
+ <p>
+ Logging repositories are considered advanced functionality. The default behavior
+ should be sufficient for most users.
+ </p>
+ <p>
+ Log4net supports logging repositories. A repository is uniquely named.
+ Each repository is a (<span class="code">ILoggerRepository</span>).
+ Multiple assemblies can link to the same repository.
+ </p>
+ <p>
+ By default there is a single logging repository per process (more precisely per AppDomain). This extends
+ across all assemblies loaded into the process and allows them to all share a
+ single configuration. The configuration of the repository only needs to be done once,
+ typically in the entry point to the application, either programmatically or using
+ a configuration attribute.
+ </p>
+ <p>
+ Named logging repositories can be created using the <span class="code">LogManager.CreateRepository</span>
+ method. The repository for can be retrieved using the
+ <span class="code">LogManager.GetRepository</span> method.
+ A repository created in this way will need to be configured programmatically.
+ </p>
+
+ <a name="attributes"></a><div class="section"><h2 id="attributes">Attributes</h2>
+ <p>
+ An assembly may choose to utilize a named logging repository rather than the default repository.
+ This completely separates the logging for the assembly from the rest of the application.
+ This can be very useful to component developers that wish to use log4net for their
+ components but do not want to require that all the applications that use their
+ component are aware of log4net. It also means that their debugging configuration is
+ separated from the applications configuration. The assembly should specify the
+ <span class="code">RepositoryAttribute</span> to set its logging repository.
+ </p>
+ <p>
+ The log4net logging repositories can be configured using the following assembly-level
+ attributes:
+ </p>
+ <ul>
+ <li>
+ <b>AliasRepositoryAttribute</b>
+ <p>
+ Specifies a named repository to use as this assembly's repository.
+ </p>
+ <p>
+ An assembly's logger repository is defined by its
+ <span class="code">RepositoryAttribute</span>, however this can be overridden by an
+ assembly loaded before the target assembly.
+ </p>
+ <p>
+ An assembly can alias another assembly's repository by specifying
+ this attribute with the name of the target repository.
+ </p>
+ <p>
+ This attribute may be used as many times as necessary to alias all the required
+ repositories.
+ </p>
+ </li>
+ <li>
+ <b>RepositoryAttribute</b>
+ <p>
+ Specifies the logging repository for the assembly.
+ </p>
+ <p>
+ Assemblies are mapped to logging repositories. This attribute controls the configuration of the repository. The
+ <span class="code">Name</span> property specifies the name of the repository
+ for this assembly. The <span class="code">RepositoryType</span>
+ property specifies the type of the repository object to create for the assembly.
+ If this attribute is not specified and a <span class="code">Name</span>
+ is not specified then the assembly will be part of the default shared logging
+ repository.
+ </p>
+ <p>
+ This attribute may only be used once per assembly.
+ </p>
+ </li>
+ </ul>
+ </div>
+ </div>
+ </div>
+
</div>
</div>
Propchange: logging/log4net/site/release/manual/repositories.html
------------------------------------------------------------------------------
svn:eol-style = native