log::log4perl::javamap(3pm) [debian man page]

JavaMap(3pm)						User Contributed Perl Documentation					      JavaMap(3pm)

NAME

       Log::Log4perl::JavaMap - maps java log4j appenders to Log::Dispatch classes

SYNOPSIS

	    ###############################
	    log4j.appender.FileAppndr1	      = org.apache.log4j.FileAppender
	    log4j.appender.FileAppndr1.File   = /var/log/onetime.log
	    log4j.appender.FileAppndr1.Append = false

	    log4j.appender.FileAppndr1.layout = org.apache.log4j.PatternLayout
	    log4j.appender.FileAppndr1.layout.ConversionPattern=%d %4r [%t] %-5p %c %x - %m%n
	    ###############################

DESCRIPTION

       If somebody wants to create an appender called "org.apache.log4j.ConsoleAppender", we want to translate it to Log::Dispatch::Screen, and
       then translate the log4j options into Log::Dispatch parameters..

   What's Implemented
       (Note that you can always use the Log::Dispatch::* module.  By 'implemented' I mean having a translation class that translates log4j
       options into the Log::Dispatch options so you can use log4j rather than log4perl syntax in your config file.)

       Here's the list of appenders I see on the current (6/2002) log4j site.

       These are implemented

	   ConsoleAppender     - Log::Dispatch::Screen
	   FileAppender        - Log::Dispatch::File
	   RollingFileAppender - Log::Dispatch::FileRotate (by Mark Pfeiffer)
	   JDBCAppender        - Log::Log4perl::Appender::DBI
	   SyslogAppender      - Log::Dispatch::Syslog
	   NTEventLogAppender  - Log::Dispatch::Win32EventLog

       These should/will/might be implemented

	   DailyRollingFileAppender -
	   SMTPAppender     - Log::Dispatch::Email::MailSender

       These might be implemented but they don't have corresponding classes in Log::Dispatch (yet):

	   NullAppender
	   TelnetAppender

       These might be simulated

	   LF5Appender - use Tk?
	   ExternallyRolledFileAppender - catch a HUP instead?

       These will probably not be implemented

	   AsyncAppender
	   JMSAppender
	   SocketAppender - (ships a serialized LoggingEvent to the server side)
	   SocketHubAppender

ROLL YOUR OWN

       Let's say you've in a mixed Java/Perl enviroment and you've come up with some custom Java appender with behavior you want to use in both
       worlds, "myorg.customAppender".	You write a Perl appender with the same behavior "Myorg::CustomAppender". You want to use one config file
       accross both applications, so the config file will have to say 'myorg.customAppender'.  But the mapping from "myorg.customAppender" to
       "Myorg::CustomAppender" isn't in this JavaMap class, so what do you do?

       In  your Perl code, before you call Log::Log4perl::init(), do this:

	   $Log::Log4perl::JavaMap::user_defined{'myorg.customAppender'} =
	       'Myorg::CustomAppender';

       and you can use 'myorg.customAppender' in your config file with impunity.

SEE ALSO

       http://jakarta.apache.org/log4j/docs/

COPYRIGHT AND LICENSE

       Copyright 2002-2009 by Mike Schilli <m@perlmeister.com> and Kevin Goess <cpan@goess.org>.

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.10.1							    2010-07-21							      JavaMap(3pm)

Check Out this Related Man Page

Filter::Boolean(3)					User Contributed Perl Documentation					Filter::Boolean(3)

NAME

       Log::Log4perl::Filter::Boolean - Special filter to combine the results of others

SYNOPSIS

	   log4perl.logger = WARN, AppWarn, AppError

	   log4perl.filter.Match1	= sub { /let this through/ }
	   log4perl.filter.Match2	= sub { /and that, too/ }
	   log4perl.filter.MyBoolean	   = Log::Log4perl::Filter::Boolean
	   log4perl.filter.MyBoolean.logic = Match1 || Match2

	   log4perl.appender.Screen	   = Log::Dispatch::Screen
	   log4perl.appender.Screen.Filter = MyBoolean
	   log4perl.appender.Screen.layout = Log::Log4perl::Layout::SimpleLayout

DESCRIPTION

       Sometimes, it's useful to combine the output of various filters to arrive at a log/no log decision. While Log4j, Log4perl's mother ship,
       chose to implement this feature as a filter chain, similar to Linux' IP chains, Log4perl tries a different approach.

       Typically, filter results will not need to be passed along in chains but combined in a programmatic manner using boolean logic. "Log if
       this filter says 'yes' and that filter says 'no'" is a fairly common requirement but hard to implement as a chain.

       "Log::Log4perl::Filter::Boolean" is a special predefined custom filter for Log4perl which combines the results of other custom filters in
       arbitrary ways, using boolean expressions:

	   log4perl.logger = WARN, AppWarn, AppError

	   log4perl.filter.Match1	= sub { /let this through/ }
	   log4perl.filter.Match2	= sub { /and that, too/ }
	   log4perl.filter.MyBoolean	   = Log::Log4perl::Filter::Boolean
	   log4perl.filter.MyBoolean.logic = Match1 || Match2

	   log4perl.appender.Screen	   = Log::Dispatch::Screen
	   log4perl.appender.Screen.Filter = MyBoolean
	   log4perl.appender.Screen.layout = Log::Log4perl::Layout::SimpleLayout

       "Log::Log4perl::Filter::Boolean"'s boolean expressions allow for combining different appenders by name using AND (&& or &), OR (|| or |)
       and NOT (!) as logical expressions. Parentheses are used for grouping. Precedence follows standard Perl. Here's a bunch of examples:

	   Match1 && !Match2		# Match1 and not Match2
	   !(Match1 || Match2)		# Neither Match1 nor Match2
	   (Match1 && Match2) || Match3 # Both Match1 and Match2 or Match3

SEE ALSO

       Log::Log4perl::Filter, Log::Log4perl::Filter::LevelMatch, Log::Log4perl::Filter::LevelRange, Log::Log4perl::Filter::StringRange

COPYRIGHT AND LICENSE

       Copyright 2002-2009 by Mike Schilli <m@perlmeister.com> and Kevin Goess <cpan@goess.org>.

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.12.1							    2010-02-07							Filter::Boolean(3)

Linux and UNIX Man Pages

log::log4perl::javamap(3pm) [debian man page]

Check Out this Related Man Page