Re: [Maypole] Maypole::Application still broken in 2.09?

From: Simon Flack (sf at flacks.net)
Date: Wed Feb 02 2005 - 19:22:15 GMT


Dave Howorth wrote:
> Matt Adams wrote:
>
>> Just wondering if Marcus R. or Simon F. (or anyone else) had any other
>> suggestions as to why Maypole::Application is still broken in 2.09.
>
>
> I suspect you'll have to wait for Simon for a definitive answer.
>
>> Maybe it's not... maybe it's me?
>>
>> Here's the problem (same as before -- just slightly edited).
>>
>> I recently upgraded to Maypole 2.09 and discovered that it is not
>> compatible with the Maypole app I have been using. I'm hoping that
>> those of you who are more familiar with the Maypole-innards will be
>> able to shed some light on why I'm having the problems I am.
>>
>> It would appear that the neat stuff in Maypole::Application 2.09 is
>> still causing problems for my poor Maypole-powered application.
>>
>> If I downgrade to Maypole::Application 2.07 everything works fine.
>>
>> I don't think my Maypole app is all that odd. Here's how it begins:
>>
>> BEGIN {
>> package MyApp;
>> use MyApp::Constants;
>> $ENV{MAYPOLE_CONFIG} = BINPATH . '/MyApp.yaml';
>> }
>>
>> package MyApp;
>>
>> use Maypole::Application qw(
>> -Debug
>> Config::YAML
>> Authentication::Abstract
>> -Setup
>> );
>>
>> But unfortunately this doesn't work out too well with
>> Maypole::Application 2.09 which still gives me the same error as in 2.08:
>>
>> MyApp...Debugging enabled
>> MyApp...Loaded plugin: Maypole::Plugin::Authentication::Abstract
>> MyApp...Loaded plugin: Maypole::Plugin::Config::YAML
>
>
> This looks a little odd. One of the things fixed in 2.09 was to make
> sure that the plugins really are loaded in the order they are declared
> (this wasn't the case in some previous releases). Now these messages
> aren't in the same order as in your use statement. So are you sure these
> messages are really being output by 2.09?

Indeed. It looks like it has loaded the plugins in sort() order, which
was the case pre 2.09.

Matt, could you check the debug output of:

        #!/usr/bin/perl
        use Maypole::Application 2.09 qw(-Debug Config::YAML
Authentication::Abstract);

> If so, they seem to be showing a 2.09 bug. A complete simple test case
> would be very helpful.
>
>> MyApp...No DSN set in config
>> [error] Can't locate object method "new" via package
>> "Class::DBI::Loader::" (perhaps you forgot to load
>> "Class::DBI::Loader::"?) at /.../lib/Class/DBI/Loader.pm line 77.
>
>
> I guess your config might be relevant to understanding what's going on
> here? (Not by me, I don't use either the YAML or CDBI-Loader :)
>
> Cheers, Dave
>
>> BEGIN failed--compilation aborted at /.../MyApp.pm line 36.
>> Compilation failed in require at (eval 10) line 3.
>> [error] Can't call method "_table2class" on an undefined value at
>> /.../lib/Maypole/Model/CDBI.pm line 250.
>>
>> Can someone give me some pointers as to a) how to fix my app so that
>> it is compliant with Maypole::Application 2.09 and/or b) what exactly
>> was the purpose of the neat code in Maypole::Application 2.09?
>>
>> FWIW, I'm using a PERL5LIB path modified by my Apache configuration.

I wonder whether it's picking up an older version of Maypole. It would
be good to check which version of Maypole::Application is being used. Do
you have Apache::Status installed?

Simon

_______________________________________________
maypole mailing list
maypole at lists.netthink.co.uk
http://lists.netthink.co.uk/listinfo/maypole



This archive was generated by hypermail 2.1.3 : Thu Feb 24 2005 - 22:25:58 GMT