I recommend to use a logging module like Log::Log4perl::Catalyst and do
all your app logging there.
My log package for NAC::Web:NAC looks like this:
package NAC::Web::NAC::Log;
use Moose;
use Catalyst::Log;
use namespace::autoclean;
BEGIN { extends 'Log::Log4perl::Catalyst'; }
=head1 NAME
On 15/10/12 15:21 Alexander Hartmaier wrote:
I recommend to use a logging module like Log::Log4perl::Catalyst and do
all your app logging there.
I use Log::Dispatch. (The application is already deployed, and it's not
feasible to change it to Log4perl now.)
I don't see where in your code you
On 2012-10-15 18:03, Robert Rothenberg wrote:
On 15/10/12 15:21 Alexander Hartmaier wrote:
I recommend to use a logging module like Log::Log4perl::Catalyst and do
all your app logging there.
I use Log::Dispatch. (The application is already deployed, and it's not
feasible to change it to
On 15/10/12 17:49 Alexander Hartmaier wrote:
On 2012-10-15 18:03, Robert Rothenberg wrote:
On 15/10/12 15:21 Alexander Hartmaier wrote:
I recommend to use a logging module like Log::Log4perl::Catalyst and do
all your app logging there.
I use Log::Dispatch. (The application is already
Hi,
I'm developing my first Catalyst application, Windows, MySQL, DBIx and
Template Toolkit. As part of this I've overcome various problems and now
have a working app, but I'm having recurring difficulties understanding the
relationship between DBIx, Catalyst and TT.
What I want is simply to
You don't need to store the data in $c-session.
if you're using Catalyst::View::TT, you just be able to:
$c-stash-{project}=$c-model('DB::Project')-find($project_id);
and then in your view:
h3[% project.project_name %]/h3
regards
On Oct 15, 2012, at 12:28 PM, Tadhg tadhg.da...@gmail.com
I've had a lot of luck with Log::Contextual recently. It's nice for easily
getting logging into model classes.
On 16/10/2012, at 1:21 AM, Alexander Hartmaier wrote:
I recommend to use a logging module like Log::Log4perl::Catalyst and do
all your app logging there.
My log package for
