All the other loggers can inherit from the root and use this appender.
其他记录器都是从这个根记录器继承而来，都将使用这个appender。
An appender won't start working before the addAppenderEvent method is called.
appender在addappenderevent方法被调用之前不会启动。
The Log4j documentation provides ample discussion on writing your own custom appender.
Log4j文档对如何编写定制appender进行了详细的讨论。
To better understand the lifecycle of an appender and some of the decisions, a UML Sequence Diagram may help.
为了更好地理解appender的生命周期以及一些决定，可以使用 UML顺序图（UML Sequence Diagram）。
The messages are formatted according to the layout (PatternLayout, in this case) associated with the appender.
这些消息是根据与这个添加器相关的layout（在这种情况中是 PatternLayout）进行格式化的。
The other appender, A2, is a PluginLogAppender and only added to the logger "helloplugin", so TestPluginLog won't use it.
另外一个appender是a2，它是一个pluginlogappender类，只能将它添加到记录器“helloplugin ”中，因此TestPluginLog没有使用它。
As you can see in Listing 7, there are two appenders defined: the appender A1 is a PluginFileAppender and assigned to the root logger.
正如您在清单7中看到的一样，我们定义了两个appender：appender a 1是一个pluginfileappender类，它被分配给根记录器。
You can also create a custom appender (handler) to send events to the "Error Log" view and another to send it to the plug-in state location.
您还可以创建一个定制的appender(处理程序)将事件发送给“ErrorLog ”视图，再创建一个将事件发送到插件所在的位置。
The other appender, PluginLogAppender, has the same lifecycle, but, since it doesn't extend an existing appender, you don't have to worry about initialization problems.
另外一个appender PluginLogAppender的生命周期相同，不过由于它并没有对现有的appender进行扩展，因此您不必担心初始化的问题。
In addition to the JMX appender, Perf4J also provides graphing appenders that generate performance graphs that can be exposed through a web front-end using a Perf4J graphing servlet.
除了JMX插件，Perf4J也支持生成性能图表的画图appender，使用前端的Perf 4j画图servlet。
In addition to the JMX appender, Perf4J also provides graphing appenders that generate performance graphs that can be exposed through a web front-end using a Perf4J graphing servlet.
除了JMX插件，Perf4J也支持生成性能图表的画图appender，使用前端的Perf 4j画图servlet。
应用推荐