On 10/30/07, Valentin Tumarkin <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I was wondering if there's a "standard" way for preventing Catalyst from
> loading a Controller module. I would like to keep my base Controller modules
> in the MyApp/Controller directory, but do not want Catalyst treating them as
> http-client accessible modules.
>
> For example:
> MyApp/Controller/BaseController.pm
> MyApp/Controller/AdvancedBaseControllerClass.pm (uses BaseController)
> MyApp/Controller/ActualController.pm (uses AdvancedBaseController)
>
> At this time I'm putting my base classes in the MyApp/Base/.. directories,
> but this method just doesn't seem as "clean" to me.
>
> Thank you,
> Valentin
>
>
> _______________________________________________
> List: [email protected]
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive:
> http://www.mail-archive.com/[EMAIL PROTECTED]/
> Dev site: http://dev.catalyst.perl.org/
>
>
Look at the setup_components config key:
__PACKAGE__->config(
setup_components => { except => qr/MyApp::Controller::Base/ }
);
The struct in setup_components is passed directly to Module::Pluggable, so
you can read the pod there to figure out exactly what you want.
-J
--
J. Shirley :: [EMAIL PROTECTED] :: Killing two stones with one bird...
http://www.toeat.com
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[EMAIL PROTECTED]/
Dev site: http://dev.catalyst.perl.org/
