Uses of Interface
org.apache.log4j.component.plugins.Plugin
Packages that use Plugin
Package
Description
The org.apache.log4j.db package provides means to append logging events
into various databases.
-
Uses of Plugin in org.apache.log4j.component.plugins
Classes in org.apache.log4j.component.plugins that implement PluginModifier and TypeClassDescriptionclass
A convienent abstract class for plugin subclasses that implements the basic methods of the Plugin interface.class
Defines the base class for Receiver plugins.Methods in org.apache.log4j.component.plugins that return PluginModifier and TypeMethodDescriptionPluginEvent.getPlugin()
Returns the source Plugin of this event, which is simple the getSource() method casted to Plugin for convenience.PluginRegistry.stopPlugin
(String pluginName) Stops a plugin by plugin name and repository.Methods in org.apache.log4j.component.plugins with parameters of type PluginModifier and TypeMethodDescriptionvoid
Adds a plugin to the plugin registry.private void
PluginRegistry.firePluginStarted
(Plugin plugin) Calls the pluginStarted method on every registered PluginListener.private void
PluginRegistry.firePluginStopped
(Plugin plugin) Calls the pluginStopped method for every registered PluginListner.boolean
Plugin.isEquivalent
(Plugin testPlugin) Returns true if the testPlugin is considered to be "equivalent" to the this plugin.boolean
PluginSkeleton.isEquivalent
(Plugin testPlugin) Returns true if the plugin has the same name and logger repository as the testPlugin passed in.Constructors in org.apache.log4j.component.plugins with parameters of type Plugin -
Uses of Plugin in org.apache.log4j.receivers.db
Classes in org.apache.log4j.receivers.db that implement PluginModifier and TypeClassDescriptionclass
Converts log data stored in a database into LoggingEvents.class
-
Uses of Plugin in org.apache.log4j.receivers.net
Classes in org.apache.log4j.receivers.net that implement PluginModifier and TypeClassDescriptionclass
JMSReceiver receives a remote logging event on a configured JSM topic and "posts" it to a LoggerRepository as if the event was generated locally.class
Multicast-based receiver.class
SocketHubReceiver receives a remote logging event on a configured socket and "posts" it to a LoggerRepository as if the event was generated locally.class
SocketReceiver receives a remote logging event on a configured socket and "posts" it to a LoggerRepository as if the event was generated locally.class
Receive LoggingEvents encoded with an XMLLayout, convert the XML data to a LoggingEvent and post the LoggingEvent.class
XMLSocketReceiver receives a remote logging event via XML on a configured socket and "posts" it to a LoggerRepository as if the event were generated locally.Methods in org.apache.log4j.receivers.net with parameters of type PluginModifier and TypeMethodDescriptionboolean
JMSReceiver.isEquivalent
(Plugin testPlugin) Returns true if the receiver is the same class and they are configured for the same properties, and super class also considers them to be equivalent.boolean
SocketHubReceiver.isEquivalent
(Plugin testPlugin) Returns true if the receiver is the same class and they are configured for the same properties, and super class also considers them to be equivalent.boolean
SocketReceiver.isEquivalent
(Plugin testPlugin) Returns true if the receiver is the same class and they are configured for the same properties, and super class also considers them to be equivalent.boolean
XMLSocketReceiver.isEquivalent
(Plugin testPlugin) Returns true if the receiver is the same class and they are configured for the same properties, and super class also considers them to be equivalent. -
Uses of Plugin in org.apache.log4j.receivers.varia
Classes in org.apache.log4j.receivers.varia that implement PluginModifier and TypeClassDescriptionclass
LogFilePatternReceiver can parse and tail log files, converting entries into LoggingEvents. -
Uses of Plugin in org.apache.log4j.receivers.xml
Classes in org.apache.log4j.receivers.xml that implement PluginModifier and TypeClassDescriptionclass
LogFileXMLReceiver will read an xml-formated log file and make the events in the log file available to the log4j framework.