[Catalyst] New Root Controller in Catalyst 5.66

Matt S Trout dbix-class at trout.me.uk
Mon Apr 17 15:30:31 CEST 2006

Sébastien Wagener wrote:
> On Wed, 2006-03-01 at 13:27 +0000, Matt S Trout wrote:
>> On Wed, Mar 01, 2006 at 06:00:01AM +0100, Sebastian Riedel wrote:
>>> 01.03.2006 05:39 Nilson Santos Figueiredo Junior:
>>>> On 3/1/06, Sebastian Riedel <sri at oook.de> wrote:
>>>>> This is another best practice promoted to be part of core, it will
>>>>> eliminate namespace collisions like for the famous "login" action in
>>>>> combination with auth plugins. ;)
>>> The application class was from the beginning just meant as a place to  
>>> interact with Catalyst "internals", load plugins, configure the app  
>>> and the like.
>> And of course, your $c for each request is blessed into that class by
>> default (unless you set __PACkAGE__->context_class to something else).
> Is it normal that I still have to put the end action into the app class
> (instead of the Root controller) while using DefaultEnd?
> My end action:
> sub end : Private {
>   my ($self, $c) = @_;
>   $c->log->debug("app end action");
>   $c->NEXT::end( $c );
> }

Catalyst::Plugin::DefaultEnd should probably really be 
Catalyst::Controller::DefaultEnd; I usually have my Controller::Root

use base qw/Catalyst::Controller Catalyst::Plugin::DefaultEnd/;

      Matt S Trout       Offering custom development, consultancy and support
   Technical Director    contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd.  mst (at) shadowcatsystems.co.uk for more information

+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +

More information about the Catalyst mailing list