I'm trying to use Catalyst::Log::Log4perl with Catalyst. My "main"
package is called MintApp.pm, where I do the following calls:
use Catalyst::Log::Log4perl;
...
__PACKAGE__->log (Catalyst::Log::Log4perl->new ('mintapp-log.conf'));
The conf file looks as follows:
log4perl.logger.MintApp=ERROR, S
On 01/04/2008 04:20 PM, Bruce J Keeler wrote:
> Greetings, Catalystos!
>
> I'm looking to find or create a canned solution for rendering
> DBIx::Class::ResultSets as paged, sortable HTML tables. All of the
> examples I've seen do this manually, foreaching through the resultset,
> spitting out s
well, the moral is probably "never work on your code when recovering from flu".
It was pretty much a self-induced problem. I have a system where the
user submits a value, and the value is copied back to them. If there
is a network problem with corruption of the data, they will see it, as
the retur
On Jan 7, 2008, at 8:53 AM, Marius Kjeldahl wrote:
As you can see from the output, for some reason the logger decides to
log several times, even though the logger is/should be only called
once.
If I remove the two first lines in the logger configuration file, it
works fine.
It looks like the
On Jan 5, 2008, at 6:48 PM, Joe Landman wrote:
Hi folks:
Thought I had this nailed, but it looks like I really didn't
understand it as I should have.
Here is the problem. I want to forward to some private actions to
simplify the application (and avoid repeating myself). I want to be
Jason Kohles wrote:
> It isn't the logger that's confused. :)
>
> Refer to the Log::Log4perl::FAQ entry titled 'I keep getting duplicate
> log messages! What's wrong?'
Thanks, looks like oneMessagePerAppender is what is needed. Strangely
enough, I did not encounter this problem at a previous pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PostgreSQL Conference East is being held on the weekend of March 29th
and 30th, 2008 in College Park, Maryland. The conference will have a
series of talks, mini-tutorials and tutorials and we are now accepting
submissions!
If you are a third pary ven
On 1/7/08, Marius Kjeldahl <[EMAIL PROTECTED]> wrote:
> I tried briefly looking into the source, when I ran into this:
>
> # I really have no idea why the correct subroutine
> # is on a different call stack
> $caller{subroutine} = ( caller(1) )[3];
This may or may not be germane: try installing JSON::XS and updating
your JSON and JSON::Any. JSON::XS is one of, if not the, fastest
serializers in all data classes and its utf8 handling is better. JSON
now, IIRC, calls it if it's present instead of its older Perl version.
-Ashley
On Jan
Excellent, and thank you for your work.
As mentioned already I've used Log4perl on another project and I never
ran into the issue. I googled for "catalyst log4perl duplicate" and the
FAQ didn't turn up on the first page. Had I removed catalyst from the
search terms, it would have been item number
On Jan 7, 2008, at 3:27 PM, Adam Jacob wrote:
On 1/7/08, Marius Kjeldahl <[EMAIL PROTECTED]> wrote:
I tried briefly looking into the source, when I ran into this:
# I really have no idea why the correct subroutine
# is on a different call stack
$cal
I'm unable to create multipart/alternative email with C:V:Email 0.10.
This worked with 0.06:
$stash->{email} = {
header => [ From => $from, To => $to, Subject => $subject],
content_type => 'multipart/alternative',
parts => [
Email::MIME->create(
On 1/7/08, Jason Kohles <[EMAIL PROTECTED]> wrote:
> It's also kind of a pain. I use log4perl with Catalyst, but without
> the plugin, primarily for three reasons:
Patches are gladly accepted, especially if they make things better,
and don't break backwards compatibility.
Regards,
Adam
--
HJK
On 1/7/08, Adam Jacob <[EMAIL PROTECTED]> wrote:
> On 1/7/08, Jason Kohles <[EMAIL PROTECTED]> wrote:
> > It's also kind of a pain. I use log4perl with Catalyst, but without
> > the plugin, primarily for three reasons:
>
> Patches are gladly accepted, especially if they make things better,
> and d
14 matches
Mail list logo
