And the patch I forgot to attach. Adam
Catalyst-Log-Log4perl.v2.tgz
Description: Binary data
On Feb 20, 2007, at 9:02 AM, Cédric Bouvier wrote:
Hello, I'm trying to use Catalyst::Log::Log4perl and I would like it to print the name of the method it was called from and the line number, instead of the default "INFO - message". Unfortunately, it seem to always consider it was called from Catalyst::handle_request, at line 1479. This line callsC::L::Log4perl::_flush, which indeed call log4perl's appropriate method.As far as I understood, C::L::L only pushes log messages to an arrayref,and sends them to log4perl only when _flush() is invoked, and thathappens *after* the request has been handled. The messages are stored inthe arrayref together with their caller's package, and depth (how deepin the call stack they are), but when they are finally sent to Log4perl,most of the context is gone. My questions: - am I missing something obvious? - is this a bug? or is there a good reason? - out of sheer curiosity, why not log at once?- are the authors on the list and willing to turn this postponed logginginto a configurable feature (I can do it myself and provide a patch, if need be) TIA -- C é d r i c B o u v i e r _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalystSearchable archive: http://www.mail-archive.com/ [email protected]/Dev site: http://dev.catalyst.perl.org/
_______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
