Hi ,
It's a bit late I know buuuut....I'm going to do this anyway:-)

Having encountered a not unrelated problem myself, I did a little investigating and AFAICT, L4P appears to construct it's methods dynamically (using closures) and doesn't make them available to an inheriting bespoke logger wrapper package via the standard route e.g. @ISA/SUPER:: etc., so they are available only to the L4P instance itself.

The only 'obvious' way I could think of at the time was to utilise MyWrapper::AUTOLOAD to dispatch non-overridden L4P method calls to the logger object via a get_logger(class) call and let L4P deal with unknown methods etc. e.g. in a manner something similar to ... 

package MyWrapper;
use warnings;
use strict;
use autodie; # Not strictly necessary, but JIC I forget later

use base qw/Log::Log4perl;
our $AUTOLOAD;

sub get_logger {
    my $self = shift;

    return Log::Log4perl->get_logger(@_); # or $self->SUPER::get_logge
+r(@_) but that requires
                                          # sufficient knowledge of L4
+P to know/realise that
                                          # get_logger is a standard e
+xportable function
}

sub trace_beg {
    my $self = shift;
    
    __PACKAGE__->debug("Starting with args: " . join ' ', @_);
}

sub AUTOLOAD {
    my $self = shift;
    (my $method = $AUTOLOAD) =~ s,.*::,,;
    
    my $class = caller;
    local $Log::Log4perl::Caller_depth = $Log::Log4perl::caller_depth 
++ 1;
    goto $self->get_logger($class)->$method(@_);
}

1;

[download]
The usual caveat emptor applies, but that's close to the way I managed to do it - less an awful lot of extraneous code.

Hope that helps ...

A user level that continues to overstate my experience :-))

In reply to Re: trying to extend Log::Log4perl by Bloodnok
in thread trying to extend Log::Log4perl by mifflin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.